Capabilities

Max PrilutskiyCEO & Co-Founder3 min read

Once connected, your AI assistant can manage your localization engine configuration through natural language. This page lists every capability exposed through the MCP server.

Engine management#

Create, update, and inspect localization engines. Each engine has its own model configuration and applies the glossaries, rulesets, and brand voice your organization owns.

Configuration is organization-owned

Glossaries, rulesets, and brand voices live at organization level and reach an engine by attachment. Ask your assistant to attach an existing one rather than duplicating it, and the same configuration governs every engine that needs it.

Provisioning#

Fill an engine from your website. Your assistant can create a new engine and fill its glossary, ruleset, and brand voice, or fill an existing engine: only the missing resource types, or a new glossary or ruleset alongside the current ones. The source is your website or text you provide.

Your assistant can check progress while the job runs and reports each part as completed, skipped, or failed when it finishes. It can retry failed parts the engine still has no resource for. See Fill from your website.

Brand voice#

Define how your product speaks in each locale. A brand voice is one object carrying a text per target locale - formal German ("Sie"), informal Italian ("tu"), any per-locale tone. Your assistant can create voices, add or edit a locale's text, and attach or detach a voice on an engine. An engine applies one voice at a time.

Glossary#

Add terms that must be localized exactly - or not localized at all. When you tell your assistant "make sure '911' localizes to '112' in German," it creates the glossary term immediately, in a glossary the engine applies. Terms are matched during localization via semantic similarity, so exact phrasing in source content doesn't need to match the term verbatim. Your assistant can also add, edit, or delete many terms at once.

Rules#

Encode linguistic conventions that generic models miss. Space before percentage signs in French, adjective positioning in Spanish, pronoun formality per market. Your assistant adds these as locale-scoped rules inside a ruleset, and every engine applying that ruleset follows them. It can also attach ready-made rules from the predefined catalog curated by Lingo.dev.

LLM model configuration#

Configure which model handles each locale pair, with ranked fallbacks. Assign Claude for European languages, GPT for CJK, or any combination - your assistant manages the full model routing table.

Available models#

List all LLM models available for assignment to your engine's model chains. Your assistant can query this to know what options exist before configuring a locale pair.

Engine suggestions#

Let the engine propose its own improvements - glossary terms, rules, and brand voice texts - from reviewer corrections, low answers from your custom measurements, or feedback you paste in. Your assistant lists the suggestions with the model's reasoning, and applies or dismisses them on your call. See Engine suggestions.

Measurements#

Set up the checks that review your translations. Your assistant can list built-in and custom measurements, create or edit a custom one, choose the events, languages, engines, and sample it runs on, turn it on or off, and read its answers.

Reports#

Ask about your translation activity: your assistant queries events and measurement answers by language, engine, model, repository, and more, and can create, update, or delete the organization's saved reports.

API keys#

Generate and revoke API keys for programmatic access to your localization engine - personal keys that act as you, and service keys with their own role and engine scope.

Your own provider keys#

Switch your organization's own key for an AI provider on or off (BYOK). While the key is on, localization with that provider's models runs on your key. While it is off, it uses your Lingo.dev credits. The stored key is kept either way. Your assistant can only switch a key already added on Settings → BYOK. Adding, replacing, and removing a key stay in the web app.

Team management#

Invite teammates to your organization, review and revoke pending invites, and remove members.

Permissions and roles#

Manage role-based access control from the conversation: list roles and permissions, create custom roles, assign roles to members and invites, and transfer organization ownership.

Knowledge base#

Ask how to do something in Lingo.dev, or how localization should be done in general, and your assistant searches the Lingo.dev docs and guides and reads the relevant page.

Feedback#

Ask your assistant to send feedback or report a problem, and it passes it to the Lingo.dev team.

Next Steps#