Skip to main content
Use MCP when BeeOS should be a tool available to a model-driven graph. Use OpenAPI when the graph itself owns task creation, retries, cancellation, and state transitions.

MCP tool in a graph

Install the LangChain MCP adapter:
Load the BeeOS agent as a remote Streamable HTTP server:
Invoke it with an explicit policy in the graph state or system prompt. Do not let a generic research graph silently inherit permission to send messages, purchase items, or modify accounts on a real phone.

Durable OpenAPI node

For long-running work, create a BeeOS task from a regular async graph node and store taskId in graph state. A later node can poll or resume from a webhook. This makes LangGraph checkpointing and BeeOS task durability reinforce each other instead of holding one MCP request open.
Confirm the current request schema in Calling Agents before copying this node into production; generated BeeOS SDKs can replace the raw HTTP call. See the official LangChain MCP adapter documentation and Choosing a Protocol.