Skip to main content
The SQD extension connects Gemini CLI to blockchain data across 130+ networks through the hosted Portal MCP server. MCP query tools cover EVM networks, Solana, Polkadot and other Substrate networks, Bitcoin, and Hyperliquid. Tron discovery, head, freshness, and timestamp lookups are available through MCP, while the bundled Portal skill documents native Tron Stream API queries. The extension adds 28 read-only MCP tools plus four skills for Portal, Pipes SDK, and Squid SDK projects.
Before you start: install Gemini CLI. Run the install commands below in your terminal, not inside a Gemini session.

Install

1

Install SQD from GitHub

No SQD account, API key, or extension setting is required.
2

Confirm the extension is active

You should see sqd version 0.8.3.
3

Start a new Gemini session

Gemini loads extensions when a session starts. Start a new session, then run /extensions list to confirm SQD is enabled.
Direct installation from GitHub works while the Gemini CLI extension gallery completes its automatic indexing.

What gets added

Try it

  • “Show me the last 200 BTC perp fills on Hyperliquid.”
  • “How many transactions landed on Base in the past 2h?”
  • “Show me the latest 20 USDC transfers on Base from the past hour.”
  • “Track USDT transfers on Tron.”
  • “Migrate this Squid SDK project from the v2 gateway to Portal.”
  • “Build a Pipes SDK indexer for USDC transfers on Ethereum.”
For a bounded data question, Gemini should call a portal_ tool and return query results. The bundled Portal skill handles raw exports, including data shapes not exposed as a dedicated MCP tool. The other skills help build Pipes SDK indexers, migrate Squid SDK projects, and compare Squid sync performance.

Troubleshooting

  • sqd does not install: confirm git is installed, then run the install command again outside an active Gemini session.
  • Tools or skills do not appear: restart Gemini CLI and run /extensions list.
  • Update an existing install: run gemini extensions update sqd, then restart Gemini CLI.
  • Prefer manual MCP setup: configure the endpoint from the Portal MCP Server page instead.