helius
01MCP server Claude CodeCodexCursor +2
One of 7 in .mcp.json
Official Helius MCP Server - Complete Solana blockchain data access for AI assistants. Runs locally from the helius-mcp npm package. Needs 1 environment variable to run.
Claude Code / Codex / AI configs for the expert Solana builder. CLAUDE.md, agents, commands, hooks, rules, skills and settings across Web, Anchor, Pinnochio, Unity, Mobile, security and more.
MCP server Claude CodeCodexCursor +2
One of 7 in .mcp.json
Official Helius MCP Server - Complete Solana blockchain data access for AI assistants. Runs locally from the helius-mcp npm package. Needs 1 environment variable to run.
MCP server Claude CodeCodexCursor +2
One of 7 in .mcp.json
MCP server "solana-dev", hosted remotely at mcp.solana.com, as configured in solanabr/solana-ai-kit.
MCP server Claude CodeCodexCursor +2
One of 7 in .mcp.json
Gives the agent up-to-date documentation and code examples for libraries and frameworks, fetched on demand so answers are not stuck at the model's training cutoff. Runs locally from the @upstash/context7-mcp npm package.
MCP server Claude CodeCodexCursor +2
One of 7 in .mcp.json
Lets the agent drive a real browser: open pages, click, type, take screenshots and read the accessibility tree, using Playwright. Runs locally from the @playwright/mcp npm package.
MCP server Claude CodeCodexCursor +2
One of 7 in .mcp.json
MCP plugin that saves 98% of your context window. Works with Claude Code, Gemini CLI, VS Code Copilot, OpenCode, and Codex CLI. Sandboxed code execution, FTS5 knowledge base, and intent-driven search. Runs locally from the context-mode npm package.
MCP server Claude CodeCodexCursor +2
One of 7 in .mcp.json
MCP server "memsearch" as configured in solanabr/solana-ai-kit. Runs locally from the memsearch-mcp npm package.
MCP server Claude CodeCodexCursor +2
One of 7 in .mcp.json
MCP server "surfpool" as configured in solanabr/solana-ai-kit. Launched with surfpool mcp.
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: