Other · Local MCP server
WxO Agent MCP
Invoke a Watson Orchestrate agent via MCP. Configure with WO_AGENT_ID.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.markusvankempen/wxo-agent-mcp- Version
- 1.0.8
- Status
- Active
- Category
- other
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-02-22
- Updated
- 2026-02-22
- Publisher
- markusvankempen (GitHub) · 8 servers with pages here
- Website
- github.com/markusvankempen/wxo-agent-mcp#readme
- Repository
- github.com/markusvankempen/wxo-agent-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | wxo-agent-mcp | 1.0.8 | stdio |
How to connect WxO Agent MCP
WxO Agent MCP runs locally from a Node.js package published to the npm registry: wxo-agent-mcp version 1.0.8. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx — the usual command is npx -y wxo-agent-mcp@1.0.8. It reads these environment variables: WO_API_KEY (required, secret), WO_INSTANCE_URL (required) and WO_AGENT_ID (required); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"wxo-agent-mcp": {
"command": "npx",
"args": [
"-y",
"wxo-agent-mcp@1.0.8"
],
"env": {
"WO_API_KEY": "<secret>",
"WO_INSTANCE_URL": "<value>",
"WO_AGENT_ID": "<value>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More from markusvankempen (GitHub)
| Server | Runs |
|---|---|
| IBM Code Engine MCP ServerDeploy to IBM Code Engine from Cursor, Copilot, Claude & Cline. Build, push, deploy via MCP. | Local · stdio |
| IBM MaximoConnect AI assistants to IBM Maximo for API discovery, OSLC querying, and Carbon UI generation. | Local · stdio |
| Literature ClockA line for the current minute, from literature, copyright-free books, or an original voice. | Local · stdio |
| Quantum OpenQASM MCPIBM Quantum OpenQASM 2.0 MCP — list backends, submit QASM, poll jobs, get histograms. | Local · stdio |
| Slack ↔ WxO MCP GatewayLifts WxO Slack limits: every-message wake-up, multi-channel MCP. https://markusvankempen.github.io/. | Local · stdio |
| Watson OrchestrateManage IBM Watson Orchestrate tools, agents, connections from Cursor, Copilot, Claude. | Local · stdio |
| Zendesk MCPZendesk MCP: 14 tools for AI agents — create, search, assign, comment, and close support tickets. | Local · stdio |
More other servers
| Server | Runs |
|---|---|
| Writing Assistant Ai MCPWriting Assistant Ai tools for AI agents. Capabilities: generate headlines, score readability. | Local · stdio |
| WSENDERManage WhatsApp, Telegram and MAX mailings: audiences, drafts, moderation and sending. | Remote · HTTP |
| WSG CheckCheck websites against the W3C Web Sustainability Guidelines and look up the guidelines. | Local · stdio |
| Wsjtx MCPOperate WSJT-X (FT8/FT4/WSPR) from MCP clients over its UDP message protocol. | Local · stdio |
| WyrdExposes one granted folder to any AI client, read-only, behind a path-containment fence. | Local · stdio |
| WyrmLocal-first memory for AI agents: ground truths, failure firewall, negotiated recall over MCP. | Local · stdio |
| X Openapi Flow MCPOpenAPI lifecycle guard and MCP sidecar for policy-driven API orchestration. | Local · stdio |
| X-EGOHuman approval for irreversible AI agent actions, bound to the exact tool call by a passkey tap. | Remote · HTTP |