SimpleLocalize

@SimpleLocalize list all translation keys tagged 'onboarding' and show which languages are missing translations

Found 12 translation keys tagged 'onboarding' across your project. Complete translations exist for English (en) and Spanish (es). Missing translations: French (fr) is missing 7 keys including 'welcome.title' and 'step_2.description'; German (de) is missing 4 keys including 'complete.button' and 'skip.link'. All keys use the default namespace. You can filter by namespace or export these gaps as a CSV if needed.

This example combines Get Project Context with translation key queries to surface localization gaps. Requires API key with read access to translation keys and project metadata. The MCP returns structured data but doesn't automatically create missing translations—you'll need a follow-up prompt to generate or import them.

@SimpleLocalize create a new translation key 'dashboard.welcome_back' with English text 'Welcome back, {username}!' and mark it with tag 'dashboard-v2'

Translation key 'dashboard.welcome_back' created successfully in the default namespace. Added English (en) translation: 'Welcome back, {username}!'. Applied tag 'dashboard-v2' for organization. The key is now available in your project and will appear in the next export. Note: Other configured languages (es, fr, de) still need translations for this key—they're currently empty.

Demonstrates the Create Translation Key tool with metadata tagging. This is a write operation that immediately modifies your SimpleLocalize project. The MCP creates the key but doesn't auto-translate to other languages—you'll see gaps until you add those translations manually or via batch import. Requires API key with write permissions.

@SimpleLocalize export all translations for the 'production' environment as JSON files and give me the download URLs

Export initiated for production environment. Generated 4 downloadable snapshots: English (en) at https://cdn.simplelocalize.io/abc123/en.json (47 KB, 156 keys), Spanish (es) at https://cdn.simplelocalize.io/abc123/es.json (45 KB, 156 keys), French (fr) at https://cdn.simplelocalize.io/abc123/fr.json (41 KB, 149 keys), German (de) at https://cdn.simplelocalize.io/abc123/de.json (43 KB, 152 keys). URLs expire in 24 hours. The MCP returns URLs only—you'll need to download the files separately if you want to inspect content locally.

Uses Export Translations to create deployment-ready snapshots filtered by hosting environment. The MCP doesn't return file bytes—it generates temporary CDN URLs that you fetch yourself. Useful for CI/CD pipelines or auditing what's live in production. Requires read access and a valid environment name from your project configuration.

When SimpleLocalize beats spreadsheets for launch coordination

A 6-person product team shipping a web app in English, Spanish, and German hits the wall two weeks before launch: translations live in three Google Sheets, engineers are hard-coding keys, and nobody knows which strings are final. SimpleLocalize wins here because the Create Translation Keys tool lets non-technical PMs batch-upload 100 keys at once while devs pull live snapshots with Export Translations. The Get Project Context tool shows everyone the same language list and tag structure, so there's no key-name drift between design mocks and production. If your launch cadence is quarterly or slower, a spreadsheet still works. But if you're shipping features every sprint and translations lag by days, the API_KEY auth and 14-tool scope justify the setup cost. Book a 30-minute onboarding call to map your current key-naming convention to SimpleLocalize's namespace model before your next release.

Why SimpleLocalize falls short for support-team translation workflows

A 3-person support team at a SaaS company wants to translate 40 Zendesk macros into French and Portuguese. They're eyeing SimpleLocalize because it has translation-key management, but this scenario is borderline at best. The toolset is built for developer-driven workflows—Create Translation Key and Get Translation Key assume you're working with namespaces and structured keys, not freeform support copy. The team would spend more time learning the namespace model than they'd save over a simpler tool like Phrase or even a shared Notion doc. SimpleLocalize shines when engineers are in the loop and keys map to UI components. If your support team isn't committing code or syncing translations to a build pipeline, the 14-tool complexity is overkill. Save the API_KEY setup for product translation; use a lightweight copy-management tool for support macros instead.

When tag-based organization justifies SimpleLocalize for agency work

A 5-person dev agency builds white-label dashboards for healthcare clients. Each client gets a fork of the same React app, but translations vary by region and compliance requirements. The Create Tag and Delete Tag tools let the agency organize keys by client name and feature set, so handoff docs are clean and the client's internal team can filter keys without touching code. Export Translations generates per-client snapshots in JSON or CSV, and Get Project Context confirms which tags exist before the agency archives a project. The trade-off: if you're only managing one or two clients, tags are unnecessary overhead—just use separate SimpleLocalize projects. But once you hit three or more forks with overlapping translation sets, the tag system pays for itself in handoff clarity. Agencies billing $150+ per hour should budget two hours for initial tag-structure design and one hour per client onboarding.