MCP N8n vs Sanity

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

MCP N8n logoMCP N8nDeveloper Tools · Local subprocess (stdio)Operate and build n8n: 61 tools, 560-node catalog, validation, autofix, snapshots and backups.64GoodAuth: not declaredSanity logoSanityDeveloper Tools · Local subprocess (stdio)Direct access to your Sanity projects (content, datasets, releases, schemas) and agent rules64GoodAuth: oauth 2.0

Verdict: choose MCP N8n for developer tools work as a local process; choose Sanity 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?

MCP N8n logoChoose MCP N8n when

  • You need dedicated capabilities in the Developer Tools domain.
  • You prefer a local stdio subprocess transport.
  • You have the keys it needs: N8N_BASE_URL, N8N_API_KEY.
  • You want tools like n8n_create_workflow, n8n_list_workflows, n8n_list_workflows_summary.
Explore MCP N8n

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

Feature & specification comparison

Rows where the two servers differ are marked.

SpecMCP N8n logoMCP N8nSanity logoSanity
CategoryDeveloper ToolsDeveloper Tools
Quality signal64/100 · Good64/100 · Good
Install commandConfirmedConfirmed
TransportLocal subprocess (stdio)Local subprocess (stdio)
AuthNot declaredOAuth 2.0
PricingNot declaredNot declared
Required env varsN8N_BASE_URLN8N_API_KEYNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars21192
Directory activity 1 views 0 installs 0 upvotes 2 views 0 installs 0 upvotes
Tools618

Tools & capabilities

MCP N8n tools 61

  • n8n_create_workflowCreate a new workflow in n8n. Prefer n8n_search_nodes + n8n_validate_workflow first so the JSON is valid. You can specify nodes, connections, and settings.
  • n8n_list_workflowsList all workflows with full details. Can filter by active status, tags, name, or project. WARNING: Returns complete workflow data including nodes and connections - use n8n_list_workflows_summary for better token efficiency.
  • n8n_list_workflows_summaryList workflows with minimal data (id, name, active, tags, updatedAt only). Recommended for browsing and listing - uses 90% fewer tokens than n8n_list_workflows. Use n8n_get_workflow to fetch full details of a specific workflow.
  • n8n_get_workflowGet detailed information about a specific workflow by ID.
  • n8n_update_workflowUpdate an existing workflow. Supports partial updates: omitted fields keep their current values (the current workflow is fetched and merged automatically).
  • n8n_delete_workflowDelete a workflow permanently. A local snapshot is saved first so it can be restored with n8n_rollback_workflow (into a new workflow).
  • n8n_activate_workflowActivate a workflow to start receiving triggers.
  • n8n_deactivate_workflowDeactivate a workflow to stop receiving triggers.
  • n8n_transfer_workflowTransfer a workflow to another project.
  • n8n_get_workflow_tagsGet all tags associated with a workflow.
  • n8n_update_workflow_tagsUpdate tags for a workflow.
  • n8n_list_executionsList workflow executions. Can filter by status, workflow ID, or project. TIP: Set includeData=false and use fields parameter to reduce token usage.
  • +49 more on the listing page

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

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.

MCP N8n

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "mcp-n8n": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-n8n"
      ],
      "env": {
        "N8N_BASE_URL": "YOUR_N8N_BASE_URL_HERE",
        "N8N_API_KEY": "YOUR_N8N_API_KEY_HERE"
      }
    }
  }
}

Sanity

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

Frequently asked questions

MCP N8n is categorized under Developer Tools and uses a local stdio subprocess. Sanity belongs to Developer Tools and uses a local stdio subprocess. Pick MCP N8n for developer tools work and Sanity 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.

MCP N8n has no declared pricing — check the project's own site. Sanity has no declared pricing — check the project's own site. Auth: oauth 2.0. 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 mcp-n8n and sanity as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, MCP N8n has a quality signal of 64/100 (Good) with 1 views, 0 installs and 21 GitHub stars. Sanity has 64/100 (Good) with 2 views, 0 installs and 192 GitHub stars.