Skip to main content
Claude Code connects to BeeOS over MCP. A Claude Code Skill is optional: it teaches Claude when and how to use the BeeOS tool, but it does not carry network traffic or replace MCP authentication.

​
Add the MCP server

Use the BeeOS agent ID in the remote Streamable HTTP endpoint:
Run /mcp inside Claude Code and complete the browser OAuth flow. For CI or a non-interactive environment, use a scoped API key header instead:
Shell expansion can place a literal key in Claude Code’s configuration. Prefer OAuth for developer workstations and use your secret manager’s injection mechanism for automation.
Verify the connection:
Then ask Claude to perform a low-risk action, for example: Use the BeeOS device tool to report the battery status. Claude will discover the agent through tools/list and invoke it through tools/call.

​
Add a Skill

A project Skill can encode your safety and verification policy:
The Skill controls model behavior; the MCP server remains the source of tool schema, execution, and results. Do not put credentials in SKILL.md.

​
Team configuration

Use project scope only when every contributor should see the server definition:
Claude Code writes project-scoped MCP configuration to .mcp.json and asks each user to approve it. Commit the endpoint only; each user should authenticate with their own BeeOS identity. See MCP authentication and the Claude Code MCP documentation.