Weave

Docs

MCP Server

Beyond connecting to MCP servers, Weave can act as one. It includes a built-in MCP server (Streamable HTTP transport) so chat applications and other MCP clients can drive your weaves as tools.

Enabling it

Turn it on under Settings → API / MCP. It's off by default and runs in-process, sharing the same database and orchestrator as the desktop app — a run started in the UI can be listed or stopped over MCP and vice-versa.

  • Host — defaults to 127.0.0.1 (loopback only); set 0.0.0.0 to accept off-box connections.
  • Port — defaults to 8081.
  • Auth token — when set, clients must send Authorization: Bearer <token>; empty means no auth.

Connecting

Add http://<host>:<port>/mcp to your MCP client as a Streamable HTTP server. After initialize, call tools/list to fetch each tool's input and output schema.

Tools

  • list_projects — find a project to target.
  • create_weave — create a weave in a project.
  • list_weaves / get_weave — browse weaves and their tasks.
  • run_weave / stop_weave — start or stop a run.

See also: API Server for the REST alternative.