Connecting Windsurf to Your Strapi CMS via MCP

Strapi 5.47.0 and later includes a built-in Model Context Protocol server, generally available from version 5.49.0, that lets Windsurf’s Cascade agent manage CMS content through Strapi’s `/mcp` endpoint rather than requiring repeated use of the Admin Panel. Setup requires enabling MCP in Strapi’s server configuration, creating a narrowly scoped Admin token, and adding a `serverUrl` plus Bearer authorization header to Windsurf’s `mcp_config.json`, after which Cascade discovers only the tools allowed by that token. Depending on Content-Type settings and permissions, Cascade can list, retrieve, create, update, delete, publish, unpublish, and discard drafts through natural-language prompts, while Strapi enforces access controls for tools, fields, locales, and individual runtime actions. The guidance recommends dedicated least-privilege tokens, environment-variable storage for secrets, and testing first on staging with read-only access; Enterprise users on Strapi 5.52.0 or later can also identify MCP activity in audit logs. Common issues include failing to restart or refresh applications after configuration changes, using unsupported request methods on the POST-only endpoint, and missing token permissions, while current limitations include no media uploads, untyped Dynamic Zones, no nested relation population, and potential schema degradation for some custom or circular component fields.

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.