@intlayer/mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 3 of 5 tools tried
Contacts while installing and starting: nothing
Its tool definitions changed since version 9.7.3. If you approved the earlier ones, read them again.
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y @intlayer/mcp@9.8.1
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
5 tools that take no input and look read-only were called once with nothing. 3 returned a result.
intlayer-content-list | Returned a result under 0.1 s · 2 characters |
intlayer-projects-list | Returned a result 0.4 s · 44 characters |
get-doc-list | Returned a result under 0.1 s · 284,850 characters |
get-doc-by-slug | No usable answer server exited with code 1 |
intlayer-dictionaries-list | No usable answer server exited with code 1 |
During the calls it contacted nothing it had not already contacted.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
intlayer-init projectRoot
Initialize 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-build watch, configOptions
Build the dictionaries. List all content declarations files `.content.{ts,tsx,js,json,...}` to update the content callable using the `useIntlayer` hook.intlayer-fill sourceLocale, outputLocales, file, mode, keys, excludedKeys, pathFilter, gitOptions, aiOptions, configOptions
Fill the dictionaries with missing translations / review translations using Intlayer servers
intlayer-push deleteLocaleDictionary, keepLocaleDictionary, dictionaries, gitOptions, configOptions
Push local dictionaries to the server
intlayer-pull dictionaries, newDictionariesPath, configOptions
Pull dictionaries from the CMS
40 more tools
intlayer-content-list configOptions, absolute, json
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.intlayer-content-test configOptions
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.
intlayer-extract file, configOptions
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.
intlayer-scan url, deep
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.
intlayer-projects-list baseDir, gitRoot, absolute, json
List all Intlayer projects in the directory. Search for configuration files to find all Intlayer projects.
intlayer-install-skills platform, skills, projectRoot
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.
intlayer-install-lsp projectRoot
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-doc-list
Get 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-doc docKey
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-doc-by-slug slug, strict
Get 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-chunks query, limit
Fetch 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-blocks baseContent, targetContent, changedLines, baseLabel, targetLabel, format
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.
intlayer-dictionaries-list clientId, clientSecret, page, pageSize
List all dictionaries for the selected project. Returns keys, IDs, and metadata.
intlayer-dictionary-get clientId, clientSecret, dictionaryKey
Get a dictionary by its key, including its full content.
intlayer-dictionary-create clientId, clientSecret, projectId, key, title, description, content
Create a new dictionary in the selected project.
intlayer-dictionary-update clientId, clientSecret, id, key, title, description, content
Update an existing dictionary content or metadata.
intlayer-dictionary-delete clientId, clientSecret, dictionaryId
Delete a dictionary by its ID. This action is irreversible.
intlayer-tags-list clientId, clientSecret, page, pageSize
List all tags for the selected organization.
intlayer-tag-create clientId, clientSecret, key, name, description, instructions
Create a new tag in the organization. Tags can be used to group dictionaries and provide AI context.
intlayer-tag-update clientId, clientSecret, tagId, key, name, description, instructions
Update an existing tag.
intlayer-tag-delete clientId, clientSecret, tagId
Delete a tag by its ID.
intlayer-organizations-list clientId, clientSecret, page, pageSize
List all organizations the authenticated user belongs to.
intlayer-organization-select clientId, clientSecret, organizationId
Select an organization as the current active organization. Required before accessing organization-specific resources.
intlayer-organization-update clientId, clientSecret, name
Update the selected organization name or settings.
intlayer-cms-projects-list clientId, clientSecret, page, pageSize
List all Intlayer CMS projects for the selected organization. These are server-side projects, not local project directories.
intlayer-cms-project-select clientId, clientSecret, projectId
Select a CMS project as the current active project. Required before accessing project-specific dictionaries.
intlayer-cms-project-create clientId, clientSecret, name
Create a new CMS project in the selected organization.
intlayer-cms-project-update clientId, clientSecret, name
Update the selected CMS project settings.
intlayer-cms-environment-select clientId, clientSecret, environmentId
Select a CMS environment as the current active environment. Required before accessing environment-specific dictionaries.
intlayer-cms-environment-reset clientId, clientSecret
Reset the current active environment to the default production environment.
intlayer-cms-environment-create clientId, clientSecret, name
Create a new CMS environment in the selected project.
intlayer-cms-environment-update clientId, clientSecret, environmentId, name
Update the selected CMS environment settings.
intlayer-cms-environment-delete clientId, clientSecret, environmentId
Delete a CMS environment by its ID.
intlayer-cms-environment-migrate clientId, clientSecret, sourceEnvironmentId, targetEnvironmentId, strategy, migrateContent, migrateConfiguration
Migrate dictionaries and configuration from one environment to another.
intlayer-analytics-get-schema clientId, clientSecret
Lists 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-report clientId, clientSecret, dateRanges, dimensions, metrics, dimensionFilters, metricFilters, orderBys, limit, offset
Aggregated 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-report clientId, clientSecret, dimensions, metrics, minutesAgo, dimensionFilters, limit
Activity 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-annotations clientId, clientSecret, startDate, endDate, types, limit
Dated 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-flow clientId, clientSecret, startUrl, range
Averaged 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-experiment clientId, clientSecret, experimentKey
Statistical 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.
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | Apache-2.0 |
|---|---|
| Needs | node >=14.18 |
| Source | github.com/aymericzip/intlayer |
| Install scripts | @parcel/watcher, esbuild declare them. This runner does not run them. |
| Tarball | sha512-MwAP4tdUbWgDqLy3rATEAdAOJOFnreoLJYdQuJ1Xj/HBzBTwL9rvRvO1GtVInOvKOl8r5moFTym4U4frwA6d6w== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 9.8.1 | 2026-11-16 | Starts with no setup | 45 |
| 9.7.3 | 2026-11-12 | Starts with no setup | 39 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/%40intlayer/mcp)
New version out? Ask for a fresh report.