There is no agent management here and no tool routing - the agent is chosen once in configuration, and everything after that is a message and a reply. That is the point: an agent that already has its instructions and tools becomes callable from Cursor, VS Code or Langflow without carrying the rest of the platform.
A small server that fronts a single Watson Orchestrate agent. The agent is fixed at configuration time; the server sends it messages and returns what it says.
- Send a message to the configured Watson Orchestrate agent and get its reply - the agent answers using its own tools and LLM
- The agent's raw configuration - name, tools and instructions - when the JSON itself is what you need
A Watson Orchestrate instance and an agent inside it. Three values identify them - WO_API_KEY, WO_INSTANCE_URL and WO_AGENT_ID - set as environment variables or in your MCP config. It installs from npm and runs over stdio.
One command plus a key — npx -y wxo-agent-mcp, then supply credentials