Skip to main content
Glama

Sonar MCP

An MCP server exposing Solana network, wallet, transaction, and token-intelligence tools backed by the Helius RPC API. Built to plug directly into MCP-compatible clients such as Cursor.

Architecture Diagram

Tools

Domain

Tool

Description

Network

get_slot

Current slot at a given commitment level

Network

get_epoch_info

Epoch progress: absolute slot, block height, index

Network

get_health

RPC node health check

Wallet

get_sol_balance

SOL balance for a wallet address

Wallet

get_token_accounts_by_owner

SPL token holdings for a wallet

Transactions

get_transaction

Full transaction detail by signature

Transactions

get_signatures_for_address

Recent transaction signatures for an address

Tokens

get_token_supply

Supply and decimals for an SPL token mint

Related MCP server: Solana AI Terminal

Prerequisites

Setup

git clone <your-repo-url> sonar-mcp
cd sonar-mcp
uv sync
cp .env.example .env

Edit .env:

HELIUS_API_KEY=your-key-here
SOLANA_NETWORK=devnet   # or mainnet

Running

Launch the MCP Inspector for local testing:

uv run mcp dev src/sonar_mcp/server.py

This opens a browser UI where each tool can be called directly against Helius before wiring the server into a client.

Using with Cursor

Add to .cursor/mcp.json (project-level) or your global Cursor MCP config:

{
  "mcpServers": {
    "sonar": {
      "command": "uv",
      "args": ["run", "--directory", "/absolute/path/to/sonar-mcp", "sonar-mcp"]
    }
  }
}

Reload MCP servers in Cursor and the 8 tools will appear under sonar.

Project structure

sonar-mcp/
├── .env.example
├── pyproject.toml
├── README.md
└── src/
    └── sonar_mcp/
        ├── instance.py      # shared MCPServer instance
        ├── server.py        # entrypoint, registers tool modules
        ├── config.py        # env + RPC URL
        ├── rpc_client.py    # shared Helius JSON-RPC POST helper
        └── tools/
            ├── network.py
            ├── wallet.py
            ├── transactions.py
            └── tokens.py

Notes

  • Built on MCP Python SDK v2 (mcp.server.MCPServer). The old FastMCP class from mcp.server.fastmcp was renamed and moved in v2 — if you're reading examples elsewhere that import FastMCP, they're targeting SDK v1.

  • All Solana RPC calls go through Helius directly; this server does not call the original Sonar FastAPI service.

  • RpcError responses are returned as {"error": ...} payloads rather than raised, so tool calls degrade gracefully instead of crashing the MCP session.

Available Tools

8 tools
get_epoch_infoB

Get current epoch progress: absolute slot, block height, epoch, slot index/total.

Inputs: commitment, min_context_slot.

get_healthA

Check whether the RPC node is healthy.

Inputs: no named parameters.

get_signatures_for_addressB

Get recent transaction signatures involving an address.

Inputs: address (required), limit.

get_slotA

Get the current slot the node has reached, at the given commitment level.

Inputs: commitment.

get_sol_balanceA

Get the SOL balance (in lamports and SOL) for a wallet address.

Inputs: address (required), commitment.

get_token_accounts_by_ownerA

List SPL token accounts owned by a wallet, optionally filtered to one mint.

Inputs: address (required), mint.

get_token_supplyA

Get total supply and decimals for an SPL token mint.

Inputs: mint (required).

get_transactionA

Get full details for a transaction by its signature.

Inputs: signature (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    Each tool targets a distinct resource or query, but get_slot and get_epoch_info overlap slightly since both report the current slot. The descriptions clarify their different scopes, so ambiguity is minimal.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with the 'get_' prefix. Variations like get_epoch_info or get_token_supply still adhere to the pattern, and there is no mixing of styles.

    Tool Count5/5

    Eight tools is well within the ideal range and appropriate for a read-only Solana RPC server. Each tool provides a needed query without bloat or redundancy.

    Completeness4/5

    The set covers core Solana read operations: slot, epoch, health, balances, token accounts, transactions, signatures, and supply. Missing queries like get_block or get_program_accounts are minor gaps, and the server's scope is clearly read-only.

    Related MCP Connectors

    Related MCP Servers