mcp
Connect a client
Register wx mcp as a local (stdio) MCP server in your client. It signs in with the default profile saved by wx init, or with the BW_HOST, BW_ACCESS_KEY and BW_SECRET environment variables (see Configure wx).
Claude Desktop
- Download
wxrks.mcpbfrom the latest wx release. - Open it with Claude Desktop and install it.
- Fill in your workspace host, access key and secret. Claude Desktop keeps the key and secret in the operating system's keychain.
The bundle carries its own wx for macOS and Windows, so you do not need to install the CLI.
Claude Code
claude mcp add wxrks -- wx mcp
To use another saved profile: claude mcp add wxrks -- wx mcp --profile eu.
Cursor
In .cursor/mcp.json for one project, or ~/.cursor/mcp.json for all of them:
{
"mcpServers": {
"wxrks": { "command": "wx", "args": ["mcp"] }
}
}
The same entry works in Claude Desktop's claude_desktop_config.json if you run your installed wx instead of the bundle.
opencode
In opencode.json:
{
"mcp": {
"wxrks": { "type": "local", "command": ["wx", "mcp"] }
}
}
Other clients
Any client that runs local MCP servers takes the command wx with the argument mcp. The credentials can go in the server's environment instead of a profile:
{
"command": "wx",
"args": ["mcp"],
"env": { "BW_HOST": "https://app.wxrks.com", "BW_ACCESS_KEY": "<access key>", "BW_SECRET": "<secret>" }
}
Troubleshooting
- The client cannot find wx. Desktop apps do not always see your shell's
PATH. Use the full path thatwhich wxprints (where wxon Windows) as the command. - Which user is it? Ask the assistant to call
whoami. It answers with the wxrks user the tools act as. - A tool fails with
BWX-403. The API user lacks the permission behind that tool (see Errors).