Discover the MCP endpoint
Hiveloom exposes every agent as a Model Context Protocol server at a stable, per-tenant URL. External clients (Claude Desktop, Cursor, ChatGPT, custom scripts) connect to that URL and authenticate via OAuth.
HTTPS matters
For local testing, http://127.0.0.1:3000/... is fine.
For remote MCP clients and Claude’s hosted MCP connector flow, use a public
https:// URL. Anthropic’s MCP connector docs require the server URL to start
with https:// and say the server must be publicly exposed over HTTP.
The two supported paths in these docs are:
- Deploy on a VPS with Caddy and Let’s Encrypt
- Cloudflare Tunnel for outbound-only HTTPS
One command
hiveloom mcp-identity create \
--tenant default \
--name my-desktop \
--agent support-botOutput:
Created MCP identity 'my-desktop' (abc123…)
Setup code: 7f3ab2c19e4d0815…
MCP URL: https://hiveloom.example.com/mcp/default/support-bot
Add the URL to your MCP client (Claude Desktop, Cursor, etc.).
Enter the setup code in the browser when prompted.Write down the Setup code and the MCP URL. You’ll paste them into Claude Desktop or Cursor on the next page.
Setup codes expire after 24 hours. If you lose the code, issue a new one:
hiveloom mcp-identity reissue-setup-code <identity-id> --tenant defaultURL shape
https://<your-host>/mcp/<tenant-slug>/<agent-name>If you’re running locally without TLS, replace https://<your-host> with
http://127.0.0.1:3000 — the path is the same.
Manage identities
hiveloom mcp-identity list --tenant default
hiveloom mcp-identity show <id> --tenant default
hiveloom mcp-identity revoke <id> --tenant defaultEach identity represents a single client connection. You can create one per device / user / workflow and revoke them individually.
Map to a person (optional)
If you’re multi-user, map an identity to a person ID so conversations are attributed:
hiveloom mcp-identity map <id> --tenant default --person-id aliceNext
Pick your client:
Or use it from any MCP-speaking client — the URL and setup code are all they need.