Skip to main content

Connect wxrks to Claude and other AI assistants

Connect Claude, Cursor, Codex, or opencode to your wxrks workspace to translate, search translation memory, check terminology, and review translations from a chat or your editor.

⚠️ Beta: MCP and CLI access to wxrks is in active development. You may see occasional errors, and the available tools can change without notice.

Connect Claude, Cursor, Codex, or opencode to your wxrks workspace so you can translate text, search your translation memories, check terminology, and get an AI review of a translation directly from a chat or your editor — using the same translation memory, glossary, machine translation, and Sous Chef AI settings as the wxrks Portal translator.
​

💡 Who is this for? This guide is for Account Admins who need to connect an AI assistant — Claude, Cursor, Codex, or opencode — to their wxrks workspace. Generating the API token this connection needs is controlled by a permission rather than tied to one specific role, so ask your Account Admin if you have access but don't see it.

What you can do once connected

Once wxrks is connected, your AI assistant can:
​

  • Translate text with your workspace's full context — translation memory hits, glossary terms, machine translation, and your Sous Chef AI instructions are all applied automatically, exactly like the wxrks Portal translator.

  • Search translation memory for existing translations similar to a piece of text, with a similarity threshold you control. See All about Translation Memories for how matching and threshold work.

  • Check terminology: verify that a translation uses your glossary terms, and flag forbidden or do-not-translate terms. See How to create a Glossary if you don't have one set up yet.

  • Review a translation with an AI quality check that returns severity ratings and a confidence score.

  • Detect the language of a piece of text, list your translation memories and glossaries, and confirm which wxrks user the connection is acting as.

Your AI assistant only ever has the access your wxrks user has — every call is enforced by wxrks' own permissions, the same as if you'd done it in the Portal yourself.

Before you start: get an API token

You'll need an API access key and secret for your wxrks user — the same credential pair used for the wxrks REST API. Follow API authentication to generate one from your Profile > Security tab. Keep both values somewhere safe: the secret is shown only once, and generating a new token invalidates the previous pair.
​

For a shared or automated integration (CI, a team bot), create a dedicated wxrks user and generate the token from that account instead of a real person's login.
​

Note your workspace's web address too: most workspaces use https://app.wxrks.com; European workspaces use https://eu.wxrks.com. (The wx CLI's own built-in default host, https://api.wxrks.com, is different from either — always enter the address you actually sign in at.)

Option A — Claude Desktop extension (recommended)

No terminal needed. Works on macOS and Windows with the Claude Desktop app.
​

  1. Download wxrks.mcpb from the latest release on the wxrks CLI releases page.

  2. Open the downloaded file. Claude Desktop opens its extension install dialog, showing the wxrks icon, description, and the 8 tools it adds.

Claude Desktop extension install dialog showing the wxrks icon, description, and the 8 tools it adds

  1. Click Install.

  2. Fill in the settings form: Workspace Host (your workspace address, see above), API access key, and API secret (the values from your wxrks Profile). These are stored in your operating system's keychain, not in a file.

Claude Desktop wxrks extension settings form with Workspace Host, API access key, and API secret fields

  1. Confirm the extension shows as enabled under Settings > Extensions.

First use

Open a new chat and check the tools menu in the composer — the wxrks tools are listed there.
​

Claude Desktop chat composer with the wxrks tools listed in the tools menu

The first time Claude uses a wxrks tool, it asks for your permission.
​

Claude Desktop permission prompt shown the first time a wxrks tool is used

Then just ask naturally:
​

  • "Who am I in wxrks?"

  • "Translate 'Release notes are ready for review' to Brazilian Portuguese and Japanese, formal tone."

  • "Search our translation memory for 'payment failed' in pt_br, threshold 0.75."

  • "Check this translation against our glossaries: source '...', target '...', English to German."

  • "Review this translation and tell me how confident you are in it."

Option B — the wx CLI (Claude Code, Codex, Cursor, opencode)

For developers and terminal users, the same tools ship inside the wx CLI.
​

Install the CLI:
​

  • macOS: brew install --cask wxrks-hq/tap/wx

  • Windows: scoop bucket add wxrks https://github.com/wxrks-hq/scoop-bucket, then scoop install wx

  • Linux / manual install: download the archive, .deb, or .rpm from the releases page

Configure it once (asks for host, access key, and secret):
​

wx init

Then register the MCP server with your client:
​

  • Claude Code: claude mcp add wxrks -- wx mcp

  • Claude Desktop / Cursor (manual JSON alternative):

{
  "mcpServers": {
    "wxrks": { "command": "wx", "args": ["mcp"] }
  }
}

  • opencode (opencode.json):

{
  "mcp": {
    "wxrks": { "type": "local", "command": ["wx", "mcp"], "enabled": true }
  }
}

  • Codex (OpenAI's ChatGPT desktop app, CLI, or IDE extension): codex mcp add wxrks -- wx mcp, or add this to ~/.codex/config.toml (one shared file for every local Codex surface; use the absolute path to wx):

[mcp_servers.wxrks]
command = "/absolute/path/to/wx"
args = ["mcp"]

To target another workspace or region, use wx mcp --profile <name> or --host <url>, or set the BW_HOST, BW_ACCESS_KEY, and BW_SECRET environment variables (useful for CI or containers).
​

The wx binary is also a full command-line client for the wxrks REST API — projects, tasks, translation memory, glossaries, billing, and more — beyond just running the MCP server. Run wx --help to see every command group.

Troubleshooting

  • "Invalid Credentials" or permission errors: the access key/secret pair is wrong or was regenerated since you saved it, or the Workspace Host doesn't match your region (European workspaces must use https://eu.wxrks.com). Generate a fresh token from your Profile and update the extension settings.

  • Extension shows as disconnected (Claude Desktop, macOS): check the log at ~/Library/Logs/Claude/mcp-server-wxrks.log. A healthy start logs something like wx mcp: serving 8 tools for <your host> (profile "default").

  • Reviewing a translation returns a server error: the AI review tool depends on a backend fix that may not have reached every workspace yet — the other tools are unaffected. Try again later, or contact support.

  • Windows warns when running wx.exe: the Windows binary isn't code-signed yet, so Windows SmartScreen may show a warning the first time you run it. This is expected, not a sign of a corrupted download.

  • Updating: install a newer wxrks.mcpb over the old one, or run brew upgrade wx / scoop update wx for the CLI. Uninstalling: Settings > Extensions > remove wxrks; your keychain-stored settings are removed with it.

Related articles

Related Articles
Did this answer your question?