Install in Your AI Client
Connect Hive to Cursor
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.
Before you start
- Cursor installed from cursor.sh.
Option 1: Cursor install link
The Client Setup page can open Cursor with the Hive MCP server prefilled after live OAuth metadata passes. The release gate separately verifies that Hive accepts Cursor's exact OAuth callback through Dynamic Client Registration. The install URL contains only Hive's public endpoint. Confirm the server, complete browser authorization, 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
{
"mcpServers": {
"hive": {
"url": "https://mcp.hiveintelligence.xyz/mcp"
}
}
}This is the remote-HTTP (Streamable HTTP) config. Cursor connects directly to mcp.hiveintelligence.xyz, discovers OAuth, and opens browser authorization. No local Node process runs, and no secret is stored in mcp.json.
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: local stdio server
Use a local subprocess when your Cursor setup requires stdio or when you want to supply upstream provider credentials directly:
{
"mcpServers": {
"hive": {
"command": "npx",
"args": ["-y", "-p", "hive-intelligence@latest", "hive"]
}
}
}This starts the self-hosted Hive MCP server and does not use HIVE_API_KEY. Add provider-specific variables to env only when needed. The 1.3.0 release candidate requires Node 22.12+.
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 mixes Hive tool calls with file edits and code generation, and the agent decides which to use.
Troubleshooting
MCP server shows red in Settings. Open the MCP panel, click the error, and check the log. Remove and re-add the URL to restart OAuth discovery.
"npx: command not found". Install Node.js 22.12 or newer from nodejs.org, then restart Cursor.
Browser authorization does not open. Click the server's authentication prompt in Cursor's MCP settings, or remove and re-add the server. Check Hive status before retrying.
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
- Claude Desktop: if you live in Claude instead of Cursor.
- VS Code: for GitHub Copilot Chat users.
- Windsurf: Codeium's IDE.
- All clients: full list.
Next steps
- Agent Resources: what Cursor can build once connected.
- JavaScript integration: REST examples and TypeScript adapter notes for Cursor projects.
- Tools Reference: every tool Cursor can call.