MCP integration

The Model Context Protocol connects an AI assistant to ReRune through a remote HTTP endpoint. Your client discovers the available tools, then sends a structured request when the assistant needs to read or update localisation data. ReRune checks your API key and current permissions on every request and applies the same business rules as the dashboard and CLI.

Use a client that supports Streamable HTTP and custom authentication headers. The client handles protocol initialization and version compatibility. Connect directly to the hosted endpoint; no ReRune MCP package or local server process is required. Authentication currently uses API keys only.

Sign in to ReRune, open API keys, and create a named key for your MCP client. Copy the generated value and replace YOUR_RERUNE_API_KEY in the example for your client. Use a management API key rather than an OTA Publish ID.

• Open API keys in ReRune

The key acts as your ReRune account. It can access projects through your organisation memberships and perform only the operations your assigned permissions allow. Revoking a key stops subsequent MCP requests; changes to your permissions also apply to subsequent operations.

Add this to your personal ~/.codex/config.toml, replacing the API-key placeholder. The configuration is shared by the Codex CLI and IDE extension.

[mcp_servers.rerune]
url = "https://rerune.io/mcp"
tool_timeout_sec = 300

[mcp_servers.rerune.http_headers]
"X-API-Key" = "YOUR_RERUNE_API_KEY"

Restart Codex, then run codex mcp list or use /mcp in the CLI to inspect the connection and available tools.

• Official client setup reference

Replace the API-key placeholder and run this command in your terminal. User scope makes ReRune available across your projects.

claude mcp add --transport http --scope user rerune \
  https://rerune.io/mcp \
  --header "X-API-Key: YOUR_RERUNE_API_KEY"

Run claude mcp get rerune, then use /mcp inside Claude Code to check the connection and available tools.

• Official client setup reference

Add this server to your personal ~/.cursor/mcp.json, merging it with any existing mcpServers entries and replacing the API-key placeholder.

{
  "mcpServers": {
    "rerune": {
      "url": "https://rerune.io/mcp",
      "headers": {
        "X-API-Key": "YOUR_RERUNE_API_KEY"
      }
    }
  }
}

Save the file and restart Cursor. Open Agent chat and ask it to use ReRune to list your projects.

• Official client setup reference

Run MCP: Open User Configuration from the VS Code Command Palette. Add this server to the opened mcp.json, merging existing servers and replacing the API-key placeholder.

{
  "servers": {
    "rerune": {
      "type": "http",
      "url": "https://rerune.io/mcp",
      "headers": {
        "X-API-Key": "YOUR_RERUNE_API_KEY"
      }
    }
  }
}

Run MCP: List Servers and start ReRune. In Copilot chat, select an agent, enable the ReRune tools, and ask it to list your projects.

• Official client setup reference

Add this server to your personal ~/.config/opencode/opencode.json, merging existing mcp entries and replacing the API-key placeholder. Keep oauth set to false for API-key authentication.

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rerune": {
      "type": "remote",
      "url": "https://rerune.io/mcp",
      "enabled": true,
      "oauth": false,
      "headers": {
        "X-API-Key": "YOUR_RERUNE_API_KEY"
      }
    }
  }
}

Restart OpenCode and run opencode mcp list to check the connection. Ask the agent to use ReRune to list your projects.

• Official client setup reference

Use a recent Pi release with built-in MCP support. Add this server to your personal ~/.pi/agent/mcp.json, merging existing mcpServers entries and replacing the API-key placeholder.

{
  "mcpServers": {
    "rerune": {
      "url": "https://rerune.io/mcp",
      "timeout": 300,
      "headers": {
        "X-API-Key": "YOUR_RERUNE_API_KEY"
      }
    }
  }
}

Run pi mcp list to check the connection. In Pi, run /reload after changing the file, use /mcp to inspect ReRune, and ask it to list your projects.

• Official client setup reference

Once connected, describe the task in chat. Start by listing your accessible projects so the assistant can use the returned project and key IDs. Each client controls its own tool approval prompts; ReRune still checks permissions independently.

1. Ask: Use ReRune to list my accessible projects.
2. Ask: Show the draft translations in my website project.
3. Ask: Update the German draft for welcome.title to Willkommen.
4. After reviewing the changes, ask: Publish those updated keys with the tag release-1.2.

For integrations that call tools directly, these examples show the tools/call parameters. Replace the sample IDs with IDs returned by ReRune. Your MCP client or SDK handles the surrounding protocol request.

{
  "name": "save_translation_value",
  "arguments": {
    "key_id": "0123456789abcdef01234567",
    "translation": {
      "lang": "de",
      "value": "Willkommen"
    }
  }
}

{
  "name": "publish_translation_keys",
  "arguments": {
    "project_id": "0123456789abcdef01234567",
    "publication": {
      "key_ids": [
        "abcdef0123456789abcdef01"
      ],
      "tag": "release-1.2"
    }
  }
}

Tool results include structuredContent with status, data, and an optional message. The status matches the existing operation's HTTP status. A failed operation sets isError to true and can include partial publication results. Check the tool result as well as the HTTP response: a successful protocol request can carry an operation error. Use tools/list for the current input and output schemas; unknown input fields are rejected.

ReRune exposes 58 tools. The groups below list every tool name. Client discovery provides each tool's description, required inputs, output schema, and read or write annotations.

Organisation membership is the project access boundary. Owners do not bypass membership or assigned permissions. Read access and write access remain separate. The main permission requirements are listed below; existing billing capacity and conflict rules still apply.

Project-language configuration applies immediately and forces full SDK synchronization. Creating translation keys does not accept variations; add them to individual language values afterward. Owner removal and owner permission changes remain prohibited.

File tools accept exactly one of content for text or base64 for binary data, with an optional filename. They do not read paths on the server or fetch a URL. The assistant must supply the actual file content.

Generated and exported files return filename, contentType, size, and base64. The client can decode base64 and save the file locally. Import saves drafts; parse and generate do not save anything.

Export reads drafts by default. Set published to true for current published snapshots. The optional variation selects that frozen variation value with same-language Main content fallback.

• HTTP 401: check that X-API-Key contains a valid, unrevoked ReRune API key. Bearer tokens and keys in query parameters do not authenticate MCP requests.
• Tool status 403: the account lacks organisation membership or the operation's required permission. HTTP 403 from a browser client can instead indicate an untrusted origin.
• HTTP 405: opening /mcp as a web page sends GET. Use an MCP client with Streamable HTTP; standalone GET streams and session deletion are unavailable.
• HTTP or tool status 429: the request or tool-execution rate limit was reached. Wait before retrying. Each tool in a legacy batch counts separately.
• Input validation error: use tools/list to inspect the tool schema. Check required fields, 24-character MongoDB IDs, publication tags, and whether file content or base64 was provided exclusively.
• Client timeout during publish-all: allow up to 300 seconds for the tool in your client. The server uses its configured publish-all deadline and can return partial results. Ordinary calls use the server's normal request deadline.

The MCP request envelope allows 16 MiB; converted operation bodies, including multipart overhead, allow 10 MiB. HTTP requests and tool executions each have a separate limit of 120 per IP per minute.

For a browser-based inspector, the server must trust that browser's exact origin. Desktop clients do not require a browser-origin setting. A client that supports only OAuth without a custom X-API-Key header cannot connect to this API-key-only release.