Solana Model Context Protocol (MCP) Demo

Created By
solana-foundationa year ago
Solana Model Context Protocol (MCP) Demo
Overview

What is Solana Model Context Protocol (MCP) Demo?

The Solana Model Context Protocol (MCP) Demo is a repository that showcases a simple implementation of a Model Context Protocol server designed for Solana development, enabling AI models to interact with tools and resources.

How to use Solana MCP?

To use the Solana MCP, clone the repository, install the dependencies, and run the server using the provided commands. You can also generate a configuration file for integration with other tools like Claude, Windsurf, and Cursor.

Key features of Solana MCP?

  • Basic RPC methods for Solana (getBalance, getAccountInfo, getTransaction)
  • Helpful prompts for Solana development
  • Extensible server for adding more tools and resources

Use cases of Solana MCP?

  1. Developing and testing Solana applications.
  2. Integrating AI models with Solana tools.
  3. Creating custom RPC endpoints for specific needs.

FAQ from Solana MCP?

  • What is the purpose of the MCP?

The MCP standardizes how AI models interact with tools and resources, making it easier for developers to build applications.

  • Is there a guide for extending the MCP?

Yes! The repository includes ideas and guidelines for extending the MCP server with new tools and features.

  • What are the prerequisites for running the MCP server?

You need Node.js (v16 or higher) and the pnpm package manager.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
solana-foundation
Star
4
Language
TypeScript
License
MIT 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