Solana MCP for Codex

Codex-ready configuration snippets for Solana Model Context Protocol servers.

This repo collects checked codex mcp add commands, config.toml snippets, runtime notes, and upstream PR text for Solana MCP projects. The goal is to make Solana tooling easy to connect to OpenAI Codex without asking every project maintainer to rediscover the same config details.

Why this exists

Solana MCP servers are spread across npm, PyPI, GitHub source builds, and remote HTTP endpoints. Codex can use both stdio and Streamable HTTP MCP servers, but each project exposes different commands, environment variables, and setup expectations.

This repo keeps those details in one place and separates package or endpoint verification from full MCP runtime testing.

Quickstart

Pick one server from the table below and either run the codex mcp add command from its server page or copy the matching block from config.toml into your Codex config.

Codex stores MCP configuration in ~/.codex/config.toml by default. You can also use .codex/config.toml inside a trusted project for project-scoped MCP configuration. The Codex CLI and IDE extension share this config.

Official Codex MCP docs: https://developers.openai.com/codex/mcp

Run the verifier:

bash scripts/verify.sh

On Windows without Git Bash or WSL, run:

powershell -NoProfile -ExecutionPolicy Bypass -File scripts/verify.ps1

The verifier checks public package metadata and the hosted Solana MCP endpoint. It does not prove that wallet-affecting tools are safe.

Servers

| Server | Verification level | Transport | Risk | Page | | --- | --- | --- | --- | --- | | sendaifun/solana-mcp | ✅ package verified | Codex stdio | wallet write | servers/sendaifun-solana-mcp.md | | solana-foundation/solana-mcp-official | ✅ MCP initialize verified | Streamable HTTP | docs-only | servers/solana-foundation-solana-mcp-official.md | | openSVM/solana-mcp-server | ⚠️ unverified — needs manual source-build test | Codex stdio | chain data, unverified | servers/openSVM-solana-mcp-server.md | | letsbonk-ai/bonk-mcp | ✅ package and launch command verified | Codex stdio | wallet write / swap / trade | servers/letsbonk-ai-bonk-mcp.md | | FrankGenGo/solana-web3js-mcp-server | ⚠️ unverified — needs manual source-build test | Codex stdio | wallet write / transactions, unverified | servers/FrankGenGo-solana-web3js-mcp-server.md |

Verification policy

✅ package verified means public package metadata resolved and matched the expected upstream project. It does not prove MCP initialization or tool behavior.

✅ MCP initialize verified means a hosted MCP endpoint responded to an MCP initialize request.

✅ package and launch command verified means package metadata resolved and the documented launch command returned help or startup output. It still does not prove safe tool execution.

⚠️ unverified — needs manual test means the repository exists and the config is based on source files, but this environment could not prove a runnable package or build. Do not open upstream PRs for unverified snippets until a maintainer or local tester confirms they run.

See VERIFICATION.md for evidence, dates, and next tests.

Safe testing

• Use devnet and disposable wallets first.
• Keep wallet/API secrets in environment variables; do not paste live keys into committed TOML, shell history, issues, or PRs.
• Keep default_tools_approval_mode = "prompt" for wallet-capable servers.
• Treat any server marked unverified as a draft config until initialize, notifications/initialized, tools/list, and at least one safe tool call are tested.
• Remote HTTP MCP servers should authenticate sensitive operations and follow MCP transport security guidance.

Tier 2 candidates are intentionally deferred until all Tier 1 servers are verified:

• dcSpark/mcp-server-helius
• FarseenSh/GOATsolana-mcp
• Grandbusta/solana-mcp
• tony-42069/solana-mcp
• caiovicentino/Solana-MCP

Contributing

See CONTRIBUTING.md. At minimum, add one server page under servers/, update the table above, add or update a block in config.toml, and extend both verifier scripts.

Disclaimer

These snippets are third-party MCP configuration examples, not endorsements. Wallet-capable MCP servers can expose tools that trade, swap, or send assets. Review the server source, use least-privilege keys, prefer devnet when testing, and keep Codex tool approvals enabled for write actions.