MartechDB
MartechDB
Toggle sidebar

Lingo.dev MCP server

lingo.dev

Yes. Lingo.dev publishes an official MCP server at https://mcp.lingo.dev/main. It's hosted. It offers 4 tools. We last checked it on 22 Nov 2026.

Official MCP server
Hosted
Sign-in: see vendor docs

Official: published in the official MCP Registry as dev.lingo/main, a name only the owner of lingo.dev can publish under. Checked 22 Nov 2026. Maintained by Stuart Brameld.

Key facts

As of 22 Nov 2026, Lingo.dev's official MCP server scores 58/100 (provisional) on MartechDB's Agent Readiness Index (v1.1). It answered 55 of our 55 checks in the last 90 days and lists 4 tools.

How the Agent Readiness Index works · Wrong? Suggest a correction

Lingo.dev MCP server review

58/100

Lingo.dev's MCP server scores 58/100 on MartechDB's Agent Readiness Index: usable by AI agents, with gaps.

The good

  • Hosted by Lingo.dev: connect by URL, with nothing to install

  • Published to the official MCP Registry

  • Answered 100% of our checks in the last 90 days

  • Included in the plan, at no extra cost

The bad

  • Nothing we've found.

Not checked yet: how you sign in; a docs page listing its tools. Anything not checked scores nothing.

Official MCP server

Lingo.dev MCP server

Lingo.dev MCP Server - World-class i18n implementation with ICU MessageFormat.

Address
https://mcp.lingo.dev/main
Runs
Hosted
Sign-in
Sign-in: see vendor docs
Cost to use
Plan: Sandbox (Pay as you go)
Official MCP Registry
Listed as dev.lingo/main · published 17 Sep 2025
How we know it's official
  • Published in the official MCP Registry as dev.lingo/main, a name only the owner of lingo.dev can publish under.
Checked 22 Nov 2026.
Tools
4 tools · listed 16 Oct 2026
First seen
17 Sep 2025
Last checked
Reachable ·
16 Nov 2026: reachable
17 Nov 2026: reachable
18 Nov 2026: reachable
19 Nov 2026: reachable
20 Nov 2026: reachable
21 Nov 2026: reachable
22 Nov 2026: reachable
Uptime
100% · 55 of 55 checks reachable since 1 Oct 2026

Lingo.dev MCP server tools (4)

As the server lists them. Names and descriptions are the vendor's own.

  • 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(step_number=1, done=false) FIRST 2. The checklist will instruct you to call THIS tool 3. Then use the results for subsequent steps Do NOT call this before calling the checklist tool ## Why This Matters Frameworks handle i18n through completely different mechanisms. The same outcome (locale-aware routing) requires different code for Next.js vs TanStack Start vs React Router. Without accurate detection, you'll implement patterns that don't work. ## How to Use 1. Examine the user's project files (package.json, directories, config files) 2. Identify framework markers and version 3. Construct a detectionResults object matching the schema 4. Call this tool with your findings 5. Store the returned framework identifier for get_framework_docs calls The sche…

  • 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 you if you need to fetch docs and which sections to read. If you're implementing i18n: Let the checklist guide you. Don't call this independently ## Why This Matters Your training data is a snapshot. Framework APIs evolve. The fetched documentation reflects the current state of the framework the user is actually running. Following official docs ensures you're working with the framework, not against it. ## How to Use **Two-Phase Workflow:** 1. **Discovery** - Call with action="index" to see available sections 2. **Reading** - Call with action="read" and section_id to get full content **Parameters:** - framework: Use the exact value from get_project_context output - version: Use "latest" unless you need version-specific docs - action: "index" or "read"…

  • 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 setting up providers, translation APIs, and UI components. If you're implementing i18n: Let the checklist guide you. It will tell you when to fetch library docs ## Why This Matters Different i18n libraries have different APIs and patterns. Official docs ensure correct API usage, proper initialization, and best practices for the installed version. ## How to Use **Two-Phase Workflow:** 1. **Discovery** - Call with action="index" 2. **Reading** - Call with action="read" and section_id **Parameters:** - library: Currently only "react-intl" supported - version: Use "latest" - action: "index" or "read" - section_id: Required for action="read" **Example:** ``` get_i18n_library_docs(library="react-intl", action="index") get_i18n_library_docs(library="react-intl…

  • 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 these phrases:** - "set up i18n" - "add internationalization" - "implement localization" - "support multiple languages" - "add translations" - "make my app multilingual" - "add French/Spanish/etc support" - "implement i18n" - "configure internationalization" - "add locale support" - ANY request about supporting multiple languages **Recognition Pattern:** ``` User message contains: [i18n, internationalization, localization, multilingual, translations, locale, multiple languages] → YOU MUST call this tool as your FIRST ACTION → DO NOT explore the codebase first → DO NOT call other tools first → DO NOT plan the implementation first → IMMEDIATELY call: i18n_checklist(step_number=1, done=false) ``` ## Why This is Mandatory Without this tool, you will: ❌…

Connect your AI to Lingo.dev

Add the official Lingo.dev MCP server to Claude, ChatGPT or your editor.

Connect Lingo.dev MCP to Claude

Claude.ai and Claude Desktop

  1. Open Customize, then Connectors.

  2. Click +, then Add custom connector.

  3. Name it Lingo.dev, paste the address below and click Add.

Claude Code

Lingo.dev MCP server questions

Does Lingo.dev have an official MCP server?

Yes. Lingo.dev publishes its MCP server itself. It's in the official MCP Registry under Lingo.dev's own domain. MartechDB only lists servers a vendor publishes, never community copies.

What is the Lingo.dev MCP server URL?

The address is https://mcp.lingo.dev/main.

How do I connect Lingo.dev MCP to Claude, ChatGPT or Cursor?

In Claude, add https://mcp.lingo.dev/main as a custom connector (Customize, Connectors, Add custom connector). In Cursor, use the Add to Cursor link on MartechDB's page, or paste the JSON settings into your mcp.json. In Claude Code, run: claude mcp add --transport http lingodev https://mcp.lingo.dev/main

What can the Lingo.dev MCP server do?

It offers 4 tools: get_project_context, get_framework_docs, get_i18n_library_docs and i18n_checklist (as listed on 16 Oct 2026).

Is the Lingo.dev MCP server in the official MCP Registry?

Yes, as dev.lingo/main.

Is the Lingo.dev MCP server working?

Yes. It answered our most recent check. We last checked it on 22 Nov 2026.

What are the alternatives to Lingo.dev's MCP server?

In Affiliates & partners, the most agent-friendly alternatives with an official MCP server are Partnero (98/100), Crossbeam (94/100), Strackr (94/100), Synup (92/100) and Affise (91/100). Lingo.dev scores 58/100 on the same index.

Alternatives to Lingo.dev's MCP server

Vendors in Affiliates & partners with an official MCP server, the most agent-friendly first. Lingo.dev scores 58/100.

Compare all 26 Affiliates & partners vendors →

Use with AI

Connect your AI to MartechDB

Then ask it about Lingo.dev, or any of the 1,851 marketing tools with an official MCP server. Free, no sign-in.

Claude.ai and Claude Desktop

  1. Open Customize, then Connectors.

  2. Click +, then Add custom connector.

  3. Name it MartechDB, paste the address below and click Add. There's no sign-in.

The free plan allows one custom connector. On Team and Enterprise plans, an owner adds the connector first.

Show that your MCP server is verified

If you work at Lingo.dev, add this badge to your MCP docs or README. It's free, it's the same for every vendor, and it updates from our daily checks: it shows uptime while the server responds, and says so if it stops.

Official MCP server, verified by MartechDB
HTML
Markdown

Something wrong or out of date? Suggest a correction or email us, and we'll check it against the evidence. Every correction we make is listed on Corrections.