---
title: Connect Hive to Windsurf
lastUpdated: '2026-06-03'
nextjs:
  metadata:
    title: "Install Hive in Windsurf | Crypto MCP Setup"
    description: "Connect Windsurf's Cascade agent to Hive's remote MCP endpoint for live crypto prices, DeFi, wallets, and security tools."
    alternates:
      canonical: https://www.hiveintelligence.xyz/install/windsurf
    keywords: "windsurf crypto, windsurf mcp, hive windsurf, codeium crypto, windsurf cascade crypto"
---

**Connect Windsurf to Hive so Cascade can call live crypto tools from your editor.** Add the remote MCP server to `mcp_config.json`, restart Windsurf, then verify a Hive price query. {% .lead %}

{% ai-doc-actions path="/install/windsurf" title="Windsurf Install Guide" /%}

---

## Before you start

1. Windsurf installed from [codeium.com/windsurf](https://codeium.com/windsurf).
2. A Hive API key from [/dashboard/keys](/dashboard/keys).

---

## Configure Windsurf

### 1. Open the MCP config file

Windsurf reads MCP servers from `~/.codeium/windsurf/mcp_config.json`. Create the file if it doesn't exist.

### 2. Add this config

```json
{
  "mcpServers": {
    "hive": {
      "serverUrl": "https://mcp.hiveintelligence.xyz/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_HIVE_API_KEY"
      }
    }
  }
}
```

Replace `YOUR_HIVE_API_KEY` with the key from [/dashboard/keys](/dashboard/keys).

Windsurf's current MCP docs use `serverUrl` for remote servers. Hive connects directly over Streamable HTTP, so there is no local Node subprocess in the default path.

### Stdio fallback

If your Windsurf build does not support remote MCP yet, or your network requires a local wrapper, use stdio instead:

```json
{
  "mcpServers": {
    "hive": {
      "command": "npx",
      "args": ["-y", "-p", "hive-intelligence", "hive"],
      "env": {
        "HIVE_API_KEY": "YOUR_HIVE_API_KEY"
      }
    }
  }
}
```

In the fallback path, Windsurf spawns `npx -y -p hive-intelligence@latest hive` as a local subprocess and hands it the key via `HIVE_API_KEY`. The wrapper forwards requests to `mcp.hiveintelligence.xyz` with the same Bearer token the remote config uses.

### 3. Restart Windsurf

Quit Windsurf fully and reopen. Cascade will pick up the Hive MCP server on launch.

### 4. Verify it worked

Open Cascade (⌘L on macOS) and ask:

> *"Using the Hive MCP server, what is the current price of BTC and ETH?"*

Cascade should call Hive's `get_price` tool and return live data.

---

## What to ask in Windsurf

- *"Write a Python script that pulls top DeFi yields from Hive and posts a daily summary to Slack."*
- *"Check this contract address for security issues before I deploy code that calls it: 0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48"*
- *"Build me a Next.js API route that returns the current BTC funding rate from supported exchanges."*
- *"Given this wallet address, show me current holdings and 24h P&L — generate the fetch code."*

Cascade mixes Hive tool calls with code generation — the agent picks the right tool per step.

---

## Troubleshooting

**Cascade doesn't list Hive.** Confirm `~/.codeium/windsurf/mcp_config.json` exists and is valid JSON. Restart Windsurf.

**"npx: command not found".** Install Node.js 20+ from [nodejs.org](https://nodejs.org), then restart Windsurf.

**API key rejected.** Verify at [/dashboard/keys](/dashboard/keys); keys are whitespace-sensitive.

---

## Other clients

- [Cursor](/install/cursor) — similar IDE, wider MCP ecosystem
- [VS Code](/install/vs-code) — for GitHub Copilot Chat users
- [All clients](/install) — full list

---

## Next steps

- [Agent Resources](/ai-agent-hub) — what Cascade can build once connected
- [Tools Reference](/tools) — every tool Cascade can call