# Locize MCP server

> Manage Locize translation projects, translation memory, glossary, styleguide and versions from an AI assistant.

- Listing: https://mcp.tc/i/locize
- Connect: use the server's own URL `https://mcp.locize.app` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Developer Tools](https://mcp.tc/c/developer-tools)
- Vendor: Locize
- Homepage: <https://www.locize.com/docs/integration/mcp>

## About

Connects AI assistants to Locize translation management projects. You can list projects, read draft and published translations, find missing translations, check coverage per version, language and namespace, and work with translation memory, glossary, styleguide and screenshot context.

The server is hosted at https://mcp.locize.app and uses streamable HTTP. Users sign in with a Locize account through OAuth in the browser, which creates a Personal Access Token in their profile. A Personal Access Token can also be passed as a Bearer token for scripts and CI.

## What it can do

- List Locize projects, branches and tenants
- Fetch draft and published translations with filters
- Find missing translations for a target language
- View translation coverage per version, language and namespace
- Use translation memory, glossary and styleguide context
- Work with project versions

## Example prompts

- "List my Locize projects and show translation coverage for each language."
- "Find missing German translations in the common namespace of my project."
- "Show translations in my project that still need review."
- "Fetch the published translations for the checkout namespace in French."

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http locize https://mcp.locize.app
```

2. Start Claude Code, type `/mcp`, pick **locize** and choose **Authenticate**. A browser window opens for the Locize sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **Locize** and paste this URL:

```url
https://mcp.locize.app
```

3. Click **Add**, then **Connect**, and sign in when Locize asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=Locize&connectorUrl=https%3A%2F%2Fmcp.locize.app>) (opens connector settings)

2. Check that the URL reads `https://mcp.locize.app` and click **Add**.

3. Click **Connect** and sign in when Locize asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://mcp.locize.app` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to Locize to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=locize&config=eyJ1cmwiOiJodHRwczovL21jcC5sb2NpemUuYXBwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "locize": {
      "url": "https://mcp.locize.app"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=locize&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fmcp.locize.app%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"locize","type":"http","url":"https://mcp.locize.app"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "locize": {
      "type": "http",
      "url": "https://mcp.locize.app"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "locize": {
      "serverUrl": "https://mcp.locize.app"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add locize --url https://mcp.locize.app
codex mcp login locize
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.locize]
url = "https://mcp.locize.app"
```

### Gemini CLI

```bash
gemini mcp add --transport http locize https://mcp.locize.app
```

Then, inside Gemini CLI, run `/mcp auth locize` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "locize": {
      "type": "http",
      "url": "https://mcp.locize.app"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://mcp.locize.app`.

## Details

- Server version: 2.0.0
- Last checked: 2026-11-17 (reachable, asks for credentials)
- Listed: 2026-10-08
- Updated: 2026-10-08

---
Source: https://mcp.tc/i/locize (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
