MadeOnSol research · MCP servers
Solana MCP Servers Compared: Solana Foundation, Helius, Bitquery & Pyth
Reviewed October 12, 2026 · 4 documented options · First-party sources linked below
A Solana MCP server connects an AI client such as Claude, Cursor or an agent runtime to external tools. But 'Solana MCP' does not describe one interchangeable product: documentation retrieval, chain operations, DEX analytics and market-price feeds require different servers.
This comparison covers four documented options that solve distinct jobs. It is a use-case guide, not a ranking by installations, latency or undisclosed sponsorship. Verify client compatibility and credentials before making an integration decision.
Short answer: which option fits?
For coding assistance and current Solana documentation, start with the Solana Foundation's developer MCP. For wallet, transaction, asset and operational API workflows, evaluate Helius. For read-only DEX and transfer research, look at Bitquery. For market-price feeds, consider Pyth.
Four options, side by side
Compare by need, not by a fabricated score| Product | Primary use | Connection | Access & permissions |
|---|---|---|---|
| Solana Developer MCPOfficial website | Solana docs, semantic retrieval and program checks | Hosted Streamable HTTP MCP endpoint | No API key for the documented developer endpoint; no wallet signing |
| Helius MCPOfficial website | Wallets, assets, transactions, streaming configuration and writes | Locally launched npm MCP server | Helius API key; some tools can create or sign on-chain actions |
| Bitquery MCPOfficial website | DEX trades, transfers, OHLC candles and wallet history | Hosted remote MCP with OAuth | Read-only dataset queries; Bitquery account and plan limits apply |
| Pyth MCPOfficial website | Feed discovery, latest prices, historical prices and candles | Hosted Streamable HTTP MCP endpoint | Feed discovery has an optional key; price tools require Pyth Pro authorization |
The comparison describes documented products, not tested latency, throughput, market share or universal fee guarantees.
Methodology and verification
We selected four identifiable first-party MCP implementations with distinct use cases, then checked the vendors' current official setup and tool documentation on 12 October 2026. The columns compare documented capabilities, not measured performance. No comparative load or latency benchmark was performed, and tool counts or pricing can change.
Each product links to the provider's own documentation. Check current pricing, eligibility, tool permissions and network support before relying on any comparison for production.
Where each product fits — and where it does not
The differences below matter more than arbitrary best-to-worst rankings. Features are based on vendor documentation, not synthetic scores or hands-on speed tests.
Solana Developer MCP
Best fit: Developers asking how to build or debug Solana programs
Maintained by the Solana Foundation, this server retrieves up-to-date documentation, answers ecosystem questions and checks Anchor or Pinocchio program source. It is the most direct starting point when an IDE assistant needs source-grounded coding guidance rather than live trading data.
Documented strengths
- First-party developer documentation rather than third-party summaries.
- Dedicated program autofixer and canonical documentation lookup.
- Remote endpoint means no Solana wallet is needed to get started.
Check before choosing: It is not a DEX trade feed or a transaction executor. Documentation answers do not replace testing your program on devnet.
Helius MCP
Best fit: Operational blockchain queries and Helius API workflows
Helius's official AI tooling includes an MCP server with ten public tools in total: nine routed domains plus a result-expansion tool. The domains cover wallet, asset, chain, transaction, streaming and write operations, including transfers and webhook configuration. It suits agents that need Helius functionality, provided approvals and API-key permissions are controlled.
Documented strengths
- Documented wallet, asset and transaction queries via nine routed domains.
- Streaming/webhook administration alongside data retrieval.
- Optional write operations for workflows designed to permit them.
Check before choosing: Do not grant signing or webhook-mutation tools to an untrusted agent by default. Verify the exact package version and API permissions deployed.
Bitquery MCP
Best fit: Market research and transaction-flow investigations
Bitquery's hosted MCP is a read-only interface to indexed blockchain activity. Its Solana guide describes DEX trades, launch patterns, transfers and wallet flow analysis, with OAuth authentication. Its documented Solana trade history is approximately 30 days in this MCP workflow; do not mistake it for unlimited historical API access.
Documented strengths
- Trading and transfer views in the same data service.
- OHLC views and transfer tracing for market investigation, within the MCP dataset's documented windows.
- Explicitly read-only operations, avoiding transaction signing.
Check before choosing: The documented MCP trade lookback is about 30 days and transfer tools default to 90 days, unlike some of the provider's full APIs. Check date windows and freshness before using results in trading automation.
Pyth MCP
Best fit: AI assistants that need structured asset-price data
Pyth's hosted MCP exposes specialist market-data tools rather than broad wallet and transaction indexing. Its documented functions include discovering symbols, fetching recent or historical observations, and returning chart-ready price data for supported instruments.
Documented strengths
- Purpose-built market-price tool surface.
- Hosted MCP endpoint instead of local package setup.
- Explicit distinction between discovery and authenticated price tools.
Check before choosing: A price-feed query is not a token-risk scan or full DEX trade tape. Check feed coverage, entitlement and freshness for each instrument.
How to choose in practice
Choose by the question your agent must answer
'Why does this Anchor instruction fail?' needs the Solana Developer MCP. 'What happened to this wallet or transaction?' fits a chain-data tool such as Helius. 'Which tokens and transfers dominated a period?' calls for indexed market data such as Bitquery. 'What is this asset's latest documented feed price?' is a Pyth-style question.
Read-only and transaction-capable servers are different risk classes
A server that retrieves documents or prices usually needs narrower permissions than one that can transfer tokens or configure webhooks. Separate developer and production credentials, limit tool exposure by use case, and require human or explicit policy approval for financial mutations.
Compare freshness and coverage before promising real time
A hosted analytics index, a price feed and a blockchain RPC observe different event families. Ask about ingestion delay, supported programs or assets, historical depth, rate limits and what happens when a backend falls behind. None is automatically a substitute for a latency-sensitive trade stream.
Frequently asked questions
What is the official Solana MCP server?
The Solana Foundation runs the Solana Developer MCP at mcp.solana.com. Its documented scope is developer knowledge retrieval and program checking, not a universal wallet or trading API.
Which Solana MCP server can send transactions?
The Helius MCP documentation includes write-oriented tools. Treat such actions as privileged and use explicit approval policies; the Solana Developer, Bitquery and Pyth options discussed here serve primarily retrieval use cases.
Is a Solana MCP server the same as a Solana RPC node?
No. MCP is a tool interface for AI clients. An MCP server may rely on RPC, indexed databases, documents or market-data services behind the scenes, but its available tool set is determined by the provider.
Which is best for AI-assisted trading research?
Choose the inputs you need: Bitquery offers indexed trade and transfer analytics, Pyth offers price-feed tools, and Helius exposes broader chain queries. Check coverage and latency for the exact strategy; none of those descriptions implies a live pre-confirmation signal.