Solana MCP Server

Created By
aldrin-labsa year ago
solana mcp sever to enable solana rpc methods
Overview

What is Solana MCP Server?

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.

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 in the Solana blockchain.
  3. Getting the current inflation rate of the Solana network.

FAQ from Solana MCP Server?

  • What RPC methods are supported?

The server supports 21 essential RPC methods including balance checks, transaction details, and system information.

  • Is there a default RPC endpoint?

Yes, the default RPC endpoint is "https://api.mainnet-beta.solana.com" unless specified otherwise.

  • 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
aldrin-labs
Star
18
Language
Rust
License
Unlicense license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

16 hours ago
Voyei

6 hours ago