Better I18NBetter I18N

Available Tools

MCP tools for translation and content management

Better i18n provides two MCP servers with focused toolsets. All project-scoped tools require a project parameter in org/project format (e.g., "aliosman-co/personal").

Translation Tools (@better-i18n/mcp)

Call listProjects first to discover available projects before using other tools.

Discovery Tools

Reading Tools

Writing Tools

Publish Tools

Production Impact: Publishing deploys changes to live CDN or GitHub. Always call getPendingChanges first to verify what will be deployed.

Sync Tools


Content Tools (@better-i18n/mcp-content)

These tools manage headless CMS content — models, entries, and localized content fields.

Content tools are in a separate MCP package. Install @better-i18n/mcp-content alongside @better-i18n/mcp if you use both translation and content features.

Model Tools

Field Tools

Entry Tools

Publish Tools


Best Practices

  1. Discover First: Start with listProjectsgetProject to understand the project.
  2. Find Gaps: Use listKeys to see all keys and find missing translations.
  3. Batch Operations: createKeys and updateKeys handle single and bulk operations efficiently.
  4. Source Text: Use updateKeys with isSource: true to update source text.
  5. Clean Up: Use deleteKeys to remove unused keys (soft delete until publish).
  6. Safe Publishing: Always call getPendingChanges before publishTranslations to verify changes.
  7. Track Deployment: Use getSync(syncId) to verify publish jobs completed successfully.
  8. Language Setup: Use proposeLanguages to add new languages, proposeLanguageEdits to change status (active/draft/archived).

On this page