MCP server¶
You can expose Dataiku agents and tools as MCP tools through a dedicated MCP endpoint.
Endpoint¶
Each project has a dedicated MCP endpoint:
http://dss_host:dss_port/public/api/mcp/PROJECT_KEY
Where PROJECT_KEY is the key of the project.
Authentication¶
Authentication is required and is done via API keys. Use HTTP Bearer Token Authentication and pass the API key as the token.
Which agents and tools can be accessed depends on both the API key permissions and which agents and tools have been exposed by the project administrator.
Agents and tools run with the permissions of the API key.
Enabling and disabling¶
At the instance level, a Dataiku administrator can enable or disable the Dataiku MCP server in Administration > Settings > LLM Mesh > Agents. Exposure of Dataiku tools and agents through the MCP server can be configured separately.
At the project level, a project administrator can choose which agents and tools from this project to expose through the Dataiku MCP server in Project settings > MCP & A2A servers.
There are three options for agents:
All - Expose all agents
None - Expose no agents
Custom selection - Choose which agents to expose
The same options are also available for tools:
All - Expose all tools
None - Expose no tools
Custom selection - Choose which tools to expose
Limitations¶
Streaming responses are not supported.
Human approval is not supported on tools exposed through the MCP server, or on tools called by agents exposed through the MCP server.