list_sections
Lists indexed Solana documentation sources with section tags and use cases.
Remote MCP server
Current Solana docs and Rust checks for coding agents
Connect your MCP client to live Solana documentation retrieval, semantic search, and the Rust autofixer for Anchor and Pinocchio program checks.
Setup
Use the direct HTTP endpoint when your client supports it. No API key is required.
1
Add the server
Run this in a terminal where the Codex CLI is installed:
codex mcp add solana-mcp --url https://mcp.solana.com/mcp
2
Verify the connection
List configured MCP servers and confirm solana-mcp appears:
codex mcp list
3
Add project instructions
Put the agent instructions below in AGENTS.md when you want Codex to route Solana
work through this MCP server consistently.
1
Add the server
Claude Code supports remote HTTP MCP servers directly:
claude mcp add --transport http solana-mcp https://mcp.solana.com/mcp
2
Verify the connection
Open Claude Code and run /mcp. The server should list these tools:
list_sections
get_documentation
Solana_Documentation_Search
Solana_Expert__Ask_For_Help
rust_autofixer
1
Configure MCP
Add this to ~/.cursor/mcp.json for global use, or .cursor/mcp.json inside
one project:
{
"mcpServers": {
"solanaMcp": {
"url": "https://mcp.solana.com/mcp"
}
}
}
2
Verify in Agent chat
Open Cursor Agent, check the available MCP tools, and ask it to call list_sections for
Solana documentation discovery.
1
Configure MCP
Add this to ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"solanaMcp": {
"serverUrl": "https://mcp.solana.com/mcp"
}
}
}
2
Verify in Cascade
Open Cascade MCP settings, confirm solanaMcp is connected, and enable the Solana tools
you want available.
1
Open user configuration
In the Command Palette, run MCP: Open User Configuration, then add:
{
"servers": {
"solanaMcp": {
"type": "http",
"url": "https://mcp.solana.com/mcp"
}
}
}
2
Start and verify
Run MCP: List Servers, start solanaMcp, then use Copilot Agent mode to ask
a Solana question that requires current docs.
Tools
The live server currently exposes these exact MCP tool names.
get_documentation
Fetches canonical docs by source id, section id, or an array of ids.
Solana_Documentation_Search
Runs semantic search over the Solana docs corpus for narrow questions.
Solana_Expert__Ask_For_Help
Answers Solana how-to and debugging questions with retrieved docs context.
rust_autofixer
Analyzes Solana program Rust for Anchor and Pinocchio security antipatterns and returns structured issues plus fix suggestions.
Agent Instructions
Add the matching file for your agent. Cursor project rules use .cursor/rules/*.mdc;
.cursorrules is legacy.
Add this to
AGENTS.md. The key rule is the Rust autofixer loop: call it before returning
Solana program Rust, apply fixes, and call it again until another pass is not required.
For Solana-related work, prefer the Solana Developer MCP tools over model memory.
Use `list_sections` first for non-trivial Solana questions so you can find the
right documentation source ids and section ids.
Use `get_documentation` when you need canonical docs for a specific source,
framework, library, or ecosystem area. Use `Solana_Documentation_Search` or
`Solana_Expert__Ask_For_Help` for narrow how-to questions, errors, or API usage.
Whenever you write or modify Solana program Rust, call `rust_autofixer` before
returning code. It accepts `code`, optional `filename`, and optional `framework`
(`auto`, `anchor`, or `pinocchio`). Apply the suggested fixes, then call
`rust_autofixer` again. Repeat until `require_another_tool_call_after_fixing`
is false.
Add this to
CLAUDE.md for Claude Code projects that prefer Claude-native project memory.
For Solana-related work, prefer the Solana Developer MCP tools over model memory.
Use `list_sections` first for non-trivial Solana questions so you can find the
right documentation source ids and section ids.
Use `get_documentation` when you need canonical docs for a specific source,
framework, library, or ecosystem area. Use `Solana_Documentation_Search` or
`Solana_Expert__Ask_For_Help` for narrow how-to questions, errors, or API usage.
Whenever you write or modify Solana program Rust, call `rust_autofixer` before
returning code. It accepts `code`, optional `filename`, and optional `framework`
(`auto`, `anchor`, or `pinocchio`). Apply the suggested fixes, then call
`rust_autofixer` again. Repeat until `require_another_tool_call_after_fixing`
is false.
Create
.cursor/rules/solana-mcp.mdc. Cursor project rules are version-controlled MDC files
under .cursor/rules.
---
description: Use Solana Developer MCP for current Solana docs and Rust program checks.
globs:
alwaysApply: true
---
For Solana-related work, prefer the Solana Developer MCP tools over model memory.
Use `list_sections` first for non-trivial Solana questions so you can find the
right documentation source ids and section ids.
Use `get_documentation` when you need canonical docs for a specific source,
framework, library, or ecosystem area. Use `Solana_Documentation_Search` or
`Solana_Expert__Ask_For_Help` for narrow how-to questions, errors, or API usage.
Whenever you write or modify Solana program Rust, call `rust_autofixer` before
returning code. It accepts `code`, optional `filename`, and optional `framework`
(`auto`, `anchor`, or `pinocchio`). Apply the suggested fixes, then call
`rust_autofixer` again. Repeat until `require_another_tool_call_after_fixing`
is false.Example Requests
Canonical docs
Use list_sections, then fetch the current Anchor docs for account constraints.
Semantic search
Search the docs for Token-2022 transfer hook account requirements.
Solana debugging
Ask for help with a failed transaction log and include the program error output.
Rust review
Run rust_autofixer on this Pinocchio instruction before returning the patch.