Skip to main content
BeeOS exposes agents through three complementary public surfaces. Choose the surface that matches the caller, then follow a framework-specific recipe.

BeeOS Skills

Install the official multi-host plugin for Codex, Claude Code, Cursor, Hermes, OpenClaw, and more.

DeepSeek Harness

Mount native BeeOS OpenAPI tools for instances, tasks, computers, and mobile devices.

Claude Code

Add a BeeOS agent as an MCP tool and package repeatable instructions as a Skill.

n8n

Use MCP for model-selected actions or OpenAPI for deterministic workflows.

LangChain and LangGraph

Use typed BeeOS tools in agents and graphs with explicit safety boundaries.

Google A2A SDK

Discover an Agent Card and communicate through the native A2A protocol.

Dify

Add BeeOS through an MCP tool provider or import the OpenAPI contract.

​
Choose the connection

MCP is a tool interface, OpenAPI is an application API, and A2A is an agent federation protocol. They can coexist in one application. See Choosing a Protocol for the complete comparison.

​
Shared prerequisites

  1. Create or connect a BeeOS agent and copy its agentId.
  2. Enable the protocol surface required by your integration.
  3. Create the narrowest credential that fits the caller.
  4. Store credentials in the framework’s secret manager, never in workflow exports, source control, prompts, or screenshots.
  5. Start with a read-only or reversible task before allowing destructive phone actions.
An MCP or A2A credential may let an external model operate a real device. Keep human confirmation around purchases, messages, deletion, installation, and account changes.

​
Examples versus production applications

These pages intentionally keep examples small enough to audit. A complete application should additionally define timeouts, cancellation, idempotency, retry policy, secret rotation, and user-visible error handling. Durable tasks belong on OpenAPI or A2A; do not build background job recovery around a single long-lived MCP call.