Skip to main content
Hyperlocalise hosts an MCP (Model Context Protocol) server so agents such as Claude Code, Codex, and Cursor can read projects, source files, translation keys, glossaries, jobs, and Board items from your workspace. The server uses OAuth with PKCE. After you approve access, the agent receives a bearer token scoped to one organization and your current membership role.

​
Connect an agent

Open your workspace Overview. The Connect your agent card shows setup snippets for Claude, Codex, and Cursor. The first connection opens a browser sign-in and consent flow. Pick the organization the agent should use. Codex may also require codex mcp login hyperlocalise after adding the server.
MCP auth is separate from organization API keys and personal access tokens. Agents authenticate through OAuth, not x-api-key.

​
Verify the connection

Ask your agent:
Confirm the agent returns projects from the intended workspace. Then ask it to list the source files in one project. An empty list can mean there is no content yet or your account lacks access; it does not by itself mean the connection failed.

​
Start a scoped task

Give the agent a project, source path, and target locale. Ask it to inspect status before starting translation so you can see whether the work already exists. Review generated output before approving or delivering it. Use the MCP tool reference for tool inputs, permissions, and detailed errors.

​
Access and troubleshooting

The session uses your current workspace membership and project access. API keys and personal access tokens do not replace the OAuth sign-in step. If a tool fails, keep its error code and follow the reference’s troubleshooting table.

​
Connect an external MCP server to an automation

To let a saved automation call a remote server, add an MCP Server connection in Integrations. Follow external MCP connections. This is a separate setup from connecting your agent to Hyperlocalise.

​
Next

Inspect available tools, configure language resources, or review translations.