How to Use Strapi's Docs MCP Server to Power AI Developer Tools

Strapi’s Docs MCP server is a Kapa-hosted remote MCP endpoint that enables AI coding tools such as Cursor, VS Code with GitHub Copilot, Claude Code, and Windsurf to query current Strapi documentation at answer time, helping avoid outdated Strapi 4 patterns when developing with Strapi 5. Available through a single public URL without authentication or a Strapi version requirement, it provides documentation retrieval rather than access to project content, and can be configured with client-specific settings or the Claude Code CLI. The service is particularly useful for addressing migration-related differences including the replacement of Entity Service with Document Service, use of persistent documentId values instead of numeric IDs, flattened REST response structures, and changed publication APIs. Effective use involves explicitly asking the assistant to use the Docs MCP server, specifying Strapi 5, and linking relevant documentation pages, while persistent IDE rules or project instructions can reinforce these requirements. Strapi also offers llms.txt resources, Markdown documentation exports, repository guidance files, and the Inki plugin for broader AI-assisted workflows. In contrast, Strapi’s separate content MCP server runs on a user’s own Strapi instance, requires version 5.47.0 or later and an Admin token, and allows authorized agents to create, update, publish, and delete content; teams can use both servers together to combine accurate documentation-based coding guidance with controlled content management.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.