Claude Desktop mcp blockchain_events__blockchain_events_manage
How to: Claude Desktop mcp blockchain_events__blockchain_events_manage
Add 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://ai.cryptoapis.io/mcp"
]
}
}
}-
02
Save the file and restart Claude Desktop.
-
03
Ask for something blockchain_events__blockchain_events_manage does. Claude Desktop lists the server's tools on connect and calls blockchain_events__blockchain_events_manage itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that 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
mcp will not start until these are set, so blockchain_events__blockchain_events_manage never becomes available.
-
CRYPTOAPIS_API_KEY
Same tool, other clients
This list was read from the server itself, by connecting to it and calling tools/list on 21 October 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.