After enabling the NocoBase MCP Server plugin, your NocoBase app exposes an MCP endpoint that MCP clients can use to access and call NocoBase APIs.
Main app:
http(s)://<host>:<port>/api/mcp
Non-main app:
http(s)://<host>:<port>/api/__app/<app_name>/mcp
This endpoint uses the streamable HTTP transport.
You can use the x-mcp-packages request header to control which package APIs are exposed by MCP, for example:
x-mcp-packages: @nocobase/server,plugin-workflow*,plugin-users
This header accepts full package names. If a scope is omitted, @nocobase/ is added automatically. By default, MCP loads these package APIs:
@nocobase/plugin-data-source-main@nocobase/plugin-data-source-manager@nocobase/plugin-workflow*@nocobase/plugin-acl@nocobase/plugin-users@nocobase/plugin-auth@nocobase/plugin-client@nocobase/plugin-flow-engine@nocobase/plugin-aiFirst, enable the API Keys plugin and create an API key.
First, enable the IdP: OAuth plugin.
First, enable the API Keys plugin and create an API key.
First, enable the IdP: OAuth plugin.
Then open Claude and sign in to the corresponding MCP service:
First, enable the API Keys plugin and create an API key. Configure opencode.json:
First, enable the IdP: OAuth plugin. Configure opencode.json:
Sign in
Debug
It is recommended to use NocoBase MCP together with NocoBase Skills. See NocoBase Skills.