Solana Foundation Rebuilds Its Developer Docs With CI-Tested Code, Ecosystem Bot Scanning, and an MCP Server

The Solana Foundation's developer documentation is in the middle of a multi-week overhaul. On July 30, Cat McGee, a Developer Relations Engineer at the Foundation, published a thread on X laying out five concrete improvements live or underway at solana.com/docs. The announcement closed with a call for community feedback and opened with a direct admission: the docs need a lot of improvements.

That framing sets the tone. The Foundation is tallying what it fixed, what is still in progress, and asking builders directly what else needs attention.

CI Testing Closes the Stale Code Problem

The most structurally significant change is how Solana SOL$93.25+1.6% now handles code examples in its documentation.

Previously, code snippets lived inline inside markdown files and had no automated test coverage. Developers who copied examples from tutorials routinely hit compilation errors, because the code had drifted from changes to underlying libraries. The fix eliminates the root cause rather than patching individual examples.

Sample code is now stored in a dedicated packages/docs-examples/ directory inside the developer-content monorepo and is run through CI on every commit. At build time, McGee's published npm package, @devrelkit/remark-include-code, pulls the tested code into the markdown files rendered on the live site. The snippets visitors see on solana.com/docs are the same code CI has already confirmed compiles and runs.

The consequence: a broken code tutorial cannot be shipped, because a failing CI build blocks the docs update before it goes out.

Automated Bots Scan Ecosystem Repos for Outdated Solana Documentation

The quality enforcement extends beyond the Foundation's own repositories. Automated bots now scan third-party ecosystem repos and file GitHub issues when their documentation references outdated Solana APIs, functions, or patterns.

Much of the documentation Solana developers actually consult lives outside solana.com: in Anchor's docs, in library readmes, in RPC provider developer guides. When those sources drift out of sync with protocol changes, developers encounter errors that the Foundation's own docs cannot help them resolve. The bot-scanning approach extends the Foundation's quality ownership to wherever developers are actually reading.

A Developer MCP for Cursor and Windsurf, Plus the Solana Skills Library

Two additions target developers who write Solana code inside AI coding assistants.

The Solana Developer MCP makes official documentation available directly to Cursor and Windsurf via the Model Context Protocol. The server ingests four sources: official Solana docs, the Anchor Framework documentation, Solana Program Examples from GitHub, and Solana Stack Exchange. It exposes semantic documentation search, canonical spec retrieval, and a Solana program autofixer covering Anchor and Pinocchio Rust checks. Developers who configure it get answers grounded in current official sources rather than the training data their assistant was last updated with.

The Solana Skills library takes a complementary approach. Skills are pre-built instruction sets installable into coding agents with a single command. The Foundation's official skill installs via npx skills add https://github.com/solana-foundation/solana-dev-skill, and the catalog lists more than 30 community-contributed skills covering protocol integrations including Jupiter JUP$0.203+3.2%, Raydium RAY$0.731+1.4%, Magic Block, and Metaplex MPLX$0.029+0.9%, with a disclaimer that community skills are not Foundation-endorsed.

Restructured Docs, Dark Mode, and a Live Devnet Demo

The docs homepage at solana.com/docs now presents three distinct paths: Quickstart at /docs/intro/quick-start, Coding with Agents at /docs/intro/coding-with-agents, and Core Concepts at /docs/core. The structure is designed around what a new developer is trying to do rather than the organizational hierarchy of the docs themselves.

Dark mode is live, rendered in the Foundation's purple color scheme.

The homepage also features an interactive 2048 game where each tile move executes a real transaction on devnet using a pre-funded wallet provided automatically. For a developer who has never shipped a Solana transaction, it delivers a working demonstration in under thirty seconds with no setup required.

Community Feedback: Central Hub, AI Navigation, and a Rust-Book Rewrite

The announcement thread surfaced specific developer requests. Multiple replies asked for a central hub: one location that consolidates all Solana developer documentation rather than spreading it across solana.com, ecosystem library docs, and community resources. McGee acknowledged the request.

AI and RAG-first navigation, designed to orient the docs around how AI coding assistants retrieve information rather than how human readers browse, is described as in the works. Several developers asked for TPS benchmarks in the docs. A full Rust-Book-style rewrite of the documentation structure is under active consideration.

The overhaul does not have a stated completion date. The multi-week framing suggests a rolling series of improvements rather than a single release.

This push follows the Foundation's same-day launch of a neutral RPC performance benchmark at solana.com/data, measuring Alchemy, Helius, QuickNode, and Triton One from seven global regions. Both initiatives reflect the same underlying bet: that improving the infrastructure around building on Solana compounds into more and better applications over time.