WxO Agent MCP
Invoke a configured Watson Orchestrate enterprise agent from Claude Code or Cursor through MCP instead of custom REST glue.
Overview
WxO Agent MCP is a build-phase MCP server that connects AI assistants to IBM watsonx Orchestrate so you can invoke a configured agent via WO_AGENT_ID.
What is this MCP server?
- stdio MCP v1.0.8 (npm wxo-agent-mcp) to invoke Watson Orchestrate agents
- Configuration driven by WO_AGENT_ID (or WO_AGENT_IDs) plus instance URL
- Authenticates with secret WO_API_KEY against WO_INSTANCE_URL
- Bridges IDE agents to IBM Orchestrate—not a skill for writing prompts from scratch
- Single-purpose invoke tool for pre-built enterprise agents
- Server version 1.0.8 with stdio npm package identifier wxo-agent-mcp
- 3 required environment variables: WO_API_KEY, WO_INSTANCE_URL, WO_AGENT_ID
- Designed as invoke-only MCP for pre-configured Watson Orchestrate agents
What problem does it solve?
Calling Watson Orchestrate agents from your coding workflow usually means bespoke API scripts that fall out of sync with agent IDs and instance URLs.
Who is it for?
Teams with existing Watson Orchestrate agents who want those capabilities as MCP tools inside Claude Code or Cursor.
Skip if: Indie hackers without IBM Orchestrate tenancy who only need local Claude skills or open-weight models.
What do I get? / Deliverables
After MCP registration with WO_API_KEY and WO_INSTANCE_URL, your editor agent can invoke the specified Orchestrate agent on demand.
- MCP-accessible invocation of a configured Orchestrate agent
- Responses from WxO agents surfaced inside your coding session
- Reduced custom REST glue for Orchestrate calls
Recommended MCP Servers
Journey fit
Calling an orchestrated IBM agent from your dev environment is agent-tooling during product build, especially for composite AI workflows. WxO Agent MCP wraps Watson Orchestrate invocation so your coding agent can delegate to a managed WO_AGENT_ID in the same session.
How it compares
Watson Orchestrate agent invoke MCP, not an agent authoring framework or prompt marketplace.
Common Questions / FAQ
Who is WxO Agent MCP for?
It is for developers who already use IBM watsonx Orchestrate and want to invoke a specific agent from an MCP-enabled coding assistant.
When should I use WxO Agent MCP?
Use it when building agentic workflows that should delegate steps to a hosted Orchestrate agent identified by WO_AGENT_ID.
How do I add WxO Agent MCP to my agent?
Install wxo-agent-mcp from npm, add stdio MCP config with WO_API_KEY, WO_INSTANCE_URL, and required WO_AGENT_ID.