Skip to main content
Glama
kedro-org

Kedro MCP Server

Official
by kedro-org
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

Kedro MCP Server

An MCP (Model Context Protocol) server that helps AI assistants (such as VS Code Copilot or Cursor) work consistently with Kedro projects.

The server provides concise, versioned guidance for:

  • General Kedro usage and best practices

  • Converting Jupyter notebooks into production-ready Kedro projects

  • Migrating projects between Kedro versions

With Kedro-MCP, your AI assistant understands Kedro workflows, pipelines, and conventions — so you can focus on building, not fixing AI mistakes.

Quick Install

To enable Kedro MCP tools in your editor, simply click one of the links below.
Your editor will open automatically, and you’ll just need to confirm installation.

Once installed, your AI assistant automatically gains access to Kedro-specific MCP tools.

Helpful references

Universal MCP configuration (JSON)

You can reuse this configuration in any MCP-compatible client (e.g. Copilot, Cursor, Claude, Windsurf):

{
  "command": "uvx",
  "args": ["kedro-mcp@latest"],
  "env": {
    "FASTMCP_LOG_LEVEL": "ERROR"
  },
  "disabled": false,
  "autoApprove": []
}

Related MCP server: CastPlan MCP

Usage

After installation, open Copilot Chat (in Agent Mode) or the Chat panel in Cursor.
Type / to see available Kedro MCP prompts.

Convert a Jupyter Notebook into a Kedro project

/mcp.Kedro.convert_notebook

When you run this command, the assistant explicitly calls the Kedro MCP server and follows the guidance provided.

Typical flow:

  1. The assistant analyses your Jupyter notebook (you can paste its content or mention its filename).

  2. It creates a conversion plan (Statement of Work) saved as a .md file in your workspace.

  3. You review and approve the plan.

  4. The assistant:

    • Ensures a Python virtual environment is active.

    • Installs the latest Kedro if missing.

    • Scaffolds a new project with kedro new.

    • Creates pipelines with kedro pipeline create.

    • Populates parameters.yml and catalog.yml based on your notebook.

You can edit the plan, switch environment tools (uv, venv, conda), or ask the assistant to resolve setup errors interactively.

Migrate a Kedro project

/mcp.Kedro.project_migration

This prompt walks you through migrating an existing Kedro project to a newer version.

Steps:

  1. The assistant analyses your project and proposes a migration plan (e.g. from 0.19 → 1.0).

  2. You review and approve the plan.

  3. The assistant ensures a virtual environment is active, installs the correct Kedro version, and applies migration steps.

Use this to get up-to-date migration tips and avoid deprecated patterns.

General Kedro guidance

/mcp.Kedro.general_usage

Use this prompt for open-ended Kedro questions.
The Kedro MCP server returns structured, up-to-date Kedro guidance that your assistant uses to generate realistic code and pipelines.

Example:

“Generate a Kedro project for a time-series forecasting pipeline using Pandas and scikit-learn.”

Manual Install (from source)

For development or debugging:

git clone https://github.com/kedro-org/kedro-mcp.git
cd kedro-mcp
uv pip install -e . --group dev

Example MCP config (local path):

{
  "mcpServers": {
    "kedro": {
      "command": "uv",
      "args": ["tool", "run", "--from", ".", "kedro-mcp"],
      "env": { "FASTMCP_LOG_LEVEL": "ERROR" }
    }
  }
}

Development

# Install dev dependencies
uv pip install -e . --group dev

# Lint & type-check
ruff check .
mypy src/

Troubleshooting

  • Server not starting: Ensure Python 3.10+ and uv are installed. Confirm the MCP config points to uvx kedro-mcp@latest or to the kedro-mcp console script.

  • Tools not appearing: Restart your assistant and verify that the MCP config key matches "kedro".

  • Version drift: Pin a version instead of @latest for reproducibility.

License

This project is licensed under the Apache Software License 2.0.
See LICENSE.txt for details.

Support

Available Tools

3 tools
kedro_general_instructionsA

Return general Kedro usage guidance.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

