Strapi MCP Server

Since v5.47.0, [Strapi](https://strapi.io) ships its own Model Context Protocol server in the core CMS — there is no separate package to install and nothing extra to deploy. You enable it by adding an mcp: { enabled: true } block to config/server.ts, and your running Strapi instance starts answering MCP over Streamable HTTP at /mcp.

The tools are generated from your content model, not hard-coded. Every collection type produces up to eight tools — list, get, create, update, delete, publish, unpublish and discard_draft — and every single type produces up to six, with create and update merged into one write and no list. Add a content type and the agent gains tools for it on the next restart. Filtering, sorting, pagination and internationalisation come through from the underlying Document Service, so an agent can ask for the French drafts of a collection updated this month rather than paging through everything. A log tool is available in development for debugging what the agent actually sent.

Permissions are the Admin token's, not the agent's. Authentication is a Authorization: Bearer <admin token> header, and Strapi enforces the token's grants at two levels: tools for content types the token cannot reach are never advertised, and fields it cannot read are filtered out of responses. Scoping an agent down to one collection is therefore a token-creation task in the admin panel, not a prompt-engineering one.

Free and self-hosted, since it is part of the open-source CMS. Strapi shipped it in beta in May 2026 and has been explicit that it is not yet production-ready — the team is collecting feedback on integration friction and on how messy real content models behave before calling it GA. Treat it as excellent for local and staging work, and think carefully before pointing it at a live editorial database.