Connect Cursor

Same setup code, same MCP URL — different client config location.

1. Open Cursor’s MCP settings

• Cursor → Settings → Cursor Settings → Features → MCP Servers.
• Or edit ~/.cursor/mcp.json directly.

Add:

{
  "mcpServers": {
    "hiveloom-support-bot": {
      "url": "https://hiveloom.example.com/mcp/default/support-bot"
    }
  }
}

Replace the URL with the one from Discover the MCP endpoint.

2. Authorize

Reload Cursor. It will open a browser to Hiveloom’s OAuth flow. Paste the setup code when prompted. The window closes and the server appears as connected in Cursor’s MCP panel.

3. Use it in Composer

In a Cursor Composer chat, reference the tool:

“@hiveloom-support-bot chat: What can you do?”

Cursor routes the call to the Hiveloom agent and streams the reply back into the Composer.

Troubleshooting

Same failure modes as Claude Desktop — the OAuth flow is identical because both clients follow the MCP spec. Re-read the troubleshooting section there if things don’t connect.

You’re done with the MVP

If you’ve reached this page, you have:

1. A Hiveloom instance reachable over HTTPS with a valid certificate.
2. A credential stored and an agent created.
3. That agent connected to Claude Desktop and Cursor over MCP.

Next: teach the agent something specific to your domain by writing a skill.

Next: Write your first skill.