DeveloperWebMCP verified
A WebMCP flow-graph playground: an agent can build and edit node-and-edge diagrams — add/remove/update nodes and edges, auto-layout, and read the current graph.
A WebMCP flow-graph playground: an agent can build and edit node-and-edge diagrams — add/remove/update nodes and edges, auto-layout, and read the current graph. This page documents every listed tool, the action or answer it provides, its installation command, and the input fields an agent should send.
Add a new node to the diagram. Returns the assigned node id — save it to use in add_edge calls. If no id is provided, it is auto-generated by lowercasing the label and replacing spaces with hyphens (e.g. 'API Gateway' → 'api-gateway'). Call this before add_edge — edges require existing node ids. Choose nodeType based on the technology: use 'database' for SQL/NoSQL stores (Postgres, MongoDB), 'cache' for in-memory stores (Redis, Memcached), 'queue' for message brokers (RabbitMQ, Kafka), 'api' for API gateways or reverse proxies, 'client' for end users or frontends, 'service' for everything else.
Open the webmcp-flow.vercel.app website and ask your browser agent to use add_nodeInstall browse first, then run the command in a terminal. WebMCP tools run directly on the website and do not need a package install.
Use the add_node tool on webmcp-flow.vercel.app with label: <string>, nodeType: <string>, id: <string>. Return the structured result and cite the source page.label string Human-readable display name shown on the node, e.g. 'Auth Service'nodeType string Visual category: 'service' (backend microservice), 'database' (persistent storage), 'cache' (in-memory store), 'queue' (message broker), 'api' (gateway/proxy), 'client' (user/frontend)id string Optional stable identifier used in add_edge. If omitted, auto-derived from label (lowercase, spaces → hyphens). Provide explicitly when the label contains special characters or you need a predictable id.Draw a directed edge from one node to another. Both nodes must already exist — call add_node first. Use the node id returned by add_node (or the auto-generated id) as source and target. Call get_graph if you are unsure which node ids are currently in the diagram.
Open the webmcp-flow.vercel.app website and ask your browser agent to use add_edgeInstall browse first, then run the command in a terminal. WebMCP tools run directly on the website and do not need a package install.
Use the add_edge tool on webmcp-flow.vercel.app with source: <string>, target: <string>, label: <string>. Return the structured result and cite the source page.source string ID of the source (origin) nodetarget string ID of the target (destination) nodelabel string Optional short label shown on the edge, e.g. 'HTTP', 'gRPC', 'SQL'Remove a node by id. All edges connected to it are automatically removed as well. Use get_graph to find the correct id before calling this.
Open the webmcp-flow.vercel.app website and ask your browser agent to use remove_nodeInstall browse first, then run the command in a terminal. WebMCP tools run directly on the website and do not need a package install.
Use the remove_node tool on webmcp-flow.vercel.app with id: <string>. Return the structured result and cite the source page.id string ID of the node to removeUpdate the label or nodeType of an existing node. The node id stays the same. Use get_graph to confirm the id before calling.
Open the webmcp-flow.vercel.app website and ask your browser agent to use update_nodeInstall browse first, then run the command in a terminal. WebMCP tools run directly on the website and do not need a package install.
Use the update_node tool on webmcp-flow.vercel.app with id: <string>, label: <string>, nodeType: <string>. Return the structured result and cite the source page.id string ID of the node to updatelabel string New display labelnodeType string New node typeReturns all current nodes and edges. Call this when you need to know existing node ids before calling add_edge, remove_node, or update_node.
Open the webmcp-flow.vercel.app website and ask your browser agent to use get_graphInstall browse first, then run the command in a terminal. WebMCP tools run directly on the website and do not need a package install.
Use the get_graph tool on webmcp-flow.vercel.app. Return the structured result and cite the source page.Remove all nodes and edges from the diagram. Use only when the user explicitly asks to reset or start over.
Open the webmcp-flow.vercel.app website and ask your browser agent to use clear_graphInstall browse first, then run the command in a terminal. WebMCP tools run directly on the website and do not need a package install.
Use the clear_graph tool on webmcp-flow.vercel.app. Return the structured result and cite the source page.Rearrange all nodes into a readable left-to-right layered layout based on edge directions. Only call this when the user explicitly asks to arrange, organize, or layout the diagram. Do not call it automatically after adding nodes or edges.
Open the webmcp-flow.vercel.app website and ask your browser agent to use auto_layoutInstall browse first, then run the command in a terminal. WebMCP tools run directly on the website and do not need a package install.
Use the auto_layout tool on webmcp-flow.vercel.app. Return the structured result and cite the source page.