Beta version: This feature is currently in Beta and subject to ongoing improvements. As we continue to refine the functionality, you may experience occasional issues or unexpected behavior

Using wxrks inside Claude

This guide shows how to connect your wxrks workspace to Claude, so you can translate, search your translation memories, check terminology and review translations directly from a Claude conversation.

Once connected, Claude can:

Translate text with your workspace's full context — translation memories, glossaries, machine translation and your Sous Chef AI instructions are applied automatically, exactly like the wxrks Portal translator.
Search translation memories for existing translations similar to a text, with a similarity threshold you control.
Check terminology: verify that a translation uses your glossary terms, and flag forbidden or do-not-translate terms.
Review translations with an AI quality review (severity ratings and a confidence score).
Detect languages, list your TMs and glossaries, and confirm which wxrks user it is acting as.

Claude only ever has the access your wxrks user has — permissions are enforced by wxrks on every call.

Before you start: get an API token

Sign in to wxrks and open Profile.
Find the API Token card in security tab and generate a token. You get two values: an access key and a secret.

Keep both values somewhere safe:

The secret is shown only once. Generating a new token invalidates the previous one.
The token acts as you, with your permissions. For team or shared setups, create a dedicated wxrks user for the integration and generate the token from that account.
Note your workspace address too: most workspaces use https://app.wxrks.com; European workspaces use https://eu.wxrks.com.

Option A - Claude Desktop extension (recommended)

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

Download wxrks.mcpb from the latest release on the wxrks CLI releases page.
Open the extensions settings in Claude Desktop.
Install Extension

Claude Desktop shows what the extension does and which tools it adds. Click Install.

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

Confirm the extension appears enabled under Settings -> Extensions.

First use

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

The first

time Claude uses a wxrks tool it asks for your permission.

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: download the archive or deb/rpm from the releases page

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

wx init

Then register the MCP server in 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 - ChatGPT desktop app, CLI or IDE extension): codex mcp add wxrks -- wx mcp, or add this to ~/.codex/config.toml (one shared file for all local Codex surfaces; 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 BW_HOST, BW_ACCESS_KEY and BW_SECRET environment variables (useful for CI).

Troubleshooting

"Invalid Credentials" or permission errors: the access key/secret pair is wrong or was regenerated since you saved it, or the Workspace Host does not match your region (EU workspaces must use https://eu.wxrks.com). Generate a fresh token in My Account 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 wx mcp: serving 8 tools for <your host>.
AI translation review returns a server error: your workspace may not have the ad-hoc review feature enabled yet — the other tools are unaffected. Try again after your workspace updates, or contact support.
Windows warns when running wx.exe: the Windows binary is not code-signed yet; this is expected. The macOS binary is signed and notarized.
Updating: install a newer wxrks.mcpb over the old one (or brew upgrade wx for the CLI). Uninstalling: Settings -> Extensions -> remove wxrks; your keychain-stored settings are removed with it.

MCP and CLI for wxrks