main is an MCP server with 4 tools an agent can call, among them get_framework_docs, get_i18n_library_docs, get_project_context. It answers at https://mcp.lingo.dev/main over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 10 of 10 times since 5 September 2026; the last check, on 18 October 2026, succeeded.
Lingo.dev MCP Server - World-class i18n implementation with ICU MessageFormat.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
get_framework_docs | Retrieves authoritative documentation directly from the framework's official repository. ## When to Use **Called during i18n_checklist Steps 1-13.** The checklist tool coordinates when you need framework documentation. Each step will tell y Inputs: framework, version, action, section_id, context |
get_i18n_library_docs | Retrieves authoritative documentation for i18n libraries (currently react-intl). ## When to Use **Called during i18n_checklist Steps 7-10.** The checklist tool will tell you when you need i18n library documentation. Typically used when sett Inputs: library, version, action, section_id, context |
get_project_context | Captures the user's project architecture to inform i18n implementation strategy. ## When to Use **Called during i18n_checklist Step 1.** The checklist tool will tell you when to call this. If you're implementing i18n: 1. Call i18n_checklist Inputs: detectionResults, context |
i18n_checklist | ## ⚠️ MANDATORY TOOL FOR ALL I18N WORK ⚠️ THIS IS NOT OPTIONAL. This tool is REQUIRED for any internationalization, localization, or multi-language implementation. ## When to Use (MANDATORY) **ALWAYS use this tool when the user says ANY of Inputs: step_number, done, build_passing, evidence, context |
Every block below points at https://mcp.lingo.dev/main. Pick your client and copy.
claude mcp add --transport http main https://mcp.lingo.dev/main
{
"mcpServers": {
"main": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.lingo.dev/main"]
}
}
}{
"mcpServers": {
"main": {
"url": "https://mcp.lingo.dev/main"
}
}
}{
"servers": {
"main": {
"type": "http",
"url": "https://mcp.lingo.dev/main"
}
}
}{
"context_servers": {
"main": {
"url": "https://mcp.lingo.dev/main"
}
}
}{
"mcpServers": {
"main": {
"serverUrl": "https://mcp.lingo.dev/main"
}
}
}{
"mcpServers": {
"main": {
"url": "https://mcp.lingo.dev/main"
}
}
}name: main
version: 0.0.1
schema: v1
mcpServers:
- name: main
type: streamable-http
url: https://mcp.lingo.dev/main{
"mcpServers": {
"main": {
"httpUrl": "https://mcp.lingo.dev/main"
}
}
}{
"mcpServers": {
"main": {
"type": "http",
"url": "https://mcp.lingo.dev/main"
}
}
}{
"mcpServers": {
"main": {
"url": "https://mcp.lingo.dev/main"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.lingo.dev%2Fmain&type=streamable_http&id=main&name=main
It answered our last check on 18 October 2026 in 661 ms. Over 10 checks since 5 September 2026 it answered 10. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by lingo.dev and served from mcp.lingo.dev, the vendor's own domain: https://mcp.lingo.dev/main.
4, as returned by the server's own tools/list on 31 August 2026: get_framework_docs, get_i18n_library_docs, get_project_context, i18n_checklist.
It answered our last check on 18 October 2026 in 661 ms. Over 10 checks since 5 September 2026 it answered 10.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.lingo.dev/main. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: dev.lingo. Endpoint host: mcp.lingo.dev. ARD identifier: urn:air:dev.lingo:mcp:main.
First indexed 31 August 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.