Localisation managers
Run requests, reviewers, vendors, and quality from one place, with a clear view of every locale.
For developers
AI coding agents
Localise from Claude Code, Codex, and Cursor
Connect your coding agent to Hyperlocalise over MCP. It can read projects, keys, and glossaries, start translation, and check status, all without leaving your editor.
The shift
From context switching to asking your agent
Today
- Adding a string means opening the TMS, finding the project, and uploading by hand.
- Your agent writes UI copy with no idea of your glossary or tone.
- Checking translation status means another tab and another login.
With Hyperlocalise
- Ask your agent to translate new strings, and it handles the round trip.
- The agent reads your glossary and guidelines before it writes copy.
- Status, jobs, and review items are one question away.
How it works
From one command to localisation in your editor
Connect once with OAuth. The agent works with your existing workspace permissions.
zsh
$claude mcp add -t http hyperlocalise https://hyperlocalise.com/mcp✓ Added HTTP MCP server hyperlocaliseOpening your browser to approve access…✓ Connected
Watch
See the platform in action
A short walkthrough of projects, review, automations, and agents working across markets.
Works with
Works in the agents your team already uses
Claude
OpenAI
GitHub
Slack
Phrase
Crowdin
Lokalise
Gemini
Key capabilities
Your workspace, available to your agent
Hosted MCP server
Connect Claude Code, Codex, or Cursor with one command and no infrastructure.
OAuth sign-in
Approve access in your browser. The agent gets your role, nothing more.
Projects, files, and keys
Read projects, source files, and translation keys from the workspace.
Glossaries and guidelines
Check copy against your glossary and guidelines before it is written.
Translation jobs
Start translation for any locale and poll it until it is done.
Review items
See what is blocked or waiting for review, and who owns it.
Example workflow
A settings page ships in four languages without leaving the editor
How one engineer adds a feature and its translations in the same session.
- 14:00
The feature is built
An engineer adds a new settings page with Cursor, including 9 new UI strings.
- 14:20
Copy follows the glossary
Before writing labels, the agent reads the glossary and uses the approved terms.
- 14:25
Translation starts
The agent starts translation for German, French, Japanese, and Spanish from the same chat.
- 16:00
Ready for review
The engineer asks for status, opens the review link for one flagged string, and opens the pull request.
Built for your role
One platform for everyone who takes you global
Localisation managers run the programme, growth teams open new markets, and developers ship the code. Find the workflow that matches your job.
International growth
Pick the right markets, launch campaigns there, and test what wins, with your brand intact in every language.
Developers
Keep localisation in Git, CI, and your coding agent, so missing or broken strings never reach production.
A few things you might ask.
Localisation from your coding agent.
Any more questions?
Contact usGive your coding agent your localisation workspace
Start free, connect Claude Code, Codex, or Cursor in one command, and ask your first question.