
Company News
Free Business Plan Upgrades for Open Source Maintainers
Open source maintainers are under more pressure than ever. We're raising our open source program from the Team plan to the Business plan, free.
Simple MCP server to invoke a single Watson Orchestrate agent remotely. Configure agent via env (WO_AGENT_ID).
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.
Use this when you want a lightweight MCP that only chats with one agent—no tool management, no agent listing, no flows. Just invoke_agent(message) and get_agent().
Full documentation: DOCUMENTATION.md (includes screenshots for VS Code and Langflow).
┌───────────────────────────────────────┐
│ Cursor • VS Code • Langflow • etc. │
│ (MCP clients) │
└──────────────────┬───────────────────┘
│ stdio / JSON-RPC
▼
┌───────────────────────────────────────┐
│ wxo-agent-mcp │
│ invoke_agent • get_agent │
└──────────────────┬───────────────────┘
│ HTTP / REST
▼
┌───────────────────────────────────────┐
│ Watson Orchestrate │
│ agent + tools + LLM │
└───────────────────────────────────────┘
| Tool | Description |
|---|---|
| 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). |
Set these in .env or your MCP client config (e.g. Cursor mcp.json):
WO_API_KEY=your-ibm-cloud-api-key
WO_INSTANCE_URL=https://your-instance-id.orchestrate.ibm.com
WO_AGENT_ID=your-agent-id
# Or WO_AGENT_IDs=id1,id2 (first is used)
npm install
npm run build
cp .env.example .env
# Edit .env with your credentials and agent ID
WO_API_KEY=... WO_INSTANCE_URL=... WO_AGENT_ID=... node dist/index.js
# Default question ("Hello, who are you?")
WO_API_KEY=... WO_INSTANCE_URL=... WO_AGENT_IDs=... npm run test:verify
# Custom question
npm run test:verify -- -ask "What is the weather in Amsterdam?"
Runs get_agent and invoke_agent to confirm connectivity.
wxo-agent-mcp folder in VS Code.npm run build..vscode/mcp.json registers the MCP server as wxo-agent and loads .env.get_agent first.npm run test:verify from the terminal (Ctrl+`).See DOCUMENTATION.md for more prompts and setup.
Question examples: Full list →
| invoke_agent | get_agent |
|---|---|
| What is the weather in Amsterdam? | Use get_agent to show agent details |
| Tell me a dad joke | What tools does my agent have? |
| What time is it in Tokyo? | |
| What can you help me with? |
Langflow: Add an MCP Tools component, choose STDIO, set Command=node, Args=["/path/to/dist/index.js"], and env vars. See DOCUMENTATION.md.
Add to Cursor — Opens the Cursor Directory page. After adding, set WO_API_KEY, WO_INSTANCE_URL, and WO_AGENT_ID in Cursor MCP settings.
For cursor.directory/mcp/new submission:
| Field | Value |
|---|---|
| Cursor Deep Link | cursor://anysphere.cursor-deeplink/mcp/install?name=WxO%20Agent%20MCP&config=eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsInd4by1hZ2VudCJdLCJlbnYiOnsiV09fQVBJX0tFWSI6InlvdXItYXBpLWtleSIsIldPX0lOU1RBTkNFX1VSTCI6Imh0dHBzOi8veW91ci1pbnN0YW5jZS5vcmNoZXN0cmF0ZS5pYm0uY29tIiwiV09fQUdFTlRfSUQiOiJ5b3VyLWFnZW50LWlkIn19 |
| Install instructions | https://github.com/markusvankempen/wxo-agent-mcp#mcp-client-configuration |
.cursor/mcp.json){
"mcpServers": {
"wxo-agent": {
"command": "npx",
"args": ["-y", "wxo-agent"],
"env": {
"WO_API_KEY": "your-api-key",
"WO_INSTANCE_URL": "https://xxx.orchestrate.ibm.com",
"WO_AGENT_ID": "your-agent-id"
}
}
}
}
.vscode/mcp.json)The server is named wxo-agent. Use envFile to load .env:
{
"servers": {
"wxo-agent": {
"type": "stdio",
"command": "node",
"args": ["${workspaceFolder}/dist/index.js"],
"envFile": "${workspaceFolder}/.env"
}
}
}
For npx (after publishing), use "command": "npx", "args": ["-y", "wxo-agent"], and add env with your credentials.
Same config as Cursor. Copy examples/antigravity-mcp.json or add to your MCP config:
{
"mcpServers": {
"wxo-agent": {
"command": "npx",
"args": ["-y", "wxo-agent"],
"env": {
"WO_API_KEY": "your-api-key",
"WO_INSTANCE_URL": "https://xxx.orchestrate.ibm.com",
"WO_AGENT_ID": "your-agent-id"
}
}
}
}
| wxo-agent-mcp | wxo-builder-mcp-server | |
|---|---|---|
| Purpose | Invoke one agent | Full dev toolkit (tools, agents, connections, flows) |
| Agent | Single WO_AGENT_ID | Multiple agents, WO_AGENT_IDs |
| Tools | invoke_agent, get_agent | 30+ tools (list_skills, deploy_tool, etc.) |
| Use case | Chat with a specific agent | Build and manage Watson Orchestrate resources |
Apache-2.0
FAQs
Simple MCP server to invoke a single Watson Orchestrate agent remotely. Configure agent via env (WO_AGENT_ID).
We found that wxo-agent demonstrated a healthy version release cadence and project activity because the last version was released less than a year ago. It has 1 open source maintainer collaborating on the project.
Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Company News
Open source maintainers are under more pressure than ever. We're raising our open source program from the Team plan to the Business plan, free.

Security News
The supply chain control that delays freshly published gems now covers lockfile generation and gem vendoring in Ruby projects.

Security News
During a UK cyber test, a Mythos 5 agent used sockpuppets, social engineering, and prompt injection to try to get a maintainer to merge malware.