Solana MCP Server

Created By
MCP-Mirrora year ago
Mirror of
Overview

What is Solana MCP Server?

The Solana MCP Server is a Model Context Protocol (MCP) server that provides comprehensive access to Solana blockchain data through Cline, implementing a wide range of Solana RPC methods for easy querying of blockchain information via natural language.

How to use Solana MCP Server?

To use the Solana MCP Server, configure it in your Cline MCP settings file and restart Cline. You can then interact with the Solana blockchain using natural language queries.

Key features of Solana MCP Server?

  • Provides 21 essential Solana RPC methods for various operations.
  • Supports account and balance operations, block and transaction information, token operations, system information, and staking & governance.
  • Allows natural language interaction for querying blockchain data.

Use cases of Solana MCP Server?

  1. Querying SOL balance for a specific address.
  2. Retrieving information about the latest block on the Solana blockchain.
  3. Checking the current inflation rate of the Solana network.

FAQ from Solana MCP Server?

  • What RPC methods are available?

The server provides methods for account operations, block information, token operations, and more.

  • Do I need to specify an RPC URL?

You can use the default RPC URL or specify your own in the environment variables.

  • What are the prerequisites for development?

You need Rust, Cargo, and optionally Solana CLI tools for testing.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago