Manage IBM Watson Orchestrate tools, agents, connections from Cursor, Copilot, Claude.
Manage IBM Watson Orchestrate tools, agents, connections from Cursor, Copilot, Claude. That is what the watson orchestrate mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.
MCP server for IBM Watson Orchestrate (WXO). Manage tools, agents, connections, flows, and execute tools from Cursor, VS Code Copilot, Claude Desktop, Antigravity, Windsurf, or the WxO Builder extension.
The server publishes 4 tools. What each one is for:
Agents — The Agents tool exposed by this serverConnections — The Connections tool exposed by this serverFlows — The Flows tool exposed by this serverCursor — Config file: .cursor/mcp.json (project) or ~/.cursor/mcp.json (global). Uses mcpServers (not servers). Same command and args as aboveBecause this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.
Configuration is passed through the environment: WO_API_KEY, WO_INSTANCE_URL, WO_AGENT_ID, YOUR_APP_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Watson Orchestrate's toolset — Agents, Connections, Flows and 1 more — is a fair guide to whether it matches your workflow. It is maintained by markusvankempen; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against Watson Orchestrate's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| Agents | The Agents tool exposed by this server. |
| Connections | The Connections tool exposed by this server. |
| Flows | The Flows tool exposed by this server. |
| Cursor | Config file: **.cursor/mcp.json** (project) or ~/.cursor/mcp.json (global). Uses mcpServers (not servers). Same command and args as above. |
{
"mcpServers": {
"wxo-builder": {
"command": "npx",
"args": ["-y", "wxo-builder-mcp-server"],
"env": {
"WO_API_KEY": "your-value",
"WO_INSTANCE_URL": "your-value",
"WO_AGENT_ID": "your-value",
"YOUR_APP_ID": "your-value"
}
}
}
}Add to claude_desktop_config.json, then restart Claude Desktop.
| Variable | Description | Required |
|---|---|---|
| WO_API_KEY | Credential the server authenticates with. | Yes |
| WO_INSTANCE_URL | Endpoint or connection string the server talks to. | Yes |
| WO_AGENT_ID | Configuration value read at startup. | Optional |
| YOUR_APP_ID | Configuration value read at startup. | Optional |
Kill hallucinated APIs — version-accurate, up-to-date library documentation injected straight into context.
Microsoft's official browser automation server — drive a real browser through the accessibility tree, no screenshots needed.
GitHub's official server — repos, issues, pull requests, Actions and code security, straight from your assistant.
Issue tracking at the speed of conversation — Linear's official hosted server with OAuth and zero install.
Local repository surgery — status, diffs, commits, branches and history for any repo on disk.
Timezone sanity for AI — current time anywhere and correct conversions, without the model doing date math.