A3.7/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden of behavioral disclosure. It only states that guidance is returned, without detailing what topics are covered, the format of the output, or any limitations. This is minimal and leaves significant ambiguity about the tool's behavior.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, succinct sentence with no redundant information. It earns its place by stating the core purpose, exemplifying high conciseness and clear structure.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a parameterless tool, the description is minimally adequate but leaves gaps: it doesn't specify the scope of 'general Kedro usage guidance' or how the output schema relates to the returned content. The presence of an output schema partially compensates, but the description alone is incomplete for full understanding.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is nothing to explain about inputs. The baseline for 0 parameters is 4, and the description appropriately does not need to add parameter-level detail.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: 'Return general Kedro usage guidance.' This uses a specific verb ('return') and resource ('general Kedro usage guidance'), distinguishing it from sibling tools like notebook_to_kedro and project_migration which handle specific conversion/migration tasks.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The usage context is implied by the tool name and description—it is for general guidance—but there is no explicit instruction on when to use this tool versus alternatives. No exclusions or alternative tools are mentioned, so the guidance is only implicit.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

notebook_to_kedroB

Return Notebook→Kedro conversion instructions.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

B3.2/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description must carry the full burden of behavioral disclosure. It only says 'Return... instructions,' which does not reveal whether instructions are generic, notebook-specific, or what form they take, though it is not misleading.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

A single concise sentence that is front-loaded and contains no filler. Every word adds value.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a simple info-return tool, the description is adequate but lacks detail about the nature of the instructions, how they relate to sibling tools, and what content is covered. The presence of an output schema reduces the need to explain return values, but overall the description is thin.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The tool has zero parameters, so there is nothing to explain beyond the schema. Per guidelines, a baseline of 4 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's function: returning conversion instructions from Notebook to Kedro. The verb 'Return' combined with the resource 'Notebook→Kedro conversion instructions' makes it distinct from sibling tools like 'kedro_general_instructions' and 'project_migration'.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives such as 'kedro_general_instructions' or 'project_migration'. The description is too brief to convey any selection context.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

project_migrationC

Return project migration instructions.

ParametersJSON Schema
NameRequiredDescriptionDefault

No parameters

Output Schema

ParametersJSON Schema
NameRequiredDescription
resultYes

TDQS

C2.5/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It implies a read operation ('return') but does not mention any permissions, potential errors, or whether it provides a static guide or dynamic lookup. The transparency is minimal.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single, front-loaded sentence with no wasted words. It is appropriately concise for a tool with no parameters, though it could benefit from additional context. The brevity is effective but not exemplary enough for a 5.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Despite the low complexity (0 params) and the presence of an output schema (which obviates the need to describe return values), the description fails to provide context about what 'project migration' means, when to use it, or how it relates to sibling tools. This is a significant completeness gap.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has zero parameters, so there is nothing to document. Per the baseline rule for 0-parameter tools, this dimension earns a 4; the description correctly says nothing about parameters and is not misleading.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose2/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description 'Return project migration instructions' essentially restates the tool name with a generic verb and resource. It does not specify what 'project migration' means or how it differs from siblings like notebook_to_kedro, making it a tautology rather than a clear, distinguishing purpose.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

There is no guidance on when to use this tool versus alternatives. The description only states what it does, with no mention of scenarios, prerequisites, or exclusions, leaving the agent without decision support.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 3 tool updatesv0.1.2
    • First observedkedro_general_instructions
    • First observednotebook_to_kedro
    • First observedproject_migration
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.1/5.0
Disambiguation5/5

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.

Naming Consistency3/5

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.

Tool Count4/5

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.

Completeness2/5

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.

Maintenance

ActivityInactive
ResponsivenessUnresponsive

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • CodeSavant

    twolven
    A
    license
    Not graded
    quality
    C
    maintenance
    Provides code manipulation, execution, and version control capabilities. It allows AI assistants to read, write, and execute code while maintaining a history of changes.
    9
    MIT

  • CastPlan MCP

    Ghostseller
    A
    license
    B
    quality
    C
    maintenance
    Provides AI assistants with persistent memory of your project architecture, development history, and technical decisions, allowing them to give context-aware coding help without needing repeated explanations.
    16
    61
    2
    MIT

  • RulesetMCP

    n8daniels
    A
    license
    Not graded
    quality
    D
    maintenance
    Provides AI agents with queryable, version-controlled project rules and coding standards. Enables validation, rule-based guidance, and task summaries to keep AI work aligned with your project's conventions without repeating context.
    2
    MIT

  • flyte-mcp

    atoolz
    A
    license
    B
    quality
    C
    maintenance
    Provides AI assistants with accurate Flyte V2 knowledge, patterns, and plugin information to help developers write correct Flyte code. It enables tasks like learning the V2 API, finding examples, selecting plugins, and migrating V1 code to V2.
    17
    Apache 2.0

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kedro-org/kedro-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server