Kedro MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FASTMCP_LOG_LEVEL | No | Log level for FastMCP server | ERROR |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| kedro_general_instructionsA | Return general Kedro usage guidance. |
| notebook_to_kedroB | Return Notebook→Kedro conversion instructions. |
| project_migrationC | Return project migration instructions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| convert_notebook | Convert a Jupyter notebook into a Kedro project. |
| migration | Migrate existing project to the latest Kedro version. |
| general_usage | General usage instructions for Kedro. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool clearly targets a distinct area: general usage, notebook conversion, and project migration. There is no overlap in their described purposes, making selection unambiguous.
Names are readable but follow different conventions: 'kedro_general_instructions' uses a prefix, 'notebook_to_kedro' uses an arrow-style descriptor, and 'project_migration' is a plain noun phrase. The lack of a uniform pattern is noticeable.
The server is narrowly scoped to providing instructions, and three tools cover its intended sub-areas. While not excessive, the set is minimal and could benefit from a few more topics to feel more complete.
The domain is Kedro, yet the tool surface covers only general guidance, notebook conversion, and project migration. Missing are tools for pipeline development, data catalog management, or execution, which are core Kedro workflows. This leaves significant gaps for agents needing practical help.