solblade
Provides tools for managing Solana wallets, including balance queries, token transfers, swapping via Jupiter, and rent reclaim, all with granular permission scoping and audit logging.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@solbladecheck my wallet balance"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Solblade is a Solana wallet that runs in your terminal and exposes a Model Context Protocol (MCP) server so AI agents can manage your wallets — with granular, per-wallet permission scoping you control.
No browser extensions. No custodial APIs. Just a CLI with an encrypted local keystore and an MCP interface that gives AI exactly the access you choose: read-only portfolio views, spend-limited transfers, or full autonomy within guardrails.
Why Solblade
AI agents need wallet access to be useful on-chain, but giving an AI your private key is insane — and read-only access is useless for real work.
Solblade sits between your keys and the AI. You set per-wallet access levels, spend limits, rate limits, and destination allowlists. The AI operates within those bounds. Every action is logged in a tamper-evident audit chain. Revoke access with one command.
CLI-native MCP server — no web app, no browser extension, just
solblade mcp servePer-wallet AI permissions — each wallet has its own access level and spend limits
Confirmation gates — require human approval for transfers, or auto-execute under limits
Rent reclaim engine — AI scans for dead token accounts and reclaims locked SOL in bulk
Tamper-evident audit log — SHA-256 chained event log of every AI action
Encrypted local keystore — AES-256-GCM with PBKDF2 key derivation, keys never leave your machine
Related MCP server: waiaas
Install
# requires Bun (https://bun.sh)
bun install -g solblade
# initialize keystore, first wallet, and RPC config
solblade initConnect to your AI
Solblade works with any MCP-compatible client. Pick your editor below.
Tip: Replace
"*"with specific tool groups to restrict access —"read"for read-only,"read,scan,cleanup"for read + rent reclaim.
claude mcp add solblade -- bunx solblade mcp serve --allow "*"That's it. One command.
Add to your config file:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"solblade": {
"command": "bunx",
"args": ["solblade", "mcp", "serve", "--allow", "*"]
}
}
}Restart Claude Desktop after saving.
Add to .cursor/mcp.json in your project root, or go to Settings > MCP Servers > Add Server:
{
"mcpServers": {
"solblade": {
"command": "bunx",
"args": ["solblade", "mcp", "serve", "--allow", "*"]
}
}
}Add to .vscode/mcp.json in your workspace:
{
"servers": {
"solblade": {
"command": "bunx",
"args": ["solblade", "mcp", "serve", "--allow", "*"]
}
}
}Or open the Command Palette (Ctrl+Shift+P) and run MCP: Add Server.
Add to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"solblade": {
"command": "bunx",
"args": ["solblade", "mcp", "serve", "--allow", "*"]
}
}
}Add to Zed settings (settings.json):
{
"context_servers": {
"solblade": {
"command": {
"path": "bunx",
"args": ["solblade", "mcp", "serve", "--allow", "*"]
}
}
}
}Solblade speaks MCP over stdio. Point any compatible client at:
bunx solblade mcp serve --allow "*"MCP Tools
Once connected, your AI agent has access to these tool groups:
Group | Tools | What it does |
balance |
| SOL and token balance queries |
wallets |
| Wallet metadata and AI access levels |
price |
| USD prices via Jupiter/Birdeye |
swap |
| Jupiter DEX quotes and execution |
transfer |
| SOL and SPL token transfers |
scan |
| Rent reclaim scanning, portfolio valuation |
cleanup |
| Close dead token accounts, reclaim rent |
history |
| On-chain transaction and account data |
log |
| AI action history and spend tracking |
admin |
| Session and permission introspection |
Permission Scoping
Every wallet has independent AI access controls:
# Read-only access
solblade wallet ai-access treasury --level read
# Transfer access with spend limits (SOL)
solblade wallet ai-access trading --level transfer --per-tx 1 --per-session 5
# Require human confirmation for each transfer
solblade wallet set-confirm trading --on
# Restrict destinations to trusted addresses
solblade wallet set-allowlist trading --add <trusted-pubkey>Confirmation Flow
When require_confirmation is enabled, write tools return a pending action instead of executing:
AI: "I'd like to send 0.5 SOL from 'trading' to 9xQe...4kPm ($75.00).
This is within your 1 SOL per-transaction limit. Approve?"
You: "Yes"
AI: "Done — tx confirmed: 5Uj8... (explorer link)"Security Model
┌─ Tool Allowlist ────────── which tools are exposed at all
├─ Wallet AI Access ──────── none / read / transfer per wallet
├─ Session Gate ──────────── password-derived key, configurable TTL
├─ Spend Limits ──────────── per-tx and per-session caps in SOL
├─ Rate Limits ───────────── max transactions per minute
├─ Destination Allowlist ─── restrict where funds can go
├─ Confirmation Gate ─────── human approval before execution
├─ Transaction Simulation ── Solana RPC simulation before signing
└─ Tamper-Evident Audit ──── SHA-256 chained event logNever exposed via MCP: private key export, seed phrases, keystore files, password/session material, permission escalation, wallet creation/deletion, RPC config changes.
CLI Commands
Wallet Management
solblade create [--label name] [--group name] # Create new wallet
solblade import --key <base58> # Import existing key
solblade list [--group name] [--tag name] # List wallets
solblade label <wallet> --set <name> # Rename wallet
solblade default <wallet> # Set default wallet
solblade remove <wallet> # Archive walletTransactions
solblade balance [wallet] # SOL balance
solblade balance --all # All wallet balances
solblade balance --tokens [wallet] # SPL token balances
solblade send <amount> SOL --to <address> # Send SOL
solblade send <amount> <token> --to <address> # Send SPL token
solblade swap <amount> <token> --to <token> # Jupiter swapSession & Security
solblade unlock # Start session
solblade lock # End session
solblade unlock --status # Check sessionMCP Server
solblade mcp serve [--allow <tools>] # Start MCP stdio serverAudit
solblade log [--limit N] # View audit logArchitecture
Component | Stack |
Runtime | Bun with native SQLite |
Encryption | AES-256-GCM, PBKDF2-SHA256 (600k iterations) |
Database | SQLite with WAL mode |
MCP |
|
Solana |
|
DEX | Jupiter V6 API |
Keystore |
|
See docs/MCP_ARCHITECTURE.md for the full MCP server design.
Development
git clone https://github.com/nullxnothing/solblade.git
cd solblade
bun install
bun run devLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/nullxnothing/solblade'
If you have feedback or need assistance with the MCP directory API, please join our Discord server