@langapi/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LANGAPI_API_KEY | Yes | Your LangAPI API key (get one at https://langapi.io) | |
| LANGAPI_API_URL | No | Custom API URL (default: https://api.langapi.io) | https://api.langapi.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_local_localesA | Scan project for locale files (JSON, ARB, .strings, .xcstrings, .stringsdict), detect i18n framework (next-intl, i18next, react-intl, flutter, ios-macos, generic), and return structured information about available translations. |
| get_translation_statusB | Compare source locale against target locales to identify missing/outdated keys and estimate translation costs. |
| sync_translationsA | Add new languages or sync existing translations via LangAPI. The server compares each file's current content against its previous translation and only translates what's new or changed. Default is dry_run=true for preview. |
| get_account_statusA | Get the current LangAPI account status: plan (free/pro), the monthly word allowance and how much of it remains this period, the credit balance, and when the allowance resets. Use this to check remaining words/credits before syncing translations. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a clear, distinct purpose: scanning locales, comparing translation status, syncing translations, and checking account info. No two tools overlap in functionality.
All tool names follow a consistent verb_noun snake_case pattern (list_, get_, sync_, get_). The naming is uniform and predictable.
Four tools are well-scoped for a translation management server. Each tool covers a necessary step in the workflow without redundancy, and the count is within the ideal range.
The tool set covers the core lifecycle: discovering locales, checking status, syncing, and account monitoring. Minor gaps like translation history or manual key editing are absent, but these are not essential for the main workflow.