All servers / Developer / Intlayer MCP server
Intlayer MCP server
Intlayer MCP server. Handle MCP to help IDE to use Intlayer. It build, fill, pull, push, dictionaries
Tested by ConnectATDScore 89 out of 100. Tested 2026-11-18 on package version 9.8.1. Package: @intlayer/mcp · source
Score breakdown
| Runs | 18 / 20 | |
|---|---|---|
| Tool descriptions | 19 / 20 | |
| Package safety | 20 / 20 | |
| Maintenance | 20 / 20 | |
| Adoption | 12 / 20 |
What we saw
- Starts and answers the MCP handshake: yes (20.1 seconds including download)
- Tools offered: 45
- Last published: 2026-11-16
- Weekly downloads (npm): 1,903
- License: Apache-2.0 · Direct dependencies: 13
Want this server set up for your team?
ConnectATD builds AI automation and wires up MCP servers like this one. Tell us what you are trying to do.
Talk to ConnectATDTools and how they are described
Agents choose tools from these descriptions. Under each name you can see how many of its parameters are explained.
intlayer-init1 of 1 parameter describedInitialize Intlayer in the project: install the Intlayer packages and set up the framework (config, bundler plugin, middleware, providers). Other setup steps run through the `intlayer init <step>` CLI commands (github-actions, skills, mcp, vscode-extension, lsp, eslint)
intlayer-build2 of 2 parameters describedBuild the dictionaries. List all content declarations files `.content.{ts,tsx,js,json,...}` to update the content callable using the `useIntlayer` hook.
intlayer-fill10 of 10 parameters describedFill the dictionaries with missing translations / review translations using Intlayer servers
intlayer-push5 of 5 parameters describedPush local dictionaries to the server
intlayer-pull3 of 3 parameters describedPull dictionaries from the CMS
intlayer-content-list3 of 3 parameters describedList 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.
intlayer-content-test1 of 1 parameter describedTest 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.
intlayer-extract2 of 2 parameters describedExtract 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.
intlayer-scan2 of 2 parameters describedScan 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.
intlayer-projects-list4 of 4 parameters describedList all Intlayer projects in the directory. Search for configuration files to find all Intlayer projects.
intlayer-install-skills3 of 3 parameters describedInstall 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.
intlayer-install-lsp1 of 1 parameter describedConfigure 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-doc-listno parametersGet the list of docs names and their metadata to get more details about what doc to retrieve. Docs are sorted by `priority` (1 to 10, higher is more important): prefer the higher priority docs when several match.
get-doc0 of 1 parameter describedGet 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-doc-by-slug2 of 2 parameters describedGet an array of docs by their slugs, most important (highest `priority`) first. 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-doc-chunks2 of 2 parameters describedFetch related doc chunks using keywords or questions. This tool will return the most relevant chunks of documentation based on the input query, best first. Relevance is weighted by the doc `priority` (1 to 10, higher is more important).
review-doc-blocks6 of 6 parameters describedCompare 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.
intlayer-dictionaries-list4 of 4 parameters describedList all dictionaries for the selected project. Returns keys, IDs, and metadata.
intlayer-dictionary-get3 of 3 parameters describedGet a dictionary by its key, including its full content.
intlayer-dictionary-create7 of 7 parameters describedCreate a new dictionary in the selected project.
intlayer-dictionary-update7 of 7 parameters describedUpdate an existing dictionary content or metadata.
intlayer-dictionary-delete3 of 3 parameters describedDelete a dictionary by its ID. This action is irreversible.
intlayer-tags-list4 of 4 parameters describedList all tags for the selected organization.
intlayer-tag-create6 of 6 parameters describedCreate a new tag in the organization. Tags can be used to group dictionaries and provide AI context.
intlayer-tag-update7 of 7 parameters describedUpdate an existing tag.
intlayer-tag-delete3 of 3 parameters describedDelete a tag by its ID.
intlayer-organizations-list4 of 4 parameters describedList all organizations the authenticated user belongs to.
intlayer-organization-select3 of 3 parameters describedSelect an organization as the current active organization. Required before accessing organization-specific resources.
intlayer-organization-update3 of 3 parameters describedUpdate the selected organization name or settings.
intlayer-cms-projects-list4 of 4 parameters describedList all Intlayer CMS projects for the selected organization. These are server-side projects, not local project directories.
intlayer-cms-project-select3 of 3 parameters describedSelect a CMS project as the current active project. Required before accessing project-specific dictionaries.
intlayer-cms-project-create3 of 3 parameters describedCreate a new CMS project in the selected organization.
intlayer-cms-project-update3 of 3 parameters describedUpdate the selected CMS project settings.
intlayer-cms-environment-select3 of 3 parameters describedSelect a CMS environment as the current active environment. Required before accessing environment-specific dictionaries.
intlayer-cms-environment-reset2 of 2 parameters describedReset the current active environment to the default production environment.
intlayer-cms-environment-create3 of 3 parameters describedCreate a new CMS environment in the selected project.
intlayer-cms-environment-update4 of 4 parameters describedUpdate the selected CMS environment settings.
intlayer-cms-environment-delete3 of 3 parameters describedDelete a CMS environment by its ID.
intlayer-cms-environment-migrate7 of 7 parameters describedMigrate dictionaries and configuration from one environment to another.
intlayer-analytics-get-schema2 of 2 parameters describedLists what the analytics reports can answer for the project: dimensions and metrics with their compatibility, data retention, first day with data, the project's locales, and its A/B experiments (variants, goals). Call it once before building non-trivial reports.
intlayer-analytics-run-report10 of 10 parameters describedAggregated analytics report of the Intlayer project: metrics broken down by dimensions over 1 to 4 date ranges (all UTC). The main analytics tool: start here for traffic, locales, pages, content exposure and conversions. Use instead: - intlayer-analytics-run-realtime-report for the last 60 minutes. - intlayer-analytics-experiment for A/B significance (p-value, winner). - intlayer-analytics-page-flow for navigation paths between pages. - intlayer-analytics-list-annotations to explain a change (content edits, releases, new locales). Each metric can only be broken down or filtered by these dimensions: - pageViews: date, week, month, locale, pagePath - activeUsers: date, week, month, locale, country - entrances: date, week, month, pagePath - contentExposures: date, week, month, locale, dictionaryKey, keyPath, contentType, variant, experimentKey - conversions: date, week, month, locale, variant, experimentKey, goal - conversionValue: date, week, month, locale, variant, experimentKey, goal Mixing metrics restricts the request to the dimensions they share. Examples: - Locales this month vs last: {"dateRanges":[{"startDate":"30daysAgo","endDate":"today","name":"current"},{"startDate":"60daysAgo","endDate":"31daysAgo","name":"previous"}],"dimensions":["locale"],"metrics":["pageViews","activeUsers"]} - Weekly French blog traffic: {"dateRanges":[{"startDate":"90daysAgo","endDate":"today"}],"dimensions":["week"],"metrics":["pageViews"],"dimensionFilters":[{"dimension":"pagePath","operator":"beginsWith","value":"/fr/blog"}]} - Most displayed fields of a dictionary: {"dateRanges":[{"startDate":"30daysAgo","endDate":"today"}],"dimensions":["keyPath","locale"],"metrics":["contentExposures"],"dimensionFilters":[{"dimension":"dictionaryKey","operator":"exact","value":"home-page"}],"limit":20} Rows hold dimension values (missing: "(not set)") and metric values; with several date ranges a "dateRange" column is added. Read metadata.warnings. activeUsers is a distinct count: use totals, not the sum of rows.
intlayer-analytics-run-realtime-report7 of 7 parameters describedActivity of the last minutes (max 60, default 30): active visitors and page views, optionally by minute, pagePath, locale, country (minute = YYYY-MM-DDTHH:mm, UTC). Aggregated only. Example: {"dimensions":["pagePath"],"metrics":["activeUsers","pageViews"],"minutesAgo":5}
intlayer-analytics-list-annotations6 of 6 parameters describedDated events that can explain a traffic or conversion change, generated from Intlayer data: dictionary created / new content version / last edit, dictionary committed to the repository (with link), first traffic of a locale, start of an A/B experiment. Most recent first. Use it to answer "why did X change around date Y?".
intlayer-analytics-page-flow4 of 4 parameters describedAveraged navigation paths from a starting page: which pages visitors open next, step by step, and where they leave. Use "(entrance)" as startUrl to start from the landing pages.
intlayer-analytics-experiment3 of 3 parameters describedStatistical result of an A/B experiment: exposures, conversions and conversion rate per variant, two-proportion z-test p-value against the control, and the winner (p < 0.05). Experiment keys are listed by intlayer-analytics-get-schema.
Tested in a sandbox with an empty environment: no API keys, a throwaway folder, nothing from a real account. A passing test shows the server runs and responds. It is not a security audit.