devkit-for-strapi-mcp

devkit-for-strapi-mcp

An MCP server that gives AI coding agents the truth about your Strapi project. It reads your real schema.json files and exposes the actual UIDs, schemas, and references — so the model stops guessing magic strings like api::article.article, service names, or field names.

Same engine as the DevKit for Strapi VS Code extension, exposed to agents instead of humans. Read-only. Works on Strapi v4 and v5, in JS and TS, with no codegen.

Tools

Tool	What it answers
list_projects	Which Strapi projects are in the workspace (name, root, version).
list_content_types	The real content-type UIDs of a project.
list_components	The real component UIDs.
list_artifacts	The real services / controllers / policies / middlewares.
get_schema	A content-type or component's real attributes (fields, relations, components).
resolve	Where a reference is defined (file + kind).
validate_reference	Is this magic string real? → valid / unknown (+ did you mean) / external.
find_references	Every call-site that uses a UID / service / handler.

In a multi-project workspace, pass from (a path inside the project you're working in) or project (its name) to disambiguate — the server never guesses between two projects.

Use it

The server indexes the workspace root and discovers the Strapi project(s) inside it (a monorepo with several apps works). It takes the root from explicit path arguments, otherwise the current working directory.

Claude Code / Cursor / Claude Desktop

{
  "mcpServers": {
    "devkit-for-strapi": { "command": "npx", "args": ["-y", "devkit-for-strapi-mcp"] }
  }
}

Run the client from your project directory (or pass the path: "args": ["-y", "devkit-for-strapi-mcp", "/path/to/workspace"]).

VS Code

Install the DevKit for Strapi extension — it bundles this server and registers it automatically (no config). It also passes your workspace folders, so multi-root works out of the box.

License

MIT.