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
- Discover First: Start with
listProjects→getProjectto understand the project. - Find Gaps: Use
listKeysto see all keys and find missing translations. - Batch Operations:
createKeysandupdateKeyshandle single and bulk operations efficiently. - Source Text: Use
updateKeyswithisSource: trueto update source text. - Clean Up: Use
deleteKeysto remove unused keys (soft delete until publish). - Safe Publishing: Always call
getPendingChangesbeforepublishTranslationsto verify changes. - Track Deployment: Use
getSync(syncId)to verify publish jobs completed successfully. - Language Setup: Use
proposeLanguagesto add new languages,proposeLanguageEditsto change status (active/draft/archived).