Shipi18n
Checks, compares, and reviews locale files from MCP-compatible coding clients.
Install Shipi18n
Pick your client, then add it in one click or paste the config.
~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": {
"shipi18n": {
"command": "npx",
"args": [
"-y",
"@shipi18n/cli"
]
}
}
}
Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.
We couldn’t confirm it starts correctly
The install command installed and started the server, which then stopped for configuration (such as an API key) that our sandbox does not have — expected for servers that connect to your account.
npx -y @shipi18n/cliNo response to initialize.
This is an experimental automated check and can have false negatives — missing environment variables, a slow cold install, etc. It doesn’t necessarily mean something’s wrong. Last checked Today.
Overview
Use cases
- Check locale changes before committing
- Review translation diffs in an AI coding session
- Find broken placeholders and plural forms
- Compare locale files for missing or extra keys
Key features
- Locale-file structural validation
- Translation diff inspection
- Optional semantic review
- Offline validation without an API key
- Support for multiple locale file formats
How Shipi18n works
Security & health
What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.
ActiveLast checked 2d ago
Recent health check succeeded.
6/6 checks healthy over the last 40d
Supply-chain signal
No high-severity advisories surfaced by our automated scan.
Critical 0High 0Medium 0Low 0
Scanned 15d ago via OSV.dev · @shipi18n/cli (npm)
Adoption & maintenance
Factual signals from GitHub, npm, and our automated checks — not a rating.
npm downloads3.2kPackage downloads in the last 30 days.
Last commit4d agoMost recent push to the default branch.
Install checkRunsOur sandbox started it; it then asked for an API key or config.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.
Reviews
No reviews yet — be the first to share how it worked for you.
Frequently Asked Questions about Shipi18n
shipi18n is an MCP server that connects AI coding clients to locale files and exposes tools for checking, diffing, and reviewing translations. Structural validation needs no API key, while semantic review uses a provider key supplied by the user. It is packaged as @shipi18n/mcp for Claude Desktop, Cursor, and other MCP clients.
Install or configure the @shipi18n/mcp package in an MCP-compatible client. The provided documentation names Claude Desktop and Cursor, but does not include a client-specific installation command or configuration example.
No API key is required for structural validation. Semantic review requires a key for the LLM provider selected by the user, and the broader project documents ANTHROPIC_API_KEY and OPENAI_API_KEY for that workflow.
It can detect structural issues including missing or orphaned keys, broken or renamed placeholders, incomplete plural forms, invalid ICU MessageFormat, duplicate JSON keys, empty strings, and untranslated values.
Related MCP servers
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.
AllMCPs Directory Badge
Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.
Badge Style:
Live Dynamic SVG Preview
Markdown (GitHub README)
[](https://allmcps.com/mcp/shipi18n)HTML Embed
<a href="https://allmcps.com/mcp/shipi18n"><img src="https://allmcps.com/api/badge/shipi18n?style=directory" alt="Shipi18n on AllMCPs" /></a>