Main
dev.lingo/main is a MCP server that guides world-class i18n implementation using ICU MessageFormat via Lingo.dev.
About
dev.lingo/main is the Lingo.dev Model Context Protocol server that helps developers implement internationalization with ICU MessageFormat discipline instead of ad hoc string replacement. When you are in the build phase—especially frontend and integration subphases—you connect the remote streamable-http server at https://mcp.lingo.dev/main so Claude Code, Cursor, or Codex can follow Lingo.dev conventions while editing catalogs, refactoring UI copy, or wiring locale-aware components. The published manifest describes version 1.0.0 as world-class i18n with ICU MessageFormat, which matters for SaaS, mobile, and extension products that will add languages after the English MVP. It is an MCP integration tied to the Lingo.dev platform, not a generic translation API; you still own repository structure and CI, but the agent gets structured i18n guidance at invoke time.
- Lingo.dev MCP server focused on i18n implementation
- ICU MessageFormat-oriented workflows for correct plurals and variables
- Hosted streamable-http endpoint at mcp.lingo.dev/main
- Version 1.0.0 remote server registration
- Fits agent-assisted string and locale file changes during build
Main by the numbers
- Data as of Jul 7, 2026 (Skillselion catalog sync)
claude mcp add --transport http main https://mcp.lingo.dev/mainAdd your badge
Show developers this MCP server is listed on Skillselion. Paste this into your README.
| Transport | HTTP |
|---|---|
| Auth | None |
What it does
Implement production-grade i18n with ICU MessageFormat using Lingo.dev tooling exposed to your agent via MCP.
Who is it for?
Best when you're adding multi-language UI and want agent help aligned with ICU MessageFormat best practices.
Skip if: Projects with zero internationalization plans or teams that already run a mature TMS with no agent involvement.
What you get
Your agent can apply Lingo.dev i18n patterns and ICU-safe message definitions while you integrate locales into the codebase.
- ICU-compliant message definitions aligned with Lingo.dev guidance
- Agent-assisted updates to translation and locale integration files
- Clearer i18n implementation path before multilingual ship
By the numbers
- Server version 1.0.0
- Remote URL https://mcp.lingo.dev/main
- ICU MessageFormat emphasized in server description
Recommended MCP Servers
0piFree, 2hr expiry agent storage to cache contexts, bridge workflows, or dump data.
100Hires AI ATS & Recruitment SoftwareOfficial 100Hires MCP: AI ATS & Recruitment Software for candidates, jobs, applications, interviews.
123elec McpInterface MCP officielle du site marchand 123elec, catalogue, stock, panier, commandes.
1stayHotel booking MCP server.2
2D Assets MCPMCP server for generating advanced mock 2D PNG assets for game prototypes.43D MeshWeaverMesh spatial optimizer reducing geometric overhead in 3D assets.How it compares
Lingo.dev i18n MCP integration, not a general machine-translation or copywriting marketplace skill.
FAQ
Who is dev.lingo/main for?
Developers implementing locales in web or mobile apps who want Lingo.dev and ICU MessageFormat expertise inside their MCP-enabled agent.
When should I use dev.lingo/main?
Use it during build when adding translation files, refactoring UI strings, or validating ICU patterns before multilingual launch.
How do I add dev.lingo/main to my agent?
Register the streamable-http remote https://mcp.lingo.dev/main in your MCP client server configuration per Lingo.dev setup docs.