Introducing SubQuery CLI Support for the SubQuery Network

Introducing SubQuery CLI Support for the SubQuery Network

The SubQuery Network is the fastest, most flexible data indexing solution in web3 technology. Until now, interacting with the network required navigating the SubQuery Explorer or integrating with APIs. With this release, we’re bringing that same power directly to your terminal.

For developers building web3 apps, this means less friction, faster deployments, and more control over your data infrastructure. Whether you’re an indexer or a project maintainer, you can now manage every part of your SubQuery project with a single CLI tool.

New CLI Capabilities on the SubQuery Network

The SubQuery CLI now supports direct network operations, giving developers a streamlined way to create, manage, and optimize projects. This is an alternative to using the SubQuery Network App and great for users who are more comfortable using their CLI. 

Here’s what you can do today:

  • Create a project and prepare it for indexing
  • Deploy a project to the SubQuery Network
  • Request a list of your projects or project deployments
  • Check boosts and indexers running your project
  • Add, remove, or swap deployment boosts to optimize performance
  • Create, list, and stop flex plans
  • Manage API keys (add or remove with ease)

All of these operations are available from your terminal, powered by the same MCP tools developers are already familiar with.

Example 1: Deployment Indexers in the SubQuery CLI

This first example shows how you can find a list of the indexers working on your project deployment on the SubQuery Network.

You can see the response lists 9 indexers serving a deployment on the Base network. Each indexer shows status, address, and rate limits. All are healthy and synced.

Asking Claude MCP using plain english:

Claude MCP response listing 9 healthy indexers serving a project deployment on the Base network.

Entering a CLI command:

SubQuery CLI listing 9 healthy indexers serving a project deployment on the Base network.

Example 2: Active Flex Plan in the SubQuery CLI

This example demonstrates how you can use a command in the CLI or simply ask Claude MCP in plain english (depending what you prefer to use) about your Flex Plan on the SubQuery Network.

The response shows the active flex plan plus deployment details, maximum credit, current spend, status, and expiry. This plan indexes NFT transfers on the Base network.

Asking Claude MCP using plain english:

Claude MCP response to query showing an active flex plan indexing project transfers on Base network.

Entering a CLI command:

SubQuery CLI showing an active flex plan indexing project transfers on Base network.

Security Best Practices When Using the CLI

Some commands require you to sign messages or transactions. You can do this securely by connecting your wallet via WalletConnect using the connect wallet command.

⚠️ While the CLI supports setting a private key via environment variables, we discourage this practice due to security risks. Always prefer WalletConnect for secure signing.

How to Get Started

  1. Make sure you have the latest SubQuery CLI installed.
  2. Run subql connect wallet to securely connect your wallet.
  3. Use the new commands to create, deploy, and manage your projects directly from the terminal or via the MCP tools.

For details on the new command features, check out the CLI references documentation.

Common Questions About the SubQuery Network

What is a SubQuery Network?

The SubQuery Network is a decentralized data infrastructure protocol that makes blockchain data more accessible for developers, projects, and enterprises. Instead of running centralized indexers or RPCs, the network connects consumers who need infrastructure with a global marketplace of indexers and node runners who supply it. 

What chains are supported by SubQuery?

SubQuery supports a wide range of blockchains across multiple ecosystems, including  Ethereum, Solana, Polkadot, Avalanche, Cosmos, Algorand, NEAR, and more. The protocol is designed to be multi-chain from the ground up with new chains added regularly. A full, up-to-date list of supported chains can be found here.

What is a SQT token?

SQT is the utility token of the SubQuery Network. It’s used by consumers to pay for data queries and indexing, while rewarding node operators and incentivizing participation across the network.

TL;DR

This is a major step forward for developer experience on the SubQuery Network. By bringing network interactions into the CLI, we’re making it faster and simpler for teams to deploy, manage, and scale their web3 technology projects.

Whether you’re building the next breakthrough in web3 apps or running powerful indexers behind the scenes, the new SubQuery CLI support gives you the tools to succeed.

👉 Try it out today and start managing your projects on the SubQuery Network directly from your terminal.

If you have any questions, reach out on our socials!

About SubQuery

SubQuery Network is innovating web3 infrastructure with tools that empower builders to decentralise without compromise. SubQuery’s infrastructure network offers both data indexers and RPCs — fully decentralised, production-ready, and designed for scale.

Our fast, flexible, and open data indexer supercharges thousands of dApps on nearly 300 networks. Through innovations like AI-assisted development via the SubQuery SDK and Model Context Protocol (MCP) integration, SubQuery is making it easier than ever to build, deploy, and maintain blockchain indexers. We’re not just a company — we’re a movement driving an inclusive and decentralised web3 era, together.

​​​​Linktree | Website | Discord | Telegram | Twitter | Blog | Medium | LinkedIn | YouTu

Share Post

share with linked inshare with githubshare with x
Brittany Seales

Brittany Seales · Head of Marketing

Head of Marketing at SubQuery Network

You might also like