Claude Desktop Hive Intelligence MCP invoke_api_endpoint
How to: Claude Desktop Hive Intelligence MCP invoke_api_endpoint
Add Hive Intelligence MCP to Claude Desktop
-
01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"mcp": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.hiveintelligence.xyz/mcp"
]
}
}
}-
02
Save the file and restart Claude Desktop.
-
03
Ask for something invoke_api_endpoint does. Claude Desktop lists the server's tools on connect and calls invoke_api_endpoint 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 Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs
Set these first
Hive Intelligence MCP will not start until these are set, so invoke_api_endpoint 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.