solana-docs

solana-docs-server is an MCP server that provides a simple, note-based context for Solana-related documentation and summaries. It exposes a lightweight note resource model where each note has a title, content, and metadata, referenced via note:// URIs. The server also includes a tool for creating new notes (create_note) and a prompt-based capability to summarize all stored notes (summarize_notes). You can interact with the server through MCP clients that send the standard MCP protocol messages, enabling you to create and retrieve notes, and to request generated summaries that incorporate the notes as embedded resources. This makes it suitable for building knowledge bases, quick Solana reference guides, or context packs for LLM-assisted analysis.

To use it, start the server and connect via an MCP client. Use create_note to add new notes by providing a title and content. Retrieve and explore notes using their note:// URIs, and invoke summarize_notes to obtain a structured prompt suitable for LLM summarization, which will include all stored notes as embedded resources. The server demonstrates core MCP concepts such as resource representation, tooling, and prompt generation, making it a practical example for developing and testing MCP-based integrations.

Prerequisites:

• Node.js and npm installed on your system
• Basic familiarity with npm scripts and building TypeScript projects

1. Install dependencies

npm install

2. Build the server

npm run build

3. Run the server (development or production as needed)

# Example (adjust path to built entry as needed)
node build/index.js

4. Optional: Run in watch mode for auto-rebuild during development

npm run watch

5. If integrating with Claude Desktop via Smithery (optional): follow the Smithery installation steps shown in the README to install the MCP server and configure Claude Desktop to point at the built server binary at the given path.

Tips and considerations:

• The MCP server communicates over stdio when launched by an orchestration tool or client; ensure your environment forwards stdio correctly if you’re debugging.
• The example Claude Desktop config uses a path to the built index.js; you may need to adjust this path to match your environment and build output location.
• If you plan to deploy publicly or semi-publicly, consider adding environment variables for access control or persistence paths for notes.
• Ensure you run npm install after cloning the repository to fetch dependencies, and run npm run build before attempting to start the server.
• The summarize_notes tool returns a structured prompt suitable for LLM summarization and includes all notes as embedded resources; you can extend prompts or metadata handling as needed for your use case.