Solana Agent Kit MCP server that lets Claude use a configured Solana wallet and RPC endpoint for on-chain actions such as wallet balance checks, asset lookup, token deployment, transfers, NFT minting, token trades, domain resolution, TPS checks, and test-fund requests.
Solana MCP Server can expose on-chain actions including transfers, token trades, NFT minting, token deployment, and wallet operations through Solana Agent Kit., Blockchain transactions can be irreversible and can lose funds through wrong recipients, bad slippage, malicious tokens, compromised prompts, or incorrect network selection., Use a dedicated low-balance wallet, keep autoApprove empty, and never connect a primary wallet or seed phrase to an AI-controlled tool session., The reviewed source decodes SOLANA_PRIVATE_KEY into a KeypairWallet and loads the Solana Agent Kit God Mode plugin, so the private key grants real signing authority to the MCP process., The reviewed installer script prints the entered private-key value during validation, so prefer manual npm configuration or review and patch the script before using it., RPC providers, token price sources, marketplaces, and Solana network state can be delayed, rate-limited, incomplete, or manipulated.
Privacy notes
Wallet addresses, balances, token holdings, transaction intents, trade targets, domain lookups, NFT metadata, RPC URLs, and prompts can be sent to the MCP client, model, RPC provider, or downstream Solana services., SOLANA_PRIVATE_KEY is a signing secret and should never be pasted into prompts, public issues, screenshots, shell history, committed MCP config, or installer debug output., On-chain actions are public and can permanently link wallet addresses, timing, assets, counterparties, and strategy to the configured wallet., The repository license file is Apache-2.0 while README and package metadata currently mention MIT, so verify current licensing before redistribution or commercial reuse.
Author
SendAI
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
6 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens.
4 areas
SafetyCredentials & tokensSolana MCP Server can expose on-chain actions including transfers, token trades, NFT minting, token deployment, and wallet operations through Solana Agent Kit.
SafetyCredentials & tokensBlockchain transactions can be irreversible and can lose funds through wrong recipients, bad slippage, malicious tokens, compromised prompts, or incorrect network selection.
SafetyCredentials & tokensUse a dedicated low-balance wallet, keep autoApprove empty, and never connect a primary wallet or seed phrase to an AI-controlled tool session.
SafetyCredentials & tokensThe reviewed source decodes SOLANA_PRIVATE_KEY into a KeypairWallet and loads the Solana Agent Kit God Mode plugin, so the private key grants real signing authority to the MCP process.
SafetyExecution & processesThe reviewed installer script prints the entered private-key value during validation, so prefer manual npm configuration or review and patch the script before using it.
SafetyCredentials & tokensRPC providers, token price sources, marketplaces, and Solana network state can be delayed, rate-limited, incomplete, or manipulated.
PrivacyCredentials & tokensWallet addresses, balances, token holdings, transaction intents, trade targets, domain lookups, NFT metadata, RPC URLs, and prompts can be sent to the MCP client, model, RPC provider, or downstream Solana services.
PrivacyCredentials & tokensSOLANA_PRIVATE_KEY is a signing secret and should never be pasted into prompts, public issues, screenshots, shell history, committed MCP config, or installer debug output.
PrivacyGeneralOn-chain actions are public and can permanently link wallet addresses, timing, assets, counterparties, and strategy to the configured wallet.
PrivacyLocal filesThe repository license file is Apache-2.0 while README and package metadata currently mention MIT, so verify current licensing before redistribution or commercial reuse.
Safety notes
Solana MCP Server can expose on-chain actions including transfers, token trades, NFT minting, token deployment, and wallet operations through Solana Agent Kit.
Blockchain transactions can be irreversible and can lose funds through wrong recipients, bad slippage, malicious tokens, compromised prompts, or incorrect network selection.
Use a dedicated low-balance wallet, keep autoApprove empty, and never connect a primary wallet or seed phrase to an AI-controlled tool session.
The reviewed source decodes SOLANA_PRIVATE_KEY into a KeypairWallet and loads the Solana Agent Kit God Mode plugin, so the private key grants real signing authority to the MCP process.
The reviewed installer script prints the entered private-key value during validation, so prefer manual npm configuration or review and patch the script before using it.
RPC providers, token price sources, marketplaces, and Solana network state can be delayed, rate-limited, incomplete, or manipulated.
Privacy notes
Wallet addresses, balances, token holdings, transaction intents, trade targets, domain lookups, NFT metadata, RPC URLs, and prompts can be sent to the MCP client, model, RPC provider, or downstream Solana services.
SOLANA_PRIVATE_KEY is a signing secret and should never be pasted into prompts, public issues, screenshots, shell history, committed MCP config, or installer debug output.
On-chain actions are public and can permanently link wallet addresses, timing, assets, counterparties, and strategy to the configured wallet.
The repository license file is Apache-2.0 while README and package metadata currently mention MIT, so verify current licensing before redistribution or commercial reuse.
Prerequisites
Node.js 16 or newer and npm, pnpm, or yarn.
Solana RPC URL for the intended network.
Dedicated Solana wallet private key with only funds approved for agent experimentation.
Devnet or testnet validation before any mainnet use.
Human review for every transfer, trade, mint, token deployment, or other value-affecting operation.
Solana MCP Server is a Solana Agent Kit based Model Context Protocol server for
Claude and other MCP clients. It initializes a Solana wallet from a private key,
connects to a configured RPC URL, loads Solana Agent Kit actions, and exposes
on-chain tools for wallet, asset, token, NFT, transfer, trading, domain, and
network queries.
The reviewed implementation starts over stdio by default and can expose an SSE
transport when a port is configured. Because the server signs with the configured
wallet private key, treat it as high-risk financial infrastructure rather than a
read-only blockchain data connector.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, npm metadata, package metadata, server entrypoint, installer script,
example client config, registry metadata, and license file for current install
commands, environment variables, wallet behavior, tool surface, transports, and
licensing.
Features
NPM package solana-mcp with a solana-mcp executable.
Solana Agent Kit and MCP adapter integration.
Wallet initialization from SOLANA_PRIVATE_KEY and RPC_URL.
Stdio transport by default, with optional SSE transport when PORT is set.
Tools described upstream for asset lookup, token deployment, token prices,
wallet address, balance, transfers, NFT minting, trades, fund requests, domain
resolution, and TPS checks.
Optional OPENAI_API_KEY environment variable.
Apache-2.0 license file, with MIT currently shown in README and package
metadata.
Installation
Install from npm:
npm install -g solana-mcp
Configure the MCP client manually with a dedicated wallet:
Start on devnet or testnet with a low-balance wallet. Do not use the interactive
installer unless you have reviewed and adjusted its private-key handling.
Use Cases
Check an approved wallet address and balance.
Retrieve Solana asset or token information for research.
Resolve Solana domain names before a manual transaction.
Test token deployment, NFT minting, transfers, or trades on devnet.
Ask Claude to draft a transaction plan that a human reviews before execution.
Monitor Solana TPS or basic network context during development.
Safety and Privacy
Solana MCP Server can sign blockchain transactions with the configured wallet.
Use a dedicated wallet, keep the balance minimal, test on devnet or testnet, and
never grant automatic approval for transfer, trade, token deployment, minting, or
other value-affecting tools. Verify recipient addresses, token identities,
slippage, network, fees, and expected outcomes outside the model conversation.
The reviewed source decodes SOLANA_PRIVATE_KEY and creates a signing wallet
for the MCP process. Anyone who can read the private key or control the MCP
session can potentially move funds. The reviewed installer script also prints
the entered private-key value during validation, so manual configuration is safer
unless the script is reviewed and changed first.
Wallet activity is public on-chain, and prompts can reveal strategy, holdings,
counterparties, token interests, and intended transactions. Protect RPC URLs,
private keys, generated configs, logs, screenshots, shell history, and model
transcripts as sensitive financial data.
Duplicate Check
No Solana MCP Server, sendaifun/solana-mcp, Solana Agent Kit MCP, blockchain
wallet MCP, or dedicated Solana on-chain action MCP entry was found in
content/mcp, content/agents, content/guides, or content/skills. This
entry is scoped to the SendAI Solana MCP server and does not duplicate general
Web3, database, or finance-oriented MCP entries.
Show that Solana MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/solana-mcp-server)
How it compares
Solana MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
Solana Agent Kit MCP server that lets Claude use a configured Solana wallet and RPC endpoint for on-chain actions such as wallet balance checks, asset lookup, token deployment, transfers, NFT minting, token trades, domain resolution, TPS checks, and test-fund requests.
MCP server for connecting Claude to AFFiNE Cloud or self-hosted AFFiNE workspaces, documents, databases, comments, collections, folders, tags, notifications, blobs, access tokens, semantic page composition, templates, edgeless canvas data, and workspace organization workflows over stdio or HTTP.
Official MCP server for agent-device, Callstack's device automation CLI for inspecting, controlling, debugging, recording, and collecting evidence from iOS, Android, TV, macOS, Linux, React Native, Expo, Flutter, and native apps.
✓Solana MCP Server can expose on-chain actions including transfers, token trades, NFT minting, token deployment, and wallet operations through Solana Agent Kit.
Blockchain transactions can be irreversible and can lose funds through wrong recipients, bad slippage, malicious tokens, compromised prompts, or incorrect network selection.
Use a dedicated low-balance wallet, keep autoApprove empty, and never connect a primary wallet or seed phrase to an AI-controlled tool session.
The reviewed source decodes SOLANA_PRIVATE_KEY into a KeypairWallet and loads the Solana Agent Kit God Mode plugin, so the private key grants real signing authority to the MCP process.
The reviewed installer script prints the entered private-key value during validation, so prefer manual npm configuration or review and patch the script before using it.
RPC providers, token price sources, marketplaces, and Solana network state can be delayed, rate-limited, incomplete, or manipulated.
✓The full tool surface can create, update, publish, revoke, move, replace, and delete AFFiNE workspaces, documents, folders, collections, comments, database rows, blobs, surface elements, tags, and access tokens.
Start with AFFINE_TOOL_PROFILE=read_only or disable groups such as destructive, admin, blobs, users, access_tokens, docs.database, or write when the assistant only needs discovery or reading.
HTTP mode exposes MCP endpoints and must be protected with bearer or OAuth authentication, HTTPS, allowed origins, and deployment-level access controls.
AFFiNE Cloud requires API tokens for MCP usage; avoid trying to automate email/password login against Cloud deployments.
Cookie and password-based auth can grant broad account access and should be avoided for unattended or shared deployments.
✓Agent Device MCP exposes structured tools backed by `AgentDeviceClient`; the docs state it does not expose generic shell execution over MCP.
Tools and CLI workflows can open apps, inspect UI, tap, type, scroll, perform gestures, wait, assert state, handle alerts, and close sessions.
Evidence workflows can capture screenshots, recordings, logs, traces, network traffic, performance samples, crash context, React profiles, and replay files.
Mutating commands should run serially against one session, and separate sessions or devices should be used for parallel work.
Prefer dedicated test devices or simulators, and require approval before entering credentials, submitting forms, changing settings, installing apps, sending messages, or touching production accounts.
✓AgentQL MCP exposes one tool, `extract-web-data`, that sends a target URL and natural-language extraction prompt to the AgentQL API.
The tool is intended for public webpages; do not use it to bypass access controls, scrape private pages, evade paywalls, or extract data where automated collection is prohibited.
Web extraction can still trigger target-site rate limits, legal restrictions, robots guidance, or terms-of-service concerns.
The source implementation uses AgentQL's query-data endpoint with fast mode, no screenshot capture, no scroll-to-bottom behavior, and no local browser cookies.
Treat extracted output as untrusted web data that may include errors, stale content, ads, tracking text, or prompt-injection attempts.
Privacy notes
✓Wallet addresses, balances, token holdings, transaction intents, trade targets, domain lookups, NFT metadata, RPC URLs, and prompts can be sent to the MCP client, model, RPC provider, or downstream Solana services.
SOLANA_PRIVATE_KEY is a signing secret and should never be pasted into prompts, public issues, screenshots, shell history, committed MCP config, or installer debug output.
On-chain actions are public and can permanently link wallet addresses, timing, assets, counterparties, and strategy to the configured wallet.
The repository license file is Apache-2.0 while README and package metadata currently mention MIT, so verify current licensing before redistribution or commercial reuse.
✓Workspaces, document titles, document bodies, comments, tags, database schemas, database rows, edgeless canvas data, notifications, user profiles, access-token metadata, blobs, and exported markdown can be sent to the MCP client and model.
API tokens, cookies, passwords, bearer tokens, OAuth config, and saved config files should be treated as secrets and kept out of prompts, logs, screenshots, issues, and committed MCP config.
Generated or modified documents can persist in AFFiNE and may become visible to collaborators depending on workspace permissions and sharing state.
Blob upload, cleanup, export, and publish/revoke workflows can expose files, generated content, or collaboration state beyond the current prompt.
✓Screenshots, recordings, traces, logs, network dumps, replay files, reports, UI snapshots, typed input, and React profiles can contain private UI state, tokens, request data, customer information, or credentials.
macOS, iOS, Android, and TV automation can expose local app state, notifications, device names, package identifiers, app content, system dialogs, and permission prompts.
Network inspection artifacts may include headers, payloads, session identifiers, URLs, and API data; review before sharing or committing.
Interactive CLI runs may check npm for newer package versions unless `AGENT_DEVICE_NO_UPDATE_NOTIFIER=1` is set.
✓Target URLs, extraction prompts, API key-authenticated requests, and extracted structured data are sent to AgentQL's API.
Extracted data can include personal data, copyrighted content, customer information, job postings, prices, social content, or other third-party material.
AGENTQL_API_KEY should stay out of prompts, issues, logs, screenshots, and committed configuration files.
Claude transcripts and downstream reports may retain extracted data, so avoid collecting information that is not approved for the model session.
Prerequisites
Node.js 16 or newer and npm, pnpm, or yarn.
Solana RPC URL for the intended network.
Dedicated Solana wallet private key with only funds approved for agent experimentation.
Devnet or testnet validation before any mainnet use.
Node.js and npm for installing the affine-mcp-server package.
AFFiNE Cloud API token or approved self-hosted AFFiNE credentials.
AFFiNE base URL for the Cloud or self-hosted deployment.
Clear workspace scope and least-privilege tool profile before enabling write, admin, destructive, blob, or access-token tools.
Node.js 22 or newer and `agent-device` installed globally or project-locally.
Xcode tooling for iOS, tvOS, or macOS targets, or Android SDK and ADB for Android targets.
Device, simulator, emulator, TV, macOS, or Linux desktop target that the agent is allowed to automate.
Required local permissions such as Android device trust, iOS Developer Mode, macOS Accessibility, and Screen Recording where applicable.
Node.js and npx available to the MCP client runtime.
AgentQL API key from the AgentQL developer portal.
Approved list of public webpages or domains Claude may query.
Review of target site terms, robots guidance, rate limits, and data-use rules before extraction.
Install
npm install -g solana-mcp
npm i -g affine-mcp-server
claude mcp add --transport stdio --scope user agent-device -- agent-device mcp