Intlayer Mcp I18n Solution & Cms

Initialize Intlayer in the project

Build the dictionaries. List all content declarations files `.content.{ts,tsx,js,json,...}` to update the content callable using the `useIntlayer` hook.

Fill the dictionaries with missing translations / review translations using Intlayer servers

Push local dictionaries to the server

Pull dictionaries from the CMS

List the content declaration (.content.{ts,tsx,js,json,...}) files present in the project. That files contain the multilingual content of the application and are used to build the dictionaries.

Test if there are missing translations in the content declaration files. That files contain the multilingual content of the application and are used to build the dictionaries.

Extract strings from an existing component to be placed in a .content file close to the component. Trigger this action to make an existing component multilingual. If the component does not exist, create a normal component including text in JSX, and then trigger this tool to extract it.

Scan a website to measure its page size and audit its i18n / SEO health (html lang/dir, canonical, hreflang, x-default, localized internal links, robots.txt, sitemap.xml, and unused bundle locale content). Returns a 0-100 score and per-check results.

List all Intlayer projects in the directory. Search for configuration files to find all Intlayer projects.

Install Intlayer documentation and skills to the project to assist AI agents. Ask the user for the platform (Cursor, VSCode, OpenCode, Claude, etc.) and which skills they want to install before calling this tool.

Configure the Intlayer Language Server in the project. Writes `intlayer.languageServer.command` and `intlayer.languageServer.args` to `.vscode/settings.json` so that VS Code, Cursor, and Windsurf automatically start the language server, enabling Go-to-Definition for `useIntlayer` and `getIntlayer` calls. Returns next-step instructions for installing the `@intlayer/lsp` binary and, optionally, registering the Intlayer Claude Code plugin.

Get the list of docs names and their metadata to get more details about what doc to retrieve

Get a doc by his key. Example: `./docs/en/getting-started.md`. List all docs metadata first to get more details about what doc key to retrieve.

Get an array of docs by their slugs. If not slug is provided, return all docs (1.2Mb). List all docs metadata first to get more details about what doc to retrieve.

Fetch related doc chunks using keywords or questions. This tool will return the most relevant chunks of documentation based on the input query.

Compare a base markdown document with its translation and return only the blocks that diverge (changed, missing, or stale), with their line ranges and content. Use this to translate a large document incrementally without retranslating it from scratch: it tells you exactly which blocks to (re)translate. Optionally pass the base line numbers that changed (for example from a git diff) so aligned-but-edited blocks are flagged for review.

List all dictionaries for the selected project. Returns keys, IDs, and metadata.

Get a dictionary by its key, including its full content.

Create a new dictionary in the selected project.

Update an existing dictionary content or metadata.

Delete a dictionary by its ID. This action is irreversible.

List all tags for the selected organization.

Create a new tag in the organization. Tags can be used to group dictionaries and provide AI context.

Update an existing tag.

Delete a tag by its ID.

List all organizations the authenticated user belongs to.

Select an organization as the current active organization. Required before accessing organization-specific resources.

Update the selected organization name or settings.

List all Intlayer CMS projects for the selected organization. These are server-side projects, not local project directories.

Select a CMS project as the current active project. Required before accessing project-specific dictionaries.

Create a new CMS project in the selected organization.

Update the selected CMS project settings.

Select a CMS environment as the current active environment. Required before accessing environment-specific dictionaries.

Reset the current active environment to the default production environment.

Create a new CMS environment in the selected project.

Update the selected CMS environment settings.

Delete a CMS environment by its ID.

Migrate dictionaries and configuration from one environment to another.