---
title: Connect Hive to Grok
lastUpdated: '2026-07-11'
nextjs:
  metadata:
    title: "Install Hive in Grok | Custom Crypto MCP Connector"
    description: "Connect Grok to Hive's public MCP endpoint with xAI's Custom Connector flow and browser-based OAuth."
    alternates:
      canonical: https://www.hiveintelligence.xyz/install/grok
    keywords: "grok mcp, xai mcp connector, grok crypto data, hive grok, custom mcp grok"
---

**Connect Grok directly to Hive as a custom MCP connector.** Enter Hive's public endpoint at `grok.com/connectors`, complete browser authorization, and let Grok discover the due-diligence tools exposed by the server. {% .lead %}

{% ai-doc-actions path="/install/grok" title="Grok Install Guide" /%}

---

## Compatibility

xAI documents Custom MCP connectors for Grok. The setup accepts a publicly reachable MCP server URL and completes any required authentication before discovering tools.

- xAI documents connectors as available to all Grok users through [`grok.com/connectors`](https://grok.com/connectors).
- An organization policy may still hide or restrict Custom connectors; ask its admin to allow Hive if the option is unavailable.
- Hive uses Streamable HTTP and OAuth discovery at `https://mcp.hiveintelligence.xyz/mcp`.

Source: [xAI Connectors documentation](https://docs.x.ai/grok/connectors), last updated by xAI on June 14, 2026.

---

## Add Hive to Grok

1. Open [`grok.com/connectors`](https://grok.com/connectors).
2. Select **New Connector**.
3. Choose **Custom**.
4. Enter the following server URL:

```text
https://mcp.hiveintelligence.xyz/mcp
```

5. Continue and complete the Hive authorization screen in your browser.
6. Return to Grok and confirm that the Hive tools were discovered.

The connector setup contains only the public MCP URL. Do not append an API key to the URL or paste one into a prompt.

### Grok CLI

xAI's Grok CLI also supports remote Streamable HTTP servers and opens OAuth on first use:

```bash
grok mcp add --transport http hive https://mcp.hiveintelligence.xyz/mcp
grok mcp doctor hive
```

Use `grok mcp list` to confirm that Hive is registered. The CLI stores OAuth credentials outside the project configuration. Source: [xAI MCP Servers documentation](https://docs.x.ai/build/features/mcp-servers).

---

## Verify the connection

Start a new Grok conversation with a bounded diligence request:

> *"Use Hive to assess this token before further research. Show the security findings, liquidity evidence, source providers, freshness, and runtime status. Return pass, block, or escalate."*

Confirm that Grok shows a Hive tool call and that the answer preserves source, freshness, and runtime information from the result. A fluent answer without a Hive tool call is not proof that the connector ran.

---

## Headless xAI API alternative

For a server-side Grok agent, xAI also documents function calling. Define a narrow function in your application, validate its arguments, call Hive REST with a server-side `HIVE_API_KEY`, and return the bounded result to Grok. This is an application integration, not the connector flow above.

Use this path when you need your own allowlist, audit log, caching, or rate limits. See [xAI Function Calling](https://docs.x.ai/developers/tools/function-calling) and Hive's [REST API guide](/api-integration).

---

## Troubleshooting

**Grok cannot reach the server.** Confirm the URL is exactly `https://mcp.hiveintelligence.xyz/mcp`. Localhost URLs require tunneling; Hive's hosted URL is already public.

**No authorization window opens.** Remove the draft connector, create it again, and make sure pop-ups are allowed for Grok. Check [Hive status](/status) before retrying.

**The connector option is controlled by your organization.** Ask its admin to allow Hive through connector management.

**Tools are missing.** Refresh the connector after authorization. Hive keeps the root tool list compact; the agent uses `search_tools`, schema lookup, and bounded invocation to reach the wider catalog.

---

## Next steps

- [Live playground](/playground): verify a read-only workflow without an account.
- [Compatible MCP clients](/install/generic): understand the standards-based setup contract.
- [MCP security](/mcp-security): review consent, tool scope, and prompt-injection boundaries.