Helius MCP Server - Helius Docs

The Helius MCP server gives AI tools direct access to Helius APIs through 10 public tools — 9 routed domain tools that cover all Helius and Solana functionality, plus expandResult for paging through large responses.

9 Routed Tools

Domain-grouped tools (heliusWallet, heliusAsset, heliusTransaction, …) — every Helius action is reachable through one of them

Autonomous Signup

Create a Helius account and get an API key entirely within Claude — no browser needed

Real-Time Data

Subscribe to Enhanced WebSockets and LaserStream gRPC directly from your AI tool

Any MCP Client

Works with Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Codex, and any MCP-compatible tool

What is MCP?

The Model Context Protocol (MCP) is an open-source standard introduced by Anthropic that allows AI models to securely connect with external data sources, tools, and APIs. It uses a client-server architecture where a host (like Claude) connects to an MCP server, allowing the AI to query databases, call APIs, or execute actions through a universal, standardized interface. Why this matters for Helius: The MCP gives Claude direct access to live Solana data and Helius infrastructure — balances, asset metadata, parsed transactions, webhook management, streaming, and more. Without it, Claude has to guess at API responses or make repeated curl requests to gain context. The MCP lets Claude actually interact with Solana through Helius using structured tool calls.

The Helius docs site at helius.dev/docs also exposes a separate MCP server auto-generated by Mintlify. That server is scoped to documentation search only. helius-mcp documented here is the comprehensive server covering all Helius and Solana functionality.

Quick Start

Add the MCP server

claude mcp add helius npx helius-mcp@latest

Or add to your MCP host’s config (Claude Desktop, Cursor, Windsurf, VS Code, etc.):

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

Configure your API key

If you already have a key:

export HELIUS_API_KEY=YOUR_API_KEY

Or set it inside Claude by calling the setHeliusApiKey action on heliusAccount. API keys are resolved in this order:

setHeliusApiKey action call within the session
HELIUS_API_KEY environment variable
~/.helius/config.json (set via the Helius CLI)

If you need a new account: See Autonomous Signup below.

Start using tools

Ask questions in plain English — the right tool and action are selected automatically:

“What NFTs does this wallet own?”
“Parse this transaction: 5abc...”
“Get the balance of Gh9ZwEm...”
“Send 1 SOL to 7xKp...”
“Create a webhook for this address”

Connecting to the Helius MCP Server

Run the following command:

claude mcp add helius npx helius-mcp@latest

Or add to your project’s .mcp.json:

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

Verify with:

claude mcp list

Want skills + MCP in one step? Install the Helius plugin instead:

/plugin marketplace add helius-labs/core-ai
/plugin install helius@helius-labs

Open Settings > Developer > Edit Config and add the server:

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

Restart Claude Desktop to apply.

Open the command palette (Cmd/Ctrl + Shift + P), search for MCP: Add Server, and enter:

Name: helius
Command: npx helius-mcp@latest

Or add to your project’s .cursor/mcp.json:

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

Create a .vscode/mcp.json file in your project root:

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

Requires the GitHub Copilot extension with MCP support enabled.

Open the command palette (Cmd/Ctrl + Shift + P), search for Configure MCP Servers, and add:

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

Run the following command:

codex mcp add helius -- npx helius-mcp@latest

Or add to your ~/.codex/config.toml (or .codex/config.toml for project-scoped):

[mcp_servers.helius]
command = "npx"
args = ["helius-mcp@latest"]

Verify with:

codex mcp list

Public Tool Surface

Helius MCP exposes 10 public tools: 9 routed domain tools plus expandResult. Every Helius and Solana action is reachable as an action argument on the appropriate routed tool.

Tool	Scope
`heliusAccount`	Account setup, auth, plans, billing
`heliusWallet`	Wallet balances, holdings, history, identity
`heliusAsset`	Assets, NFTs, collections, token holders
`heliusTransaction`	Transaction parsing and wallet transaction history
`heliusChain`	Chain state, token accounts, blocks, network status, program accounts
`heliusStreaming`	Webhook CRUD and subscription config (WebSockets, LaserStream)
`heliusKnowledge`	Docs, guides, pricing, troubleshooting, source, blog, SIMDs
`heliusWrite`	Transfers — SOL and SPL tokens
`heliusCompression`	Merkle proofs for compressed NFTs
`expandResult`	Expand summary-first outputs by `resultId`

Full Tool Catalog

Every action grouped by routed tool, with call-shape details and expandResult usage

Routed tool call shape

Each of the 9 routed tools shares 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

Example call:

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

Summary-first responses and `expandResult`

Heavy responses are summary-first. Routed tools return a compact summary plus a 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. This keeps token usage low for exploratory queries while still letting agents drill into the full payload when needed. Create a Helius account from your AI tool through a hosted payment link or by paying USDC directly from a local keypair. The signup flow runs through the heliusAccount routed tool:

Generate a keypair

The AI calls heliusAccount with action: "generateKeypair" — it creates a Solana wallet and returns the address.

Create the payment intent

The AI calls heliusAccount with action: "signup" and mode: "link" — returns a paymentUrl (e.g. https://dashboard.helius.dev/pay/<id>) the user opens to pay with any wallet. Or pass mode: "autopay" to send USDC from the local keypair automatically (wallet must hold ~0.001 SOL + the plan amount in USDC).

Resume after payment

After paying via link, the AI calls heliusAccount with action: "signup" and mode: "resume" — polls the payment intent, finalizes account provisioning, and configures the API key automatically.

Paid plans (Developer / Business / Professional): signup and upgradePlan require email, firstName, and lastName. The Agent plan does not.

Or do the same from the terminal with the Helius CLI:

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 from the local keypair:
npx helius-cli@latest signup --plan agent --pay

Network Configuration

The MCP server defaults to mainnet-beta. Switch to devnet via environment variable:

export HELIUS_NETWORK=devnet

Or call the setNetwork action on heliusAccount within a session.

System Prompts

The helius-mcp package ships with pre-built system prompts that teach AI models how to use Helius tools effectively. They live 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 the helius-skills/SYSTEM-PROMPTS.md integration guide for code examples.

Skills

Skills are expert instruction sets that teach Claude how to route your requests to the right MCP actions and reference files. They go beyond raw tool access — they include routing logic, correct SDK patterns, and rules that prevent common mistakes.

Skills Overview

Four skills available: Build (general Solana dev), Phantom (frontend dApps), DFlow (trading apps), and SVM (protocol internals)

Learn More

Claude Code Plugin

One-click install of MCP + skills

Helius CLI

Command-line account management

MCP Specification

Learn about the Model Context Protocol standard

helius-mcp on npm

Package details and version history

Changelog

Version history and release notes

Contribute

Contribution guide for helius-mcp

For Agents

Documentation Index

9 Routed Tools

Autonomous Signup

Real-Time Data

Any MCP Client

​What is MCP?

​Quick Start

​Connecting to the Helius MCP Server

​Public Tool Surface

Full Tool Catalog

​Routed tool call shape

​Summary-first responses and expandResult

​Signup

​Network Configuration

​System Prompts

​Skills

Skills Overview

​Learn More

Claude Code Plugin

Helius CLI

MCP Specification

helius-mcp on npm

Changelog

Contribute

What is MCP?

Quick Start

Connecting to the Helius MCP Server

Public Tool Surface

Routed tool call shape

Summary-first responses and `expandResult`

Signup

Network Configuration

System Prompts

Skills

Learn More