Intlayer MCP Server

What it does

The Intlayer MCP server is published by the makers of Intlayer, a per-component internationalisation library for JavaScript frameworks such as Next.js and React with Vite. It gives a coding assistant three kinds of tools: lookups in the Intlayer documentation, the project-level Intlayer CLI commands (init, build, fill, push, pull, extract and more), and calls to the Intlayer CMS API for dictionaries, tags, organisations, projects and environments.

Run locally over stdio with npx, it registers 37 tools at version 9.7.0: 10 CLI tools, 5 documentation tools, 20 CMS API tools, and two installers that write Intlayer agent skills and Language Server settings into the project. The hosted endpoint at https://mcp.intlayer.org skips the CLI and installer tools; its docs describe it as documentation only, but the server code at v9.7.0 also loads the CMS API tools there, which still need Intlayer credentials (src/server/server.ts).

The documentation search tool returns 10 chunks by default, ordered by each page's priority, and a review tool compares a source markdown file with its translation and returns only the blocks that changed or are missing. A scan tool audits a public website's i18n and SEO signals (lang, hreflang, canonical, sitemap) and returns a score from 0 to 100.

What it needs

Node.js with npx for the local server. The CLI tools act on a project that uses Intlayer (an intlayer config file, or config passed in the call). The CMS tools and push/pull need an Intlayer CMS access key: INTLAYER_CLIENT_ID and INTLAYER_CLIENT_SECRET, set in the environment or passed per call. A deeper render-based website scan needs puppeteer installed separately.

Limits

The hosted endpoint has no CLI or installer tools, and its makers say its availability is not guaranteed: they cap simultaneous connections and recommend the local server. Without INTLAYER_CLIENT_ID and INTLAYER_CLIENT_SECRET every CMS API tool returns a credentials error. intlayer-scan falls back to a plain fetch when puppeteer is not installed. The docs' remote snippets for Cursor, VS Code and Claude Desktop go through the separate mcp-remote package.

Who it suits

Suits developers already using Intlayer, or setting it up, who want an assistant to read its docs, build dictionaries, fill missing translations and sync content with the Intlayer CMS from the editor. The documentation tools work with no account; CMS work needs an access key. Teams that only want docs answers can point a client at the free hosted endpoint; anyone needing the CLI tools must run it locally. It is of no use on projects that use another i18n library.