Capabilities

Once connected, your AI assistant can manage your entire 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 voices your organization owns.

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 whole voices from an engine. An engine reads one voice per locale, so a conflicting attach is refused rather than silently resolved.

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.

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. The underlying API still calls an individual rule an instruction.

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.

AI Reviewers#

Create and configure AI Reviewers that automatically evaluate localization quality. Define review criteria, select the evaluation model, and set sampling rates. Attach or detach scorers from specific engines.

Localization#

Run localizations directly through your engine - single requests with full context enrichment, or async batch jobs targeting up to 100 locales in one call. Also detect the language of arbitrary text. See Localize from the Editor for detailed workflows.

Observability#

Inspect request logs with full execution context - which model handled a request, token usage, duration, fallback status, and complete input/output. Retrieve AI Reviewer verdicts, glossary compliance reports, and rule adherence results per request. See Debug Localization Quality for the post-mortem workflow.

Engine provisioning#

Submit links and content to create a fully configured engine automatically - AI extracts a brand voice, glossary terms, and rules from your sources. See Provision Engines with AI for details.

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.

API keys#

Generate and revoke API keys for programmatic access to your localization engine.

Integration credentials#

Manage credentials for external integrations connected to your organization.

Team management#

Invite teammates to your organization and review pending invites. New invites grant admin access by default and trigger the standard invitation email; when the MCP session is authenticated with OAuth, the email shows the inviter's name.

Permissions and roles#

Manage role-based access control from the conversation: list roles and permissions, create custom roles, assign users to roles, manage per-engine access grants, and transfer organization ownership.

Audit logs#

Query the append-only history of state-changing actions in your organization - who changed what, when, from which IP. Filter by actor, target, action type, or time range.

AI agent threads#

Create and manage AI agent threads for automated localization debugging and issue resolution.

Next Steps#