globalize.now
Localize your app: manage projects, languages and translation jobs
- Category
- Pending
- Primary Subcategory
- Pending
Integration details
Description
globalize.now is localization infrastructure for React, Next.js and Vue apps. Connect it to run your localization from Claude: list your projects and their target languages, add or remove languages, submit files for translation and pull back the results, manage glossaries and per-language style guides, and connect a GitHub repository so translations land in your repo as locale files. Translations live in your repository, not in a runtime widget. Every job uses your project's glossary, style guides and translation memory, so terminology stays consistent across languages. Supported formats include JSON (flat, nested, ARB, Chrome messages.json), PO, XLIFF 1.2 and 2.0, YAML, Android XML, iOS xcstrings, Markdown and HTML. Converting hardcoded strings in your code into i18n keys happens in the globalize.now app or via the agent skills; this connector covers everything after that.
- Integration type
- Connector
- Verification status
Community connector- Platform
- Claude
- Category
- Pending
- Primary Subcategory
- Pending
- Secondary Subcategories
- None listed
- Brand
- Unknown
- Access
- Account required
- First tracked
- 2026-09-24
- Tool count
- 21
- Geography
- US
The broad Category that contains the Primary Subcategory.
The Primary Subcategory used for this profile’s headline score.
Other Subcategories where the Integration is listed.
Claude Discoverability Score
Claude Connector discovery is coming soon
Community Connectors only appear in Claude’s registry.Once verified, organic discovery begins and we can calculate your score.Read more about Community Connector verification.
No spam. Unsubscribe any time.
No spam. Unsubscribe any time.
What discovery looks like

Claude can surface verified Connectors when they match a user’s Prompt.
How Claude Connector discovery works
Your Connector will compete to appear for users’ Prompts once Claude verifies it
Competitive lineup
21 tools agents can invoke
How do I improve a Community connector's discoverability?
The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.
Where is this profile measured?
This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.