Skip to content

Zed Hive Intelligence MCP Prompt/analyze_token

How to: Zed Hive Intelligence MCP analyze_token

client:Zed transport:streamable-http prompt:analyze_token

Add Hive Intelligence MCP to Zed

  1. 01

    Open ~/.config/zed/settings.json and merge this in. Keep any servers already there.

{
  "context_servers": {
    "mcp": {
      "url": "https://mcp.hiveintelligence.xyz/mcp"
    }
  }
}
  1. 02

    Save the file and restart Zed.

  2. 03

    analyze_token is surfaced in the client's prompt or command menu. Unlike a tool, you invoke it deliberately — Zed will not call it for you.

  3. 04

    If it does not appear, check that Hive Intelligence MCP is connected and that you are looking at its prompts rather than its tools.

Merge this into your existing settings object — do not replace the file. Zed docs

Set these first

Hive Intelligence MCP will not start until these are set, so it never reaches Zed.

  • COINGECKO_PRO_API_KEY
  • ALCHEMY_API_KEY
  • GOPLUS_APP_KEY
  • GOPLUS_APP_SECRET
  • HELIUS_API_KEY
  • MORALIS_API_KEY
  • TENDERLY_API_KEY
  • TENDERLY_NODE_ACCESS_KEY
  • TENDERLY_GATEWAY_ACCESS_KEY
  • TENDERLY_ACCOUNT_SLUG
  • TENDERLY_PROJECT_SLUG

Same prompt, other clients

Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026. A listing does not declare its prompts, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each prompt's arguments.