Skip to main content

Ollang MCP + Strapi

Strapi’s built-in MCP server is self-hosted and operated by the Strapi project, not Ollang. It is available from v5.47.0 and GA in v5.49.0. Enable it explicitly with server.mcp.enabled in the server config; it is false by default.
Use Strapi’s built-in MCP server at your Strapi instance’s /mcp endpoint with Ollang MCP to automate CMS localization. The Streamable HTTP endpoint might look like http://localhost:1337/mcp.

Why Strapi + Ollang?

Strapi is an open-source headless CMS. By connecting both servers, your AI assistant can:
  • Pull content entries and translate them via Ollang
  • Create localized versions of blog posts and product pages
  • Update and publish translated content
  • Identify content missing translations

Setup

Enable server.mcp.enabled in the Strapi server config, then create an Admin API token in the Strapi admin panel. The token’s permissions determine which CRUD tools are exposed for each content type.
claude_desktop_config.json
Self-hosted and local URLs need a client that can reach your Strapi instance. Claude’s cloud-hosted connectors cannot reach localhost.

Strapi MCP Tools

The Admin API token permissions determine which CRUD tools are exposed for each content type.

Example Workflows

Translate blog posts

Localize a product catalog

Audit CMS localization