What is MCP Service?

The MCP (Model Context Protocol) service generates an authorization URL associated with your individual member identity. With this URL, you can seamlessly connect Jodoo to third-party platforms such as AI agents, code editors, and command-line tools. You can then use these platforms to view your Jodoo tasks, query data, retrieve user messages, and add data to Jodoo forms, enabling cross-platform automation and data collaboration.

MCP Service vs. OpenAPI:

Member-level authorization and ready-to-use tools
The MCP Service uses the permissions of an individual member and packages the corresponding APIs as tools. Once the MCP Service is configured, the member’s identity is authorized and the available tools can be used directly.
Better suited to AI Agent scenarios
MCP tools are more AI Agent-friendly than calling APIs directly.

When to Use It?

The MCP Service is suitable for scenarios where you need to operate Jodoo through an AI assistant. For example:

Quickly retrieve Jodoo tasks and records: Query the current member’s workflow tasks and related form records through the MCP Service to support informed decision-making.
Bring personal work information together: Display workflow tasks, accessible Apps, and member information in a custom dashboard for centralized work management.
Add records to Jodoo forms: Add records to Jodoo forms through the MCP Service, reducing cross-system operations and improving collaboration efficiency.

What Does It Look Like?

The following example shows how to retrieve information about the currently signed-in member in VS Code:

Plan Description

This is a paid advanced feature. For details, contact our Sales Team.

How to Set It Up

Step 1 Enabling the MCP Service

Go to Avatar > Management > Business Settings > Business Security. Click and enable MCP Service.

Step 2 Creating an MCP Service

Go to Open Platform > Developer Tool > MCP Service. Click Create MCP Service, enter a service name, and click Create. The MCP Service is then created successfully.

Notes:

After an admin enables the MCP Service, members of the organization can use it. Each member can create only one MCP Service in an organization.
The MCP Service uses the same Jodoo permissions as the authorizing member. Members can only operate forms and records they have permission to access.
When a member creates an MCP Service, the Create Data capability requires admin approval.

Step 3 Integrating with VS Code

The process for adding the MCP Service to Cursor is the same as the process for adding it to VS Code. This section uses VS Code as an example.

1. On the MCP Service card, click Add to VS Code. After VS Code opens, click Install on the MCP server page to complete the installation.

2. After the MCP server is installed, click Chat to open the chat dialog. Enter the information you want to query, and VS Code will retrieve the relevant records from Jodoo.

Note：For the information that can be queried, see Supported Tools.

Step 4 Integrating with Other Tools

Different AI tools require different MCP setup methods. For details, refer to the MCP configuration documentation for the corresponding AI tool. This section uses OpenCode as an example. For details about MCP configuration, see MCP Servers.

1. After installing OpenCode, locate the opencode.json file in your user home directory and open it.

2. On the Jodoo MCP Service card, go to How to Use and click Copy JSON. Paste the copied JSON configuration into the opencode.json file.

3. Open OpenCode. You can then query relevant Jodoo records directly from the dialog.

Managing MCP Services

Editing an MCP Service

To rename an MCP Service, click Edit in the upper-right corner of the MCP Service card and modify the service name.

Deleting an MCP Service

If you no longer need the MCP Service, click the Delete button in the upper-right corner of the MCP Service card, and then confirm the deletion.

Viewing MCP Service Call Logs

Admins can go to Developer Tool > MCP Service and click MCP Service Call Logs in the upper-right corner to view the relevant logs. The logs can be filtered by the following criteria:

Operator
Type
Time

Supported Tools

The MCP Service currently supports the following tools:

member_data_create: Creates one form record.
member_app_entry_list: Retrieves the list of forms in an App from the current member’s perspective.
member_app_entry_widget_list: Retrieves the list of fields in a form from the current member’s perspective.
member_app_list: Retrieves the list of Apps accessible to the current member.
member_data_get: Retrieves the details of a single record from the current member’s perspective.
member_data_list: Queries multiple records from the current member’s perspective.
member_managed_data_get: Retrieves the details of a single record using the same permission scope as the Manage Data page.
member_managed_data_list: Queries multiple records using the same permission scope as the Manage Data page.
member_user_info: Retrieves information about the currently signed-in member.
member_workflow_task_list: Retrieves the current member’s workflow task list.
get_tool_schema: Retrieves the output JSON Schema of a specified tool. It can be used to restore the response-structure cache when the cache is lost by an Agent client. The input schema is already provided through tools/list and is therefore not returned again.
get_tool_help: Retrieves in-depth usage instructions for a specified tool in Markdown format.The get_tool_help tool currently supports:
- member_data_list
- member_data_create
- member_managed_data_list
- member_workflow_task_list

More to Know

The MCP Service has a rate limit of three requests per second.
Records written through MCP are marked as MCP-written in the data log.
Writing records through MCP is subject to the following limitations:
- Writing to Select Data, Lookup, Image, and Attachment fields is not currently supported.
- Writing records through MCP does not trigger Data Linkage, Formula recalculation, Front-End Events, data validation, or similar features.
- Field visibility rules are not enforced. MCP can write values to fields that are not visible to the member.
To start a workflow or trigger a Automation Pro when creating a record through MCP, provide an explicit instruction in the record-creation request. Otherwise, no workflow will be started and no Automations will be triggered by default.
If you encounter any of the following issues while interacting with the MCP Service, add this instruction to your prompt:
Before calling Jodoo MCP, call the get_tool_help tool first. Then perform the specific business query, such as querying workflow tasks or form records.
This instruction may help when:
- Parameter names cannot be identified accurately.
- Pagination markers are used incorrectly.
- The letter casing of parameters cannot be distinguished.
- An error occurs while querying paginated records through MCP.
- Filter conditions do not work as expected.

MCP Service(Beta)