Install Hive

Connect a supported AI client to Hive's live crypto due-diligence workflows with one public MCP URL. Interactive clients use browser-based OAuth; headless agents can use a Hive API key as an explicit fallback.

Choose your client → Try Hive without an account Headless API keys

Connection details

Every supported client guide points to the same hosted MCP server. URL-only clients discover OAuth from the server and open a browser; header-based API keys remain available for headless code.

The install actions on Client Setup probe the live protected-resource and authorization-server metadata before they become active. If the matching OAuth backend release has not reached production, the buttons stay disabled and the page sends you to the documented API-key fallback instead of opening a known-broken install flow.

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.
• Interactive install links contain only the public URL. If you use a headless API key, keep it out of prompts, screenshots, public repos, browser code, shell history, and custom-protocol URLs.
• 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.
• Grok / xAI: Grok custom MCP connector with browser OAuth.
• 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.
• Compatible MCP clients: standards-based Streamable HTTP and OAuth checklist.

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 browser authorization completed, and the client supports Streamable HTTP MCP.

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. Dedicated guides cover Claude, Cursor, Windsurf, VS Code, ChatGPT, Grok, OpenAI Responses API, Codex CLI, and Gemini CLI. Other clients can connect when they implement Streamable HTTP plus OAuth discovery; headless callers may use Authorization: Bearer instead.

What access do I need before installing?

Interactive OAuth MCP setup creates or links a Hive account in the browser; no API key is copied into the client config. REST, CLI, the TypeScript adapter, and headless MCP fallbacks use a Hive API key from /dashboard/keys. Local stdio is self-hosted and uses optional upstream provider credentials instead.

When do I need the local stdio server?

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 local stdio when a client requires a subprocess or when you want to call providers with your own credentials; the 1.3.0 release candidate requires Node 22.12+ 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. The recommended MCP endpoint is the managed service at https://mcp.hiveintelligence.xyz/mcp. The hive-intelligence package also contains a separate self-hosted stdio server (npx -y -p hive-intelligence@latest hive) for clients that require a subprocess or developers who want to supply provider credentials directly. Cursor, VS Code, Windsurf, Codex CLI, and Gemini CLI accept the managed HTTP endpoint directly; Claude Desktop adds it through Custom Connectors; OpenAI Responses API uses a server-side tools entry.

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.