Log inSubmit server
Watson Orchestrate logo

Watson Orchestrate

Connects MCP clients to IBM Watson Orchestrate for managing skills, tools, agents, and connections.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Watson Orchestrate

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "watson-orchestrate": {
      "command": "npx",
      "args": [
        "-y",
        "wxo-builder-mcp-server"
      ],
      "env": {
        "WO_API_KEY": "YOUR_VALUE_HERE",
        "WO_INSTANCE_URL": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The Watson Orchestrate MCP server connects MCP clients to an IBM Watson Orchestrate instance through REST API requests. It exposes operations for listing, creating, deploying, updating, copying, deleting, assigning, and executing tools and skills, along with agent-related actions. Run it through npm and configure it as an MCP client server using environment variables. Use it when an AI assistant needs to administer Watson Orchestrate resources from Cursor, VS Code Copilot, Claude Desktop, or Windsurf.

Use cases

  • List Watson Orchestrate skills and connected tools
  • Create and upload Python-based Watson Orchestrate tools
  • Deploy, update, copy, or delete skills
  • Assign tools to Watson Orchestrate agents
  • Execute tools through an MCP client

Key features

  • Skill listing and administration
  • Tool and connection discovery
  • Python tool creation and upload
  • Agent assignment with default agent configuration
  • Tool execution through Watson Orchestrate
  • REST API proxy over MCP

Tools23

What Watson Orchestrate lets your agent do. Expand a tool for its parameters.

Self-reported~90 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

8/8 checks healthy over the last 42d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 14d ago via OSV.dev · wxo-builder-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads54Package downloads in the last 30 days.
Last commit8mo agoMost recent push to the default branch.
Tools exposed23Callable tools this server registers over MCP.

How Watson Orchestrate works

What the Watson Orchestrate MCP server does

The Watson Orchestrate MCP server exposes IBM Watson Orchestrate administration and execution capabilities through MCP tools. It is intended for AI clients that need to inspect or modify Watson Orchestrate resources without directly implementing the platform's REST calls.

Available operations cover skills, tools, connections, and agents. The server can list skills, standard tools, and tools together with their connections. It can retrieve, update, copy, deploy, or delete skills, and it can execute tools through the connected Watson Orchestrate instance.

Tool creation is also supported. Inputs include a tool specification, Python source code, requirements, and a Python filename. The listed creation operations support building Python tools from a specification or uploading a Python tool, including creating a tool and assigning it to an agent.

How it works

An MCP client communicates with the local server using MCP tool calls. The server then acts as an HTTP client and forwards requests to the configured Watson Orchestrate instance. Watson Orchestrate does not connect back to the MCP process.

The package is distributed through npm as wxo-builder-mcp-server. A client configuration starts it with npx -y wxo-builder-mcp-server. Cursor uses an mcpServers configuration section, while VS Code Copilot uses servers with a stdio entry. The repository also provides example configurations for Claude Desktop, Antigravity, and Windsurf.

Setup and configuration

Install the package with npm or invoke it directly through npx. Set these required environment variables in the MCP client configuration or an environment file:

  • WO_API_KEY: IBM Cloud API key used to access Watson Orchestrate.
  • WO_INSTANCE_URL: URL of the Watson Orchestrate instance, such as an orchestrate.ibm.com host.

Agent-oriented tools can use a default agent when the request does not specify an agent. Set WO_AGENT_IDs to a comma-separated list, or set the backward-compatible WO_AGENT_ID variable for a single default. When multiple IDs are supplied, the first ID is used by default.

The Watson Orchestrate MCP server is configured per client. The README includes copy-ready examples for Cursor, VS Code, Claude Desktop, Antigravity, and Windsurf. Cursor also supports a one-click installation link, after which the API key and instance URL must be supplied in the MCP settings.

Tools and capabilities

The exposed tool set includes:

  • Discovery: list_skills, list_tools_with_connections, and list_standard_tools.
  • Skill administration: get_skill, delete_skill, deploy_skill, update_skill, and copy_skill.
  • Remote tool creation: deploy_tool_from_url, create_python_tool_from_tool_spec_json, and create_python_tool_and_upload.
  • Agent assignment: create_tool_and_assign_to_agent and assign_tool_to_agent.
  • Execution: execute_tool.

Creation and assignment inputs include tool specifications, Python code, requirements, filenames, agent IDs, agent names, and new names where applicable. The package also includes an OpenAPI specification describing the Watson Orchestrate API.

The Watson Orchestrate MCP server can be paired with the WxO Builder VS Code extension. The extension is described as providing visual editing, drag-and-drop agent editing, and local or remote testing, while the MCP package provides AI-driven access to the Watson Orchestrate capabilities.

Limitations and notes

This package requires access to a Watson Orchestrate instance and a valid API key. Its role is to proxy MCP requests to the configured REST API; it does not provide a standalone Watson Orchestrate environment.

Agent defaults are optional, and requests can provide an agent identifier or name instead. If no explicit agent is provided, the first configured default ID is used when one is available.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Watson Orchestrate

Watson Orchestrate is an MCP server that connects MCP clients to an IBM Watson Orchestrate instance through its REST API. Its main tools list skills, tools, and connections; create, deploy, update, copy, delete, and execute tools or skills; and assign tools to agents.

Install it with npm or run it through npx using `npx -y wxo-builder-mcp-server`. Add that command to your MCP client configuration, then provide `WO_API_KEY` and `WO_INSTANCE_URL`.

Yes, Watson Orchestrate works with Cursor through an MCP configuration using `npx -y wxo-builder-mcp-server`. Set the API key and instance URL in Cursor's MCP settings; the README also provides a Cursor deep link.

Set `WO_AGENT_IDs` to a comma-separated list of agent IDs, or set `WO_AGENT_ID` for one agent. When a request omits an agent, the first ID in the list is used as the default.

The README names Cursor, VS Code Copilot, Claude Desktop, Antigravity, and Windsurf as MCP clients for this server. It also documents configuration examples for those clients.

Related MCP servers

All in Developer Tools All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWatson Orchestrate AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/watson-orchestrate?style=directory)](https://allmcps.com/mcp/watson-orchestrate)
HTML Embed
<a href="https://allmcps.com/mcp/watson-orchestrate"><img src="https://allmcps.com/api/badge/watson-orchestrate?style=directory" alt="Watson Orchestrate on AllMCPs" /></a>