SolanaViz MCP Server

A Model Context Protocol (MCP) server that enables Claude to access, analyze, and visualize Solana blockchain data through natural language conversations. Exposed over MCP by the solanaviz mcp server, that capability becomes something an assistant can invoke while it works, not something you go and do afterwards.

What it actually does

• Data Analysis — Fetch and analyze Solana blockchain data, tokens, and wallet information
• Visualization — Generate text-based visualizations for data exploration
• Price Predictions — AI-driven price forecasts for tokens
• Security Analysis — Evaluate security risks for tokens and protocols
• Multi-wallet Support — Analyze any Solana wallet, including your own

Adding it to your client

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Its toolset

Everything the assistant can do here goes through one of these:

• set_wallet — Set or change the active wallet address for analysis
• get_token_data — Retrieve comprehensive token information and metrics
• get_wallet_tokens — Analyze token holdings in a wallet address
• get_price_history — Fetch historical price data for a token
• get_token_pairs — Analyze trading pairs across DEXes
• get_trending_tokens — Identify currently trending tokens on Solana
• get_price_prediction — Generate AI-driven price forecasts for tokens
• get_token_security — Evaluate security risks for tokens and protocols
• generate_sankey_diagram — Visualize flows between entities (tokens, protocols, wallets)
• generate_treemap — Visualize hierarchical data with nested rectangles
• generate_heatmap — Visualize data intensity across categories
• generate_network_graph — Visualize relationships and connections between entities

Configuration

You will need 5 environment variables: BIRDEYE_API_KEY, COINGECKO_API_KEY, ALLORA_API_KEY, HELIUS_RPC_URL, DEFAULT_WALLET_ADDRESS. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

• Node.js 18+ - npm or pnpm - Claude Desktop (for using the MCP server) - API Keys: - BirdEye - CoinGecko - Allora - Helius (Solana RPC provider)

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch SolanaViz.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the solanaviz mcp server does with a few real requests.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. SolanaViz's toolset — set_wallet, get_token_data, get_wallet_tokens and 11 more — is a fair guide to whether it matches your workflow. It is maintained by FarseenSh; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.