Connect Claude Desktop
Before you start: you need the MCP URL and setup code from Discover the MCP endpoint.
1. Edit Claude Desktop’s config
Claude Desktop reads its MCP config from a JSON file:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json - Linux:
~/.config/Claude/claude_desktop_config.json
Add (or merge into) the mcpServers section:
{
"mcpServers": {
"hiveloom-support-bot": {
"url": "https://hiveloom.example.com/mcp/default/support-bot"
}
}
}Replace the URL with the one hiveloom mcp-identity create printed.
2. Restart Claude Desktop
Fully quit and reopen the app. On first connect, Claude Desktop:
- Hits Hiveloom’s
/.well-known/oauth-authorization-serverfor discovery. - Opens a browser window to the
/oauth/authorizeendpoint. - Prompts you for the setup code.
- Paste the code. Submit. The browser window closes and Claude Desktop is connected.
3. Verify
In a conversation, Claude Desktop should now show three tools from the Hiveloom agent:
- chat — send a message to the agent.
- memory — search stored memories.
- list_conversations — list prior conversations.
Ask Claude to use the chat tool:
“Use the hiveloom-support-bot
chattool to say hello.”
Claude routes the request to the Hiveloom agent and returns the agent’s reply.
Troubleshooting
- Tools don’t appear after restart — Claude Desktop failed to reach the MCP URL. Open the MCP log in Claude Desktop’s settings and look for 4xx/5xx errors. Most common cause: TLS misconfig (revisit TLS).
- OAuth browser page fails with
http://URLs in discovery — the reverse proxy isn’t forwardingX-Forwarded-Proto: https. Revisit Reverse proxy. - Setup code says “expired” — issue a new one:
hiveloom mcp-identity reissue-setup-code <identity-id> --tenant default
Next: Connect Cursor for the IDE surface, or jump to Write your first skill to customise the agent.