I18n Agent
Localize your app copy across dozens of languages with context-aware AI translation directly from your coding agent.
Overview
ai.i18nagent/i18n-agent is a MCP server for the Build phase that provides context-aware AI translation across 48 languages for agent-driven localization.
What is this MCP server?
- AI-powered translation for 48 languages with context-aware quality (v1.16.3).
- Hosted streamable-http remote at https://mcp.i18nagent.ai/mcp plus npm @i18n-agent/mcp-client for stdio.
- Requires I18N_AGENT_API_KEY from app.i18nagent.ai; optional MCP_SERVER_URL env for client routing.
- GitHub source: i18n-agent/mcp-client for reproducible local installs.
- Keeps localization inside the agent loop instead of copy-pasting into standalone translation UIs.
- Version 1.16.3
- 48 languages supported per registry description
- npm package @i18n-agent/mcp-client; remote https://mcp.i18nagent.ai/mcp
What problem does it solve?
Indie builders delay global launches because moving strings through manual translation tools disconnects from the repo and the agent.
Who is it for?
Solo builders adding multi-language UI and marketing copy who want MCP-native translation with a hosted or npm stdio client.
Skip if: Teams that require fully offline translation, certified legal localization only, or no third-party translation API.
What do I get? / Deliverables
After you add the API key and MCP client, your agent can produce localized strings and content with i18n-agent quality controls in-session.
- Agent-invokable translations across up to forty-eight languages
- stdio or streamable-http MCP integration paths
- Faster locale updates aligned with your codebase workflow
Recommended MCP Servers
Journey fit
Internationalization is most often tackled during Build when UI strings, locales, and product copy are implemented. Frontend shelf fits because i18n-agent primarily serves string catalogs, UI localization, and locale expansion workflows.
How it compares
AI localization MCP service, not a static i18n framework skill or database connector.
Common Questions / FAQ
Who is ai.i18nagent/I18n Agent for?
Solo builders and small teams localizing apps or content who already use MCP clients and want forty-eight-language AI translation with an API key.
When should I use ai.i18nagent/I18n Agent?
Use it during Build frontend work when adding locales, and again at Launch or Grow when expanding languages for distribution and content.
How do I add ai.i18nagent/I18n Agent to my agent?
Create an API key at app.i18nagent.ai, install @I18n Agent/mcp-client for stdio or point your client to https://mcp.i18nagent.ai/mcp, and set I18N_AGENT_API_KEY (plus MCP_SERVER_URL if needed).