graph as an MCP client
Each[mcp.<name>] table in config.toml connects one server, over stdio with command or streamable HTTP with url. The server’s tools join the catalog as <name>__<tool>, and agents and plan steps call them like any other tool.
You choose which of a server’s tools graph loads, and can correct a tool’s description or output shape when the server’s own is wrong or missing.
graph as an MCP server
graph mcp serve runs graph as an MCP server over stdio. A connected client gets one tool per plan in your catalog, named plan_<identifier>, plus tools for writing and testing plans. An ask step in a plan reaches the client’s user as an elicitation request.
Guides
Connect an MCP server
Add a server’s tools to your catalog.
Serve plans over MCP
Run your plans from Claude, Cursor and other clients.
Filter and override a server's tools
Load only the tools you need and fix their descriptions.
Test an MCP server
Check a connection and call a tool directly.