Hive Intelligence home
Hive Intelligence
GitHub

Install in Your AI Client

Connect Hive to Cursor

Written by , Product docsLast updated

Connect Cursor to Hive so the IDE's AI can call live crypto tools while you code. Use the Cursor install link when it is available, or add the remote HTTP config to mcp.json and verify a Hive tool call.

View MarkdownAsk ClaudeAsk ChatGPT

Before you start

  1. Cursor installed from cursor.sh.
  2. A Hive API key from /dashboard/keys.

The Client Setup page can open Cursor with the Hive MCP server prefilled. If the generated install URL includes your API key, treat that URL as sensitive. Confirm the server in Cursor, then verify the tool call below.

Option 2: Manual config

1. Open the MCP settings

In Cursor, go to Settings → MCP Servers → Add Server (or edit ~/.cursor/mcp.json directly).

2. Add this config

json
{
  "mcpServers": {
    "hive": {
      "url": "https://mcp.hiveintelligence.xyz/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_HIVE_API_KEY"
      }
    }
  }
}

Replace YOUR_HIVE_API_KEY with the key from /dashboard/keys.

This is the remote-HTTP (Streamable HTTP) config — Cursor connects directly to mcp.hiveintelligence.xyz and authenticates with Authorization: Bearer. No local Node process, no @latest to re-download on every reload.

Cursor also accepts the same url field for SSE transport — Cursor auto-detects whether the endpoint speaks Streamable HTTP or SSE from the response. Both work with this single config block. (Reference: Cursor MCP docs.)

3. Reload Cursor

The MCP server should appear green in Settings → MCP Servers after Cursor reloads the entry.

4. Verify it worked

Open the AI chat panel (⌘L on macOS) and ask:

"What's the current price of BTC, ETH, and SOL?"

You should see Cursor call the get_price tool.

Alternative: stdio via the local Node wrapper

If you can't reach Hive's endpoint directly (corporate proxy, air-gapped setup), spawn the wrapper as a subprocess instead:

json
{
  "mcpServers": {
    "hive": {
      "command": "npx",
      "args": ["-y", "-p", "hive-intelligence", "hive"],
      "env": {
        "HIVE_API_KEY": "YOUR_HIVE_API_KEY"
      }
    }
  }
}

The HIVE_API_KEY env var is how the wrapper receives the secret; it still forwards every upstream request with Authorization: Bearer attached, so authentication is identical to the remote-HTTP path. Requires Node 20+.

What to ask in Cursor

Cursor's context-aware AI is especially good at code-adjacent crypto work:

  • "Write a Node.js script that monitors the top 10 DeFi pools by APY on Base and alerts me when any new pool enters the top 10."
  • "Check if this contract address is a honeypot before I hardcode it in the repo: 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"
  • "Generate a TypeScript type from this Hive tool response so I can strongly type the wallet-balances call."
  • "Fetch funding rates for BTC perpetuals across Binance, Bybit, and OKX and render them as a React component."

Cursor will mix Hive tool calls with file edits and code generation — the agent decides which to use.

Troubleshooting

MCP server shows red in Settings. Open the MCP panel, click the error, and check the log — usually a bad HIVE_API_KEY or Node.js missing.

"npx: command not found". Install Node.js 20 or higher from nodejs.org, then restart Cursor.

API key rejected. Regenerate at /dashboard/keys. Keys are sensitive to leading/trailing whitespace; copy the key exactly.

Install link doesn't open Cursor. Make sure Cursor is running and you're on Cursor 0.42+ (older versions didn't support MCP install links).

Other clients

Next steps

Previous
Claude Code
Next
Windsurf