Connect Hive to a Standards-Compatible MCP Client

A standards-compatible MCP client needs only Hive's public URL to begin interactive setup. The client connects over Streamable HTTP, follows OAuth discovery, opens browser consent, and then lists Hive's compact task-oriented tool surface.

Connection contract

The official MCP specification defines stdio and Streamable HTTP as standard transports. Remote clients must send the required MCP Accept header and follow session/authorization behavior. See the MCP transport specification and authorization guide.

URL-only interactive setup

In your client's MCP server settings, create a remote server named Hive and enter:

https://mcp.hiveintelligence.xyz/mcp

Do not add a secret to an install URL. A compatible client should:

1. contact the MCP endpoint;
2. receive the authorization challenge;
3. discover the protected-resource and authorization-server metadata;
4. open Hive's browser consent screen;
5. return to the client and fetch tools/list.

Configuration key names differ by host (url, serverUrl, or httpUrl). Use a dedicated client guide when one exists.

Headless API-key fallback

CI jobs, server-side agents, and clients without interactive OAuth can send a Hive key as a secret header:

Authorization: Bearer YOUR_HIVE_API_KEY

Store the key in an environment variable or secret manager. Never place it in a custom-protocol install URL, browser bundle, committed project config, prompt, screenshot, or log. The legacy x-api-key header remains accepted but is not recommended for new integrations.

Verify behavior, not just configuration

After connecting, ask the client:

"Use Hive to get the current BTC and ETH prices. Include the source, provider-native evidence time when available, Hive runtime status, and receipt ID/version. If the provider exposes no native clock, say source recency is unknown."

Verification is complete only when the host shows a Hive tool call and the answer preserves runtime metadata. If the host answers from model memory, check that Hive is enabled for the conversation and refresh its tool list.

Hive intentionally keeps root tools/list compact. Agents discover a task, inspect the exact schema and operation, execute a bounded call through the declared invoker, and report provenance plus the runtime receipt.

Compatibility checklist

• Supports MCP Streamable HTTP, not only local stdio.
• Implements MCP authorization discovery for URL-only setup, or supports secret HTTP headers for a headless fallback.
• Preserves the server's session ID and protocol-version headers.
• Lets the user review and disable tools.
• Shows tool-call failures instead of silently answering from memory.
• Does not log authorization headers or full upstream payloads.

If any item is unclear, verify it in the client's official documentation before adding Hive.

Next steps

• Client Setup: copy client-specific configurations.
• MCP Security: authorization and tool-use boundaries.
• Known Limitations: current product constraints.
• Public status: live health and runtime visibility.