convez.ai
MCP ServerIntegração & APIsIntermediário
CHARLES-PONZI

Solana MCP para Codex

CHARLES-PONZI/solana-mcp-for-codex

Integração padronizada de ferramentas Solana ao Codex via MCP

Ver no GitHub
BomPluginScore · de 0 a 100

Snippets de configuração prontos para Codex que facilitam a integração de servidores Solana MCP com o OpenAI Codex. Centraliza detalhes de setup, variáveis de ambiente e comandos de instalação para diferentes projetos Solana, eliminando reconfiguração repetida.

Instalação

$npx convez-ai CHARLES-PONZI/solana-mcp-for-codex

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
1
Forks
0
Acompanhando
0
Saúde
85%
Último commit
há 5 meses
Versão
v0.3.1
Issues abertas
0
Contribuidores
1

Casos de uso

  • Conectar servidores Solana ao OpenAI Codex sem reconfiguração manual
  • Acessar ferramentas de leitura e escrita Solana (wallets, swaps, transfers) via AI
  • Verificar e validar configurações MCP antes de ativar em produção

Veredito

Repositório técnico e bem mantido que reduz atrito na integração Solana-Codex. Oferece segurança por camadas (verificação de pacotes, testes de fumaça) e documenta corretamente riscos de operações com wallet. Útil para devs que querem usar IA para interagir com Solana programaticamente.

README

A tradução para o português deste README ainda está na fila.

Solana MCP for Codex

validate

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.

servers.json is the source of truth for the README server table and the commented config.toml snippets. Run python scripts/render_registry.py --write after editing registry metadata.

Quickstart

For the safest default install, add the repo marketplace and install the Codex plugin:

codex plugin marketplace add CHARLES-PONZI/solana-mcp-for-codex

Then open /plugins in Codex and install Solana MCP for Codex. The plugin includes only the hosted Solana Developer MCP docs endpoint. Wallet-capable servers remain opt-in snippets so plugin install does not silently enable signing, swapping, trading, or transfer tools.

For manual setup, 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:

python scripts/validate_repo.py
python scripts/render_registry.py --check
python scripts/check_freshness.py
bash scripts/verify.sh
node scripts/mcp-smoke.mjs

On Windows without Git Bash or WSL, run:

python scripts\validate_repo.py
python scripts\render_registry.py --check
python scripts\check_freshness.py
powershell -NoProfile -ExecutionPolicy Bypass -File scripts/verify.ps1
node scripts\mcp-smoke.mjs

The verifier checks public package metadata, upstream freshness, repository metadata, plugin packaging, registry-derived docs, and the hosted Solana MCP endpoint. It does not prove that wallet-affecting tools are safe.

Optional wallet-capable stdio smoke tests are gated behind RUN_WALLET_MCP_SMOKE=1 and require disposable test wallet environment variables. Do not run them with production wallets.

Servers

ServerVerification levelTransportRiskPage
sendaifun/solana-mcp✅ package verifiedCodex stdiowallet writeservers/sendaifun-solana-mcp.md
solana-foundation/solana-mcp-official✅ MCP smoke + read-only tool verifiedStreamable HTTPdocs-onlyservers/solana-foundation-solana-mcp-official.md
openSVM/solana-mcp-server⚠️ unverified — needs manual source-build testCodex stdiochain data, unverifiedservers/openSVM-solana-mcp-server.md
letsbonk-ai/bonk-mcp✅ package and launch command verifiedCodex stdiowallet write / swap / tradeservers/letsbonk-ai-bonk-mcp.md
FrankGenGo/solana-web3js-mcp-server⚠️ unverified — needs manual source-build testCodex stdiowallet write / transactions, unverifiedservers/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.

✅ MCP smoke verified means an MCP endpoint completed initialize, notifications/initialized, and tools/list.

✅ MCP smoke + read-only tool verified means an MCP endpoint completed the smoke check plus one safe read-only tool call.

✅ 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.

See UPSTREAM-PRS.md for which Solana MCP projects are ready for a docs PR and which still need runtime proof before opening one.

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 servers.json, render the generated files, and extend the relevant 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.

Ver o original no GitHub

Bom para

Relacionados