Intlpull
Manage translations, locales, and OTA i18n releases from the agent with Intlpull’s large MCP tool surface instead of juggling spreadsheets and manual exports.
Overview
io.github.intlpull/intlpull is a Build-phase MCP server for an AI-powered i18n platform with 50+ tools for translations, OTA releases, and locale management.
What is this MCP server?
- AI-powered i18n platform exposed as an MCP server with 50+ tools
- Covers translations workflow, OTA releases, and related locale operations
- npm @intlpullhq/mcp-server v0.2.1 over stdio for local agent clients
- Open-source repo at intlpullhq/intlpull on GitHub
- Suited to solo builders shipping multi-language SaaS or mobile from one agent session
- 50+ MCP tools per server description
- Package version 0.2.1
- npm identifier @intlpullhq/mcp-server
What problem does it solve?
Shipping multiple languages means endless copy-paste between repos, translation vendors, and release tooling the agent cannot see.
Who is it for?
Indie SaaS and mobile builders using Intlpull who want agents to manage locales and translation releases from the IDE.
Skip if: English-only hobby projects or teams that do not use Intlpull and only need occasional manual JSON locale edits.
What do I get? / Deliverables
After you wire the Intlpull MCP server, your agent can operate translations and OTA i18n workflows through a single stdio tool catalog.
- Agent-driven translation and locale operations via 50+ MCP tools
- OTA i18n release actions without custom scripts
- Integrated i18n workflow inside the coding agent session
Recommended MCP Servers
Journey fit
Build is where UI copy and locale coverage ship; internationalization is a product surface task before you optimize discovery on Launch. frontend matches shipping localized strings, locale files, and OTA translation updates that users see in the app or site.
How it compares
i18n platform MCP with 50+ tools, not a generic Google Translate wrapper or SEO localization skill.
Common Questions / FAQ
Who is intlpull for?
Solo builders and small teams on the Intlpull i18n platform who need Claude Code, Cursor, or similar agents to drive translations and OTA releases.
When should I use intlpull?
Use it during Build while you are adding locales, syncing keys, or shipping OTA translation updates before launch.
How do I add intlpull to my agent?
Install @intlpullhq/mcp-server from npm, configure Intlpull account/project access per Intlpull docs, add the stdio server entry in your MCP client, and restart the agent.