LangAPI.io 2.0 — Agentic i18n via MCP
Agentic i18n for Cursor/Claude — consistent locale syncing
Start new thread

LangAPI | Agentic i18n via MCP - Agentic i18n for Cursor/Claude — consistent locale syncing

by•
LangAPI is an Agentic i18n engine for MCP. Connect it to Cursor/Claude/VS Code to audit missing keys and sync translations across JSON and iOS .strings files with one command. Delta-sync translates only what changed, preserves formatting and key order, and protects variables like {{username}}. Pay-as-you-go credits (no subscriptions); your code stays local—only strings are sent.

Add a comment

Replies

Best
Maker
📌
Hi Product Hunt — I’m Dmitry, the maker of LangAPI. If you’ve tried “just ask Cursor/Claude to translate my locale JSON”, you’ve probably seen the same problems I did: * inconsistent terminology (“Dashboard” becomes 3 different things), * broken JSON/formatting (diff chaos), * variables getting translated ({{username}}, {0}, %s) and your app crashes. LangAPI is an MCP server that lets your AI assistant manage i18n like a reliable teammate: * Delta-sync: translate only missing/changed keys (not the entire file) * Format-preserving writes: key order/indentation stay stable for clean diffs * Variable-safe: placeholders stay untouched How to try it (2 minutes): 1. Get an API key (includes 1,000 free credits) 2. Add the MCP server to Cursor / Claude Desktop / Claude Code (npx @langapi/mcp-server) 3. Ask: “Which languages are missing keys?” → then “Sync all translations” Pricing is pay-as-you-go credits (no subscriptions; credits never expire). 
Security note: your code stays local — only text strings are sent for translation. I’d love feedback from anyone using next-intl / i18next / vue-i18n / Flutter ARB: what’s the most painful part of your i18n workflow today?