LiveGraph speaks the Model Context Protocol in both directions — your agents call remote MCP servers as tools, and any graph can be published as an MCP server that other agents and clients call.
A node reaches a server by adding it under MCP in its settings — copy a config below, or sign up and add it straight onto a node.
Repos, issues, PRs, files, branches and code search — the connector the repo improvement loops run on. Pair with allowedWriteBranches to fence pushes off main.
Up-to-date library and framework documentation pulled straight into the agent's context — resolve a package name, then query its docs by topic.
Ask questions about any public GitHub repository and get answers grounded in its DeepWiki — read the generated wiki structure and contents too.
Semantic search over Cloudflare's product documentation — Workers, Pages, R2, D1, Durable Objects and the rest — for agents that build on the platform.
Semantic web search tuned for agents — search any topic and get clean, ready-to-use page content back instead of a link list.
Search the Hub's models, datasets and Spaces and inspect repo details — plus a view into which account the token resolves to.
Payments, customers, invoices and subscriptions — create payment links, look up charges, manage billing objects from inside a run.
Static-analysis findings from the Semgrep AppSec Platform plus remote scans with built-in or custom rules — security review inside a graph.
Web search, page extraction, site crawling and multi-step research built for agents — a heavier-duty alternative to single-shot search.
Turn any URL into clean markdown — scrape single pages, search the web, and parse results for agents that need page content not links.
One endpoint in front of the whole Zapier app directory — Gmail, Slack, Sheets and 8,000 more, with each action gated by what you enable in Zapier.
Your personal https://mcp.zapier.com/… URL — each account gets its own.
First-party PDF form filling — open a PDF, read and set AcroForm fields, search and edit text blocks, then export the result. The connector behind LiveGraph's /files PDF flow.
Hosted livegraph.ai workers reach the service at this private-network address. On your own deployment use the compose profile's address (e.g. http://127.0.0.1:3931/mcp).
Not listed? Any streamable-HTTP MCP server works — paste its URL into a node's MCP settings, or browse the Smithery and PulseMCP catalogs from the same place.
These servers ask for a browser sign-in flow instead of a static key. LiveGraph's MCP client is static-auth today, so they're listed as what's next — not as working connectors.
Search, read and create pages and databases in a Notion workspace.
Issues, projects and cycles — triage and update the tracker agents file work against.
Jira issues and Confluence pages through Atlassian's remote MCP.
Errors, issues and releases — let an agent pull the actual stack behind an alert.
Projects, databases, edge functions and logs on the Supabase platform.
Account-level Cloudflare management — Workers, zones, KV, analytics (distinct from the no-auth docs search above).
The reverse direction is built in — publish any graph as an MCP server from its Settings → MCP tool, and it answers tools/list/tools/call at POST /mcp/serve/<slug> for other agents and MCP clients. Signed-in graph owners publish from the same canvas.
Sign up free to wire a connector onto an agent — or watch a real multi-agent run in the live demo, no account needed. Already have an account? Log in.