Back to all features
knowledge + extensibility

MCP + Integrations

Drop MCP servers and deploy targets onto the canvas as nodes. The run reaches the tools and surfaces you already use — Linear, Notion, Vercel — wired in like any other step.

Planning spec stage · open RFC
what it is

Tools and surfaces, as first-class nodes.

DISPATCH speaks the Model Context Protocol. Point a node at an MCP server and its tools become callable steps; point one at a deploy target and the canvas ships to it. No glue scripts, no per-service SDK.

mcp servers

Reach in.

A Context or Investigate node binds to an MCP server and exposes its tools to the run.

Robloxmcp
Linearmcp
Notionmcp
+ anystdio · http
deploy targets

Reach out.

A Deploy node ships the run's artifact to a surface your users already live on.

Verceldeploy
Safenticdeploy
Netlifydeploy
+ anytarget
why it matters

One graph, real surfaces.

No more sandbox. The same run files the Linear issue, writes the Notion doc, and ships the Vercel preview.

protocolMCP · stdio + http
credentialslocal · per-node
surfacenode, not glue
how it works

Bind, expose, wire.

Three steps turn an external service into a node the run can use.

01 — bind

Add a server, locally.

Register an MCP server by command or URL. Credentials stay on your machine; nothing is brokered through a cloud.

$ dispatch mcp add linear --stdio
02 — expose

Tools become steps.

The server's tool list surfaces on the node. create_issue, deploy, search_pages — callable like any built-in.

›linear.create_issueready
›notion.write_pageready
›vercel.deploytarget
03 — wire

Drop it in the chain.

Wire the integration node downstream of Create or Apply. Its output — an issue URL, a deploy preview — flows on to Review.

Createdraft
Deployvercel.deploy
try it

Wire it. Run it.

Connect each integration, then run. Watch the chain reach Linear and Notion, then ship to Vercel.

canvas · mcp + deploy
2 unwired
Initialisertrigger
ship the weekly digest
Investigateweb_search
3 sources gathered
Createdraft
digest + changelog built
Linearmcp
create_issue · idle
Notionmcp
write_page · idle
Verceldeploy
deploy · idle
log ›connect Linear and a deploy target, then press Run.

Notion is optional. Linear (MCP) and Vercel (deploy) are required to run.

Back to all features
related features

Wired to the rest of the canvas.

Activecommunity

Skills-as-Nodes

Publish a skill; it becomes a node anyone can drop on the canvas.

open
Testingvia MCP

Subscription Models

Wire non-API subscription models straight into nodes via MCP.

open
PlanningRunPod GPU

Rapid Pod Deployments

Ship a canvas to a GPU pod serving a 70B-class model.

open