Sanity vs Watson Orchestrate

A side-by-side look at the Sanity and Watson Orchestrate MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

Sanity logoSanityDeveloper Tools · Local subprocess (stdio)Direct access to your Sanity projects (content, datasets, releases, schemas) and agent rules64GoodAuth: oauth 2.0Watson Orchestrate logoWatson OrchestrateDeveloper Tools · Local subprocess (stdio)Manage IBM Watson Orchestrate tools, agents, connections from Cursor, Copilot, Claude.49FairAuth: not declared

Verdict: choose Sanity for developer tools work as a local process; choose Watson Orchestrate for developer tools as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

Sanity logoChoose Sanity when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • Its auth model fits you: OAuth 2.0.
  • You want tools like query_documents, create_documents, patch_documents.
Explore Sanity

Watson Orchestrate logoChoose Watson Orchestrate when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: WO_API_KEY, WO_INSTANCE_URL.
  • You want tools like list_skills, list_tools_with_connections, list_standard_tools.
Explore Watson Orchestrate

Feature & specification comparison

Rows where the two servers differ are marked.

SpecSanity logoSanityWatson Orchestrate logoWatson Orchestrate
CategoryDeveloper ToolsDeveloper Tools
Quality signal64/100 · Good49/100 · Fair
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthOAuth 2.0Not declared
PricingNot declaredNot declared
Required env varsNone listedWO_API_KEYWO_INSTANCE_URL
Verified ownerCommunity listingCommunity listing
GitHub stars1940
Directory activity 2 views 0 installs 0 upvotes 0 views 0 installs 0 upvotes
Tools823

Tools & capabilities

Sanity tools 8

  • query_documentsrun GROQ queries directly
  • create_documentscreate draft documents from structured content, or version documents when a release ID is provided
  • patch_documentssurgical edits to existing documents; published documents are edited by creating or updating drafts
  • deploy_studiodeploy a hosted Studio bound to an MCP-managed schema
  • create_versioncreate version documents for releases
  • whoamiverify the authenticated Sanity user
  • get_project_studioslist Studio applications linked to a project
  • give_feedbackreport MCP tool errors, missing capabilities, confusing output, or documentation issues

Watson Orchestrate tools 23

  • list_skills
  • list_tools_with_connections
  • list_standard_tools
  • get_skill
  • delete_skill
  • deploy_skill
  • deploy_tool_from_url
  • create_python_tool_from_tool_spec_json
  • tool-spec.json
  • python_code
  • requirements
  • create_python_tool_and_upload
  • +11 more on the listing page

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

Sanity

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "sanity": {
      "command": "npx",
      "args": [
        "-y",
        "sanity@latest"
      ]
    }
  }
}

Watson Orchestrate

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "watson-orchestrate": {
      "command": "npx",
      "args": [
        "-y",
        "wxo-builder-mcp-server"
      ],
      "env": {
        "WO_API_KEY": "YOUR_WO_API_KEY_HERE",
        "WO_INSTANCE_URL": "YOUR_WO_INSTANCE_URL_HERE"
      }
    }
  }
}

Frequently asked questions

Sanity is categorized under Developer Tools and uses a local stdio subprocess. Watson Orchestrate belongs to Developer Tools and uses a local stdio subprocess. Pick Sanity for developer tools work and Watson Orchestrate for developer tools.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.

Sanity has no declared pricing — check the project's own site. Auth: oauth 2.0. Watson Orchestrate has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add sanity and watson-orchestrate as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, Sanity has a quality signal of 64/100 (Good) with 2 views, 0 installs and 194 GitHub stars. Watson Orchestrate has 49/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.