Get Started
Install Hive
Connect a supported AI client to Hive's live crypto tools with one Hive API key. Pick your client below for exact setup steps. Every guide uses the same remote MCP endpoint; the client-specific part is where the config lives and how the client passes authentication.
Get a Hive API key → Or jump to a client below
Connection details
Every supported client guide points to the same hosted MCP server. The client-specific part is where the server is configured and how the auth header is supplied.
| Item | Value |
|---|---|
| Remote MCP URL | https://mcp.hiveintelligence.xyz/mcp |
| Transport | Streamable HTTP |
| Auth header | Authorization: Bearer YOUR_HIVE_API_KEY |
| Key setup | /dashboard/keys |
| Verification prompt | "Use Hive tools to get the current price of BTC, ETH, and SOL in USD." |
Before you connect
- Verify that the MCP client is connecting to Hive's official endpoint:
https://mcp.hiveintelligence.xyz/mcp. Do not approve a look-alike MCP URL or marketplace entry that points somewhere else. - Keep your Hive API key private; never paste it into prompts, screenshots, public repos, browser code, or model-generated config.
- Use client tool-call approval or review prompts when your MCP client supports them.
- Hive provider tools are read-only, but Hive-native stateful tools can write monitors, alerts, memory facts, reports, and B2B subject audit state.
- Before production rollout, read MCP Security for prompt-injection boundaries, scoped tool access, key handling, and stateful-tool isolation.
Pick your client
- Claude Desktop — Anthropic's desktop app, MCP native
- Claude Code — Anthropic's terminal CLI
- OpenAI Responses API / ChatGPT — remote MCP from server-side OpenAI agents, with ChatGPT app beta notes
- Codex CLI — OpenAI's open-source coding agent
- Cursor — AI-first IDE with an MCP install link or manual config
- Windsurf — Codeium's AI IDE
- VS Code — Microsoft VS Code with GitHub Copilot Chat
- Gemini CLI — Google's official Gemini command-line agent
Need all setup paths on one page?
Client Setup covers every supported client and API path in one tabbed page with the remote MCP endpoint, auth shape, client-specific configuration, and verification steps.
Hive also ships 17 agent skills for install, discovery, token diligence, wallet investigation, stateful monitoring, DeFi research, Solana analysis, network diagnostics, prediction markets, and other common crypto workflows. Install the public skill pack with npx skills add hive-intel/hive-skills, or let hive init --all --browser install supported local agent resources during CLI setup.
Verify after setup
After saving the client configuration, restart the client or reload its MCP server list. Then ask one live-data prompt:
"Use Hive tools to get the current price of BTC, ETH, and SOL in USD."
Continue when the response shows a Hive tool call and live provider-backed data. If the client does not show a tool call, check that the server is enabled, the API key is available to the client, and the client supports Streamable HTTP MCP with API-key headers.
For deeper checks after the first call, use Quick Start for REST, category MCP, CLI, and discovery examples.
Frequently asked
Which client should I pick?
Pick the supported client or API path you already use every day — switching clients just to install Hive is unnecessary. Dedicated guides cover Claude Desktop, Claude Code, Cursor, Windsurf, VS Code, OpenAI Responses API, Codex CLI, and Gemini CLI. Other MCP clients can connect only when they support Streamable HTTP plus API-key headers (Authorization: Bearer recommended, x-api-key legacy).
What access do I need before installing?
You need a Hive API key from /dashboard/keys and a supported MCP client or API runtime. Plan limits control monthly credits and rate limits; see Pricing when you need a higher budget or throughput.
When do I need the local stdio wrapper?
Most documented clients (Cursor, Windsurf, VS Code, Codex CLI, Gemini CLI) connect directly to Hive's managed HTTP endpoint. Claude Desktop adds Hive through its Custom Connectors UI. OpenAI Responses API integrations configure Hive in the server-side tools array. Use the stdio wrapper only when a client or network cannot call remote HTTP MCP directly; that fallback path needs Node 20+ on your PATH.
Can I install Hive in more than one client at the same time?
Yes. Install it in Claude Desktop for chat, Cursor for IDE work, Gemini CLI for scripts, and OpenAI Responses API for server-side agents — the same API key works everywhere. Every installed client or API integration discovers Hive's tool surface independently at runtime.
What can my agent do once Hive is installed?
Query live crypto prices, check wallet positions across chains, analyze DeFi yields, screen tokens for honeypots and rugpulls, and track DEX flows. Hive returns freshness metadata, provider/source context, and runtime status so agents can explain where an answer came from. See Agent Resources for example prompts and agent workflows.
Is Hive an MCP server I have to run myself?
No. Hive is managed — the MCP endpoint is https://mcp.hiveintelligence.xyz/mcp and Hive runs the hosted service, scaling layer, and upstream provider integration. For stdio transports you run a thin local wrapper (npx -y -p hive-intelligence@latest hive). That wrapper ships in the hive-intelligence npm package — the same package that also provides the hive CLI, so one install covers every local surface. Cursor, VS Code, Windsurf, Codex CLI, and Gemini CLI accept the remote HTTP endpoint directly via their config files; Claude Desktop adds it through its Custom Connectors UI; OpenAI Responses API uses a server-side tools entry. The default remote path does not require the local wrapper.
Next steps
- Agent Resources — what your agent can build once installed
- Agent Skills — workflow guidance for agents after installation
- Quick Start — REST, MCP, and CLI basics
- Tools Reference — every tool, every category