WalletMCP - Solana Blockchain MCP Server

Created By
paulfruitfula year ago
A Simple MCP Server For Interacting With Solana Wallets
Overview

What is WalletMCP?

WalletMCP is a Model Context Protocol (MCP) server designed for interacting with the Solana blockchain, providing tools for developers to manage wallets, transactions, and program logs.

How to use WalletMCP?

To use WalletMCP, clone the repository from GitHub, install the dependencies, build the server, and configure it with the Claude Desktop MCP Client to start interacting with Solana wallets.

Key features of WalletMCP?

  • Retrieve wallet transactions and SOL balances.
  • Access program logs from the Solana blockchain.
  • Send SOL transactions programmatically.
  • Fully MCP-compliant tool definitions with schema validation.

Use cases of WalletMCP?

  1. Checking recent transactions of a Solana wallet.
  2. Fetching the SOL balance of a wallet.
  3. Sending SOL from one wallet to another.
  4. Managing program buffers and logs.

FAQ from WalletMCP?

  • Can WalletMCP interact with all Solana wallets?

Yes! WalletMCP is designed to work with any wallet compatible with the Solana blockchain.

  • Is WalletMCP free to use?

Yes! WalletMCP is open-source and free for everyone to use.

  • What technologies does WalletMCP use?

WalletMCP uses Solana Web3.js SDK, Model Context Protocol (MCP), Zod for validation, and is built with TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
paulfruitful
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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