BEEOS CLOUD / DEVELOPER REFERENCE
MCP and A2A boundaries
Place tools, agent-to-agent calls, and runtime methods on the correct surface
| Surface | What it does | SDK entry |
|---|---|---|
| Cloud Server REST | Manages product-scoped resources | Server SDK |
| Instance methods | JSON-RPC control of a running framework | methods.invoke; onRuntimeMethod |
| Agent A2A | Discovers and calls another agent | Harness SDK a2a.discover, call, getTask |
| MCP | Exposes or configures tools | Instance mcp/* methods; protocol gateway |
MCP tool access does not replace the Server API: an MCP client may call an agent tool, while an app backend still owns instance lifecycle and user scope. A2A calls travel through the Agent Gateway and do not use a Cloud bsk_ key inside the agent. C14 instance methods are a management channel, not an A2A message.
For framework configuration, use methods.mcp.prepare, set, unset, and list only after checking the instance's capabilities. For agent-to-agent communication, use the Harness SDK A2A port.
BeeOS CloudBack to documentation