Skip to main content
Hive implements the Model Context Protocol over Streamable HTTP. Any compliant client can connect, whether or not it has a guide here.

What to give your client

Most clients want a JSON block shaped roughly like this:
The key names vary by client. Windsurf wants serverUrl, VS Code wants servers with "type": "http", and Gemini CLI wants httpUrl. Check your client’s own MCP docs for which it expects.

Headless clients

If your client cannot open a browser, authenticate with a key instead:
Create a key at dashboard keys and read it from an environment variable rather than committing it.

The developer profile

The root endpoint shows the nine use-case tools. To reach the full catalog from an MCP client, connect to the developer profile instead:
It adds search_tools, get_api_endpoint_schema and invoke_api_endpoint next to the nine. Each catalog call costs 1 credit.

Check it works

  1. Ask your client: “What Hive tools do you have?” Expect nine: find_token, get_token_price, check_token_safety, research_token, analyze_wallet, market_positioning, market_overview, defi_yields and prediction_markets. An empty list means the connection or sign-in failed. Go back to the sign-in step on this page.
  2. Ask: “Is PEPE on Ethereum safe to buy, and what is it worth?”
  3. Confirm the answer names GoPlus and CoinGecko with a fetch time. An answer with no source came from the model’s memory, not from Hive.