Simple MCP (Model Context Protocol) server that **invokes a single Watson Orchestrate agent** remotely. The agent is defined once via environment
If you already use Wxo Agent MCP, the wxo agent mcp mcp server is the piece that lets your assistant work with it directly. Simple MCP (Model Context Protocol) server that invokes a single Watson Orchestrate agent remotely. The agent is defined once via environment variables or MCP config.
Installation goes through your MCP client rather than a global install: point it at npm on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
invoke_agent — Send a message to the configured Watson Orchestrate agent. The agent responds using its tools and LLMget_agent — Get details of the configured agent (name, description, tools, instructions)Architecture — The Architecture tool exposed by this serverVerify — The Verify tool exposed by this serverAntigravity — Same config as Cursor. Copy examples/antigravity-mcp.json or add to your MCP config:Configuration is passed through the environment: WO_API_KEY, WO_INSTANCE_URL, WO_AGENT_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 AI and media services 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. Wxo Agent MCP's toolset — invoke_agent, get_agent, Architecture and 2 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.
SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.
| Tool | What it does |
|---|---|
| invoke_agent | Send a message to the configured Watson Orchestrate agent. The agent responds using its tools and LLM. |
| get_agent | Get details of the configured agent (name, description, tools, instructions). |
| Architecture | The Architecture tool exposed by this server. |
| Verify | The Verify tool exposed by this server. |
| Antigravity | Same config as Cursor. Copy examples/antigravity-mcp.json or add to your MCP config: |
{
"mcpServers": {
"wxo-agent": {
"command": "npx",
"args": ["-y", "wxo-agent-mcp"],
"env": {
"WO_API_KEY": "your-api-key",
"WO_INSTANCE_URL": "https://xxx.orchestrate.ibm.com",
"WO_AGENT_ID": "your-agent-id"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| 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 |
Build a programmable telecommunications stack for connecting telephony services with the Internet via a cloud-based utility.
Search built for AI, not humans — semantic web search that returns model-ready content, plus code context.
Answers, not links — delegate questions to Perplexity's search-grounded models and get cited responses back.
Give your assistant a voice — text-to-speech, voice cloning and audio tools from the ElevenLabs API.
Give your assistant a real code sandbox — isolated cloud VMs for actually running the code it writes.
The ML hub in your context window — search models, datasets, papers and run Spaces from the official server.