helius

Helius MCP Server

MCP server for Helius — Solana blockchain data access for AI assistants, provided by Solana's fastest, most reliable infrastructure provider

See the CHANGELOG for version history and release notes.

Interested in contributing? Read the contribution guide before opening a PR.

Quick Start

1. Add the MCP server

Add to your MCP host's config (works with Claude, Cursor, Windsurf, and any MCP-compatible client):

{
  "mcpServers": {
    "helius": {
      "command": "npx",
      "args": ["helius-mcp@latest"]
    }
  }
}

Or if you're using Claude Code:

claude mcp add helius npx helius-mcp@latest

2. Configure your API key

If you already have a Helius API key:

export HELIUS_API_KEY=your-api-key

Or set it from your AI assistant by calling the setHeliusApiKey tool.

If you need a new account:

The MCP includes a signup tool with three modes:

1. Call the generateKeypair tool — it creates a Solana wallet and returns the address
2. Call signup with mode: "link" — returns a paymentUrl (e.g. https://dashboard.helius.dev/pay/<id>) you open in any browser to pay with any wallet
3. After paying in the browser, call signup with mode: "resume" — finalizes provisioning and configures the API key automatically
4. Or skip the browser: call signup with mode: "autopay" to pay USDC from the local keypair (wallet must hold ~0.001 SOL + the plan amount in USDC)

All paid plans: signup and upgradePlan require email, firstName, and lastName for new signups (every plan, including Agent).

Or do the same from the terminal:

npx helius-cli@latest keygen                  # Generate keypair
npx helius-cli@latest signup --plan agent     # Print hosted payment link
# (pay in browser, then:)
npx helius-cli@latest signup --resume         # Finalize account
# Or autopay USDC from the local keypair:
npx helius-cli@latest signup --plan agent --pay

3. Start using tools

Ask questions in plain English — the right tool is selected automatically:

• "What NFTs does this wallet own?"
• "Parse this transaction: 5abc..."
• "Get the balance of Gh9ZwEm..."
• "Create a webhook for <address>"

Public Tool Surface

Helius MCP exposes 11 public tools total: 10 routed domain tools plus expandResult.

• heliusAccount — account setup, auth, plans, billing
• heliusWallet — wallet balances, holdings, wallet history, identity
• heliusAsset — assets, NFTs, collections, token holders
• heliusTransaction — transaction parsing and wallet transaction history
• heliusChain — chain state, token accounts, blocks, network status, stake reads, transaction and Jito bundle simulation, bundle status
• heliusStreaming — webhook CRUD, subscription config, Parsed Streams program discovery, Preconfirmations coverage
• heliusKnowledge — docs, guides, pricing, troubleshooting, source, blog, SIMDs
• heliusWrite — transfers and staking mutations
• heliusCompression — compressed account, balance, proof, and history actions
• heliusPrivacy — Solana Privacy Rings indexer reads: encrypted UTXOs and shielded transactions by view tag, nullifier, or signature, Merkle and non-inclusion proofs, and user records
• expandResult — expand summary-first outputs by resultId

The 10 routed domain tools share a common shape:

• action — the Helius action name to run, such as getBalance or createWebhook
• domain-specific params — for example address, signatures, or webhookURL
• optional detail — summary, standard, or full
• telemetry fields — _feedback, _feedbackTool, _model

Each routed tool takes an action field with the Helius action name:

{
  "name": "heliusWallet",
  "arguments": {
    "action": "getBalance",
    "address": "Gh9ZwEmdLJ8DscKNTkTqPbNwLNNBjuSzaG9Vp2KGtKJr",
    "_feedback": "initial balance check",
    "_feedbackTool": "heliusWallet.getBalance",
    "_model": "your-model-id"
  }
}

Heavy responses are summary-first. Routed tools return a compact summary plus resultId when the full response would be large or when detail: "summary" is requested. Use expandResult with that resultId to fetch a specific section, range, page, or continuation slice on demand.

Read-only mode

Start the server with --read-only, or set HELIUS_MCP_READ_ONLY=1, to serve only actions that do not change state:

claude mcp add helius-read-only -- npx helius-mcp@latest --read-only

The read-only server lists 10 tools: heliusWrite is removed, and every other tool lists only its read actions. That rules out transfers, staking, webhook create/update/delete, setHeliusApiKey, generateKeypair, signup, and billing. recommendStack stays, without its remember option. Every tool is annotated readOnlyHint: true. Configure the API key with HELIUS_API_KEY, since setHeliusApiKey is not available.

System Prompts

This package ships with pre-built system prompts that teach AI models how to use Helius tools effectively. Find them in system-prompts/:

system-prompts/
├── helius/              # Core Helius skill
├── helius-dflow/        # DFlow trading skill
├── helius-phantom/      # Phantom frontend skill
└── svm/                 # SVM architecture skill

Each contains three variants:

• openai.developer.md — for OpenAI Responses/Chat Completions API (developer message)
• claude.system.md — for Claude API (system prompt)
• full.md — self-contained with all references inlined (Cursor Rules, ChatGPT, etc.)

See helius-skills/SYSTEM-PROMPTS.md for integration guides and code examples.

Networks

Mainnet Beta (default) and Devnet. Set via HELIUS_NETWORK env var or setNetwork in the session

Related Resources

• Full Documentation
• LLM-Optimized Docs
• API Reference
• Billing and Credits
• Rate Limits
• Dashboard
• Status Page
• Full Agent Signup Instructions