Claude.ai Hive Intelligence MCP get_api_endpoint_schema
How to: Claude.ai Hive Intelligence MCP get_api_endpoint_schema
Add Hive Intelligence MCP to Claude.ai
-
01
Open Settings → Connectors → Add custom connector and merge this in. Keep any servers already there.
https://mcp.hiveintelligence.xyz/mcp-
02
Save the file and restart Claude.ai.
-
03
Ask for something get_api_endpoint_schema does. Claude.ai lists the server's tools on connect and calls get_api_endpoint_schema itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that Hive Intelligence MCP's identifier in your config matches the one above exactly.
Claude on the web takes a remote URL and completes OAuth in the browser. For a packaged server use Claude Desktop or Claude Code instead. Claude.ai docs
Set these first
Hive Intelligence MCP will not start until these are set, so get_api_endpoint_schema never becomes available.
-
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 tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.