globalize.now is now a connector in Claude's directory, which means you can run your app's localization from an ordinary Claude chat: translate the locale files you drop in, add a language, set the terms that must never be translated, and connect a GitHub repository so translations arrive in your repo as locale files. globalize.now is AI-powered localization infrastructure, and until this week reaching it from Claude meant pasting a server URL into a custom connector. Now it is one click in the directory, with a browser sign-in and no API key.
The listing went live on 24 September after Anthropic's automated review. Below is how to add it, what it can and cannot do, and eight requests worth trying in your first session.
What did we launch in Claude?
A listing for the globalize.now MCP server in Claude's connectors directory, published as a community connector under Code and Productivity. The server itself is not new; coding agents have used it since July. What changed is how you reach it. Before, you needed to know the endpoint and add it as a custom connector. Now anyone on Claude, Claude Desktop or the Claude mobile apps can find it by name and connect in under a minute.
The connector exposes 21 tools grouped into four jobs:
| Job | What Claude can do |
|---|---|
| Projects and languages | List projects, create one, add or remove target languages, set project-wide context |
| Translation | Submit files for translation as one job and pull back the translated files |
| Consistency | Add and remove glossary entries, write per-language style guides |
| Repository | Install the GitHub app, detect a repo's framework and locale paths, connect it, pick branches |
Every translation job uses the project's glossary, style guides, context and translation memory, so a term you fixed in March is still fixed in the file you translate today.
How do you add globalize.now to Claude?
It takes three steps and no configuration.
- Open the directory. In Claude, go to Customize, then Connectors, and click the plus button to browse. Search for globalize.now, or open the listing directly at claude.ai/directory/globalize-now.
- Connect and sign in. Click Connect. A browser window asks you to sign in to globalize.now and approve access. That is the whole authentication step. There is no key to generate, copy or rotate.
- Ask. Start a chat and say what you want. Claude picks the tools, and each tool call shows up in the conversation so you can see what it did.
If you work in Claude Code or Cursor instead, the same server is one command away. The developers page has the snippets, and our Claude Code guide covers the full agent workflow.
What can you ask Claude to do?
These eight requests cover what most teams do in a week. Each one is a sentence in the chat, not a screen in a dashboard.
1. Translate a file you drop into the chat
"Translate this en.json into German, Japanese and Arabic." Attach the file and the translated files come back in the same format.
We ran exactly that against a demo landing page we use for testing. The source was a nested JSON file with a placeholder and an ICU plural:
"invite": "Invite {name} to the crew",
"count": "{count, plural, one {# trip planned} other {# trips planned}}"
About a minute and a half later the job was done. The {name} placeholder survived in all three languages. More interesting is what happened to the plural. German kept one and other. Japanese, which does not inflect nouns for number, collapsed to a single other form. Arabic expanded to all six forms its grammar needs: zero, one, two, few, many and other. That is the part hand-rolled translation scripts usually get wrong, and it came back correct without anyone asking for it.
2. Add a language to a live project
"Add Japanese to the storefront project." Claude adds the target language, and from then on Japanese is part of every translation job for that project. If the repository is connected, the Japanese files arrive in a pull request like every other translation.
3. Lock the words that must never change
"Never translate 'Workspace', and always render 'checkout' as 'Kasse' in German." Claude writes both as glossary entries. Product names, plan names and feature names stay put across every language and every future job, which fixes the most common complaint about machine-translated UI text.
4. Set the voice, one language at a time
"French should use tu, not vous. German should use du." Style guides are per language, so formality, tone and conventions can differ where the markets differ. They apply to every run after that, whether you translate from Claude, from the app or on a push.
5. Tell it what the product is
"This is a sailing app for weekend crews. Keep nautical terms accurate and never translate the plan names." Project context is shared across all languages and holds up to 1,000 characters. The demo project in use case 1 carries exactly this kind of note, which is why helm, navigator and lookout came back as sailing roles, not generic job titles.
6. Connect a GitHub repository from the chat
"Connect my repo acme/web and translate into French and Spanish." Claude checks whether the globalize.now GitHub app is installed and, if not, gives you the install link to approve in your browser. It then detects the framework, the source language and where the locale files live, shows you what it found, and connects the repository on the branch you choose. From there, translations arrive as pull requests you review and merge. Nothing is committed to your main branch directly.
7. Translate content that is not UI strings
"Translate this changelog into Italian." Markdown and HTML are supported formats, so release notes, help articles and email templates go through the same project, glossary and style guides as the app itself. This is where the connector helps people who are not developers most. A product manager can ship localized release notes without opening an editor.
8. Handle mobile string files
"Here is our Localizable.xcstrings and strings.xml, add Portuguese." iOS string catalogs and Android XML are parsed natively, so the same chat covers the web app and both mobile apps.
What does the connector not do?
It does not rewrite your source code. If your app still has hardcoded English strings in its components, that is a one-time conversion: the strings become translation keys and locale files, delivered as a pull request. It runs in the globalize.now app when you connect a repository, or through our skills in a coding agent. The get-started guide walks through it. Once the keys exist, the connector handles everything after that.
It also does not replace your translation reviewers if you have them. It produces translations that follow your rules, quickly. If a regulated market needs a human sign-off, keep that step. The pull request is where it fits.
Who is this for?
Three kinds of people get the most out of it:
- Developers who already live in Claude. You plan in Claude, write code in Claude Code, and now the localization jobs sit in the same place. If you built the app with an agent, our guide to localizing a Claude Code app is the companion piece.
- Product and marketing people. Translating a release note, fixing a term or adding a market no longer needs an engineer to open a dashboard or run a script.
- Teams whose translations keep drifting. A glossary and style guides that apply everywhere are the fix for translation files that fall out of sync. The connector puts those rules one sentence away.
Is it safe to connect?
Yes. The connector signs in with OAuth and only acts with your own permissions, in your own workspace. You can disconnect it at any time from Claude's connector settings.
Where to start
If you already have a globalize.now project, add the connector and ask Claude to list your projects. Then try use case 1 with a real locale file. If you are new, create an account at app.globalize.now first, and the developers page shows the other ways to connect the same server.
globalize.now turns hardcoded app copy into translation-ready locale files and keeps them updated as you ship.
Try globalize.now free