Solana Debug MCP
Provides tools for inspecting and debugging Solana transactions, accounts, Anchor IDLs, Anchor errors, and Program Derived Addresses from MCP-compatible clients.
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., "@Solana Debug MCPsimulate transaction and show logs"
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.
Solana Debug MCP
Solana Debug MCP is a Model Context Protocol server for inspecting and debugging Solana transactions, accounts, Anchor IDLs, Anchor errors, and Program Derived Addresses from MCP-compatible clients.
This project is ready for local production-style MCP use over stdio. It can simulate base64 or base58 serialized Solana transactions, inspect account metadata, inspect legacy and versioned transaction instructions, fetch on-chain Anchor IDLs, decode supported Anchor account and instruction fields, look up built-in and IDL-provided Anchor errors, and derive PDAs.
Features
simulate_transaction: Simulate a serialized Solana transaction through an RPC endpoint and summarize logs.decode_account: Fetch account metadata and decode supported Anchor account fields when an IDL is supplied or fetchable.decode_instruction: Inspect legacy/versioned instructions and decode supported Anchor instruction args when an IDL is supplied or fetchable.anchor_error_lookup: Look up common Anchor framework errors and custom IDL errors.pda_verify: Derive a PDA from seeds and check whether the account exists on chain.
Related MCP server: MCP Inspector as MCP Server
Current Limitations
Hosted HTTP/SaaS transport is not implemented; current production target is local stdio MCP.
IDL enum decoding and some unusual Anchor IDL shapes are not implemented yet.
pda_verifysupports typed seeds. Plain string seeds are still accepted as UTF-8 for backward compatibility.Error analysis is deterministic log pattern matching, not AI-generated analysis.
Requirements
Node.js 20 or newer
pnpm 10 or newer
A Solana RPC endpoint
Optional Helius API key for mainnet RPC
Installation
pnpm install
pnpm run buildFor local development:
pnpm run devFor production-style local execution:
pnpm startConfiguration
Create a .env file from the example:
cp .env.example .envSupported environment variables:
# Optional. If set, the server uses Helius mainnet RPC by default.
HELIUS_API_KEY=your-helius-api-key
# Optional fallback RPC URL when HELIUS_API_KEY is not set.
SOLANA_RPC_URL=https://api.mainnet-beta.solana.com
# Documented for future cluster-aware IDL fetching. Currently unused.
SOLANA_CLUSTER=mainnet-betaRPC precedence in the current implementation:
Tool-level
rpc_url, where supportedHELIUS_API_KEY, if setSOLANA_RPC_URLhttps://api.mainnet-beta.solana.com
Claude Desktop Setup
Build the project first:
pnpm run buildThen add the server to your Claude Desktop configuration.
macOS path:
~/Library/Application Support/Claude/claude_desktop_config.jsonExample configuration:
{
"mcpServers": {
"solana-debug": {
"command": "node",
"args": ["/absolute/path/to/solanaDebug/dist/index.js"],
"env": {
"HELIUS_API_KEY": "your-helius-api-key",
"SOLANA_RPC_URL": "https://api.mainnet-beta.solana.com"
}
}
}
}Restart Claude Desktop after editing the config.
MCP Tools
simulate_transaction
Simulates a serialized Solana transaction and returns simulation status, logs, units consumed, and pattern-based analysis.
Input:
{
"transaction": "base64-or-base58-serialized-transaction",
"rpc_url": "https://api.mainnet-beta.solana.com"
}Fields:
transaction: Required string. Accepts base64 or base58 serialized legacy or versioned transaction bytes.rpc_url: Optional string. Overrides environment RPC defaults for this call.
Output shape:
{
"ok": true,
"data": {
"success": false,
"error_code": "custom program error...",
"error_message": "Transaction simulation failed",
"transaction_type": "legacy",
"encoding": "base64",
"logs": [],
"analysis": "Pattern-based explanation"
}
}Implementation:
Registered in
src/index.ts.Handler is
simulateTransactioninsrc/tools/simulate.ts.RPC call is made by
RPCService.simulateTransactioninsrc/services/rpc.ts.Log summary is generated by
generateAnalysisinsrc/services/analyzer.ts.
decode_account
Fetches basic account information from RPC.
Input:
{
"address": "account-public-key",
"program_id": "expected-owner-program-id"
}Fields:
address: Required account public key.program_id: Required expected owner program ID. The response reports whether it matches the fetched account owner.
Output shape:
{
"ok": true,
"data": {
"address": "account-public-key",
"program_id": "expected-owner-program-id",
"owner_matches_program_id": true,
"account_type": "unknown",
"data": {
"lamports": 1000000,
"sol_balance": 0.001,
"owner": "actual-owner-program-id",
"executable": false,
"data_length": 128,
"note": "Full IDL decoding not yet implemented in MVP. Raw account data available."
}
}
}Implementation:
Registered in
src/index.ts.Handler is
decodeAccountinsrc/tools/decode.ts.Account fetching is handled by
RPCService.getAccountInfo.src/services/idl.tscontains placeholder IDL-service code but is not wired into this tool yet.
decode_instruction
Inspects one or all instructions in a serialized legacy transaction.
Input:
{
"transaction": "base64-or-base58-serialized-transaction",
"instruction_index": 0
}Fields:
transaction: Required string. Accepts base64 or base58 serialized legacy or versioned transaction bytes.instruction_index: Optional number. When omitted, all instructions are returned.
Output shape for one instruction:
{
"ok": true,
"data": {
"transaction_type": "legacy",
"encoding": "base64",
"instruction": {
"index": 0,
"program_id": "program-public-key",
"accounts": [
{
"pubkey": "account-public-key",
"isSigner": true,
"isWritable": true
}
],
"data": "base64-instruction-data",
"data_length": 16
}
}
}Implementation:
Registered in
src/index.ts.Handler is
decodeInstructioninsrc/tools/decode.ts.Uses the shared transaction parser in
src/services/transaction.ts.
anchor_error_lookup
Looks up a common Anchor framework error by decimal or hexadecimal code.
Input:
{
"error_code": "0x1771",
"program_id": "optional-program-id"
}or:
{
"error_code": "6001"
}Fields:
error_code: Required string. Accepts decimal,0xhex, or0Xhex.program_id: Optional string. Used to fetch an on-chain Anchor IDL for custom error lookup whenidlis not supplied.
Output shape:
{
"ok": true,
"data": {
"error_code": "0x1771",
"error_code_decimal": 6001,
"error_name": "Unknown",
"description": "Error code not found in Anchor error database",
"common_causes": ["Custom program error", "Unknown error type"],
"suggested_fixes": [
"Check program source code for custom error definitions",
"Review transaction logs for more context",
"Verify error code is from Anchor framework"
],
"program_id": "unknown"
}
}Implementation:
Registered in
src/index.ts.Handler and built-in error table are in
src/tools/errors.ts.
pda_verify
Derives a Program Derived Address and checks whether the derived account exists.
Input:
{
"program_id": "program-public-key",
"seeds": [
{ "type": "utf8", "value": "seed" },
{ "type": "pubkey", "value": "public-key-seed" }
]
}Fields:
program_id: Required program public key.seeds: Required array of typed seeds. Supported types areutf8,pubkey,hex, andbase64. Plain strings are accepted as UTF-8 seeds for backward compatibility.
Output shape:
{
"ok": true,
"data": {
"address": "derived-pda",
"bump": 255,
"exists": true,
"program_id": "program-public-key",
"seeds": [{ "type": "utf8", "value": "seed" }],
"account_data": {
"lamports": 1000000,
"owner": "owner-public-key",
"data_length": 128
}
}
}Implementation:
Registered in
src/index.ts.Handler is
pdaVerifyinsrc/tools/pda.ts.PDA derivation uses
PublicKey.findProgramAddressSync.Account lookup uses
RPCService.getAccountInfo.
Project Structure
src/
├── index.ts MCP server entry point and tool registration
├── tools/
│ ├── simulate.ts simulate_transaction handler
│ ├── decode.ts decode_account and decode_instruction handlers
│ ├── errors.ts anchor_error_lookup handler and error table
│ └── pda.ts pda_verify handler
├── services/
│ ├── rpc.ts Solana RPC wrapper
│ ├── transaction.ts Shared transaction parser and instruction views
│ ├── idl.ts Placeholder IDL fetching and decoding service
│ └── analyzer.ts Transaction log pattern matching
└── utils/
└── types.ts Shared result helpers and interfacesDevelopment Workflow
Install dependencies:
pnpm installRun the server from TypeScript:
pnpm run devTypecheck and build:
pnpm run typecheck
pnpm run buildRun tests:
pnpm testRun the opt-in live RPC smoke test:
pnpm run test:liveThis uses your configured .env or process environment and reaches the configured Solana RPC provider.
Run the built server:
pnpm startClean generated output:
pnpm run cleanImplementation Notes
Adding a Tool
Add the handler under
src/tools/.Define its Zod schema near the handler.
Register it with
server.tool(...)insrc/index.ts.Return MCP-compatible text content with
createResultorcreateErrorResult.Add tests for valid input, invalid input, and RPC failure behavior.
Returning Results
Tools return:
{
content: [{ type: "text", text: "..." }]
}JSON payloads are currently serialized into the text field. Success responses use { "ok": true, "data": ... }; failures use { "ok": false, "error": "..." }.
RPC Access
RPCService wraps @solana/web3.js Connection creation and common calls. New RPC-backed features should be added there when they are reusable by multiple tools.
IDL Decoding
src/services/idl.ts supports Anchor IDL fetching and decoding:
On-chain Anchor IDL address derivation.
Inflating and parsing on-chain Anchor IDL account data.
Account and instruction discriminator matching.
Primitive fields:
bool,u8,i8,u16,i16,u32,i32,u64,i64,string,bytes,publicKey, andpubkey.Complex fields:
option,vec, fixed arrays, and nested defined structs.Custom IDL errors through
anchor_error_lookup.
IDL support should still add enum decoding and broader fixture coverage for unusual Anchor IDL shapes.
Troubleshooting
Unable to parse transaction
The transaction field must be a serialized Solana transaction encoded as base64 or base58. JSON transaction objects and signatures are not accepted.
RPC timeouts or rate limits
Set HELIUS_API_KEY or SOLANA_RPC_URL in .env. The RPC wrapper has retry and timeout handling, but persistent rate limits require a better RPC provider or a dedicated key.
.env is not loading
The server loads .env from the current working directory. Start the server from the project root, or pass environment variables through your MCP client config.
Live RPC smoke test is skipped
This is expected. Run it explicitly:
pnpm run test:liveContributing
Add or update tests first.
Run
pnpm run typecheck.Run
pnpm test.Keep MCP tool outputs structured as
{ "ok": true, "data": ... }or{ "ok": false, "error": "..." }.Keep network tests opt-in unless they use mocked RPC.
Testing Status
The project has a focused Node test suite for transaction parsing, instruction inspection, Anchor error lookup, and structured errors. More unit and integration coverage is still needed before production use. See PRODUCTION_PLAN.md for the recommended production-readiness checklist.
Production Status
This project is production-ready for local stdio MCP usage. Hosted HTTP/SaaS deployment is not implemented.
Security
See SECURITY.md. Do not commit .env files or private RPC keys. Serialized transactions and account addresses may be sent to the configured RPC provider.
Release
See RELEASE.md for the package release checklist.
Usage Scenarios
See USER_STORIES.md for concrete examples of how Solana developers can use this MCP server.
Testing It Yourself
See TESTING_GUIDE.md for a hands-on path after cloning the repo.
License
MIT
Author
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/biccsdev/solana_debug_mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server