Gemini CLI mcp block_data__evm_block_data
How to: Gemini CLI mcp block_data__evm_block_data
Add mcp to Gemini CLI
-
01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"mcp": {
"httpUrl": "https://ai.cryptoapis.io/mcp"
}
}
}-
02
Save the file and restart Gemini CLI.
-
03
Ask for something block_data__evm_block_data does. Gemini CLI lists the server's tools on connect and calls block_data__evm_block_data 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.
Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs
Set these first
mcp will not start until these are set, so block_data__evm_block_data 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.