solana-docs-mcp-server
# solana-docs-server MCP Server
[](https://smithery.ai/server/@aldrin-labs/solana-docs-mcp-server)
solana docs context
This is a TypeScript-based MCP server that implements a simple notes system. It demonstrates core MCP concepts by providing:
- Resources representing text notes with URIs and metadata
- Tools for creating new notes
- Prompts for generating summaries of notes
<a href="https://glama.ai/mcp/servers/v2cs13njts"><img width="380" height="200" src="https://glama.ai/mcp/servers/v2cs13njts/badge" alt="solana-docs-mcp-server MCP server" /></a>
## Features
### Resources
- List and access notes via `note://` URIs
- Each note has a title, content and metadata
- Plain text mime type for simple content access
### Tools
- `create_note` - Create new text notes
- Takes title and content as required parameters
- Stores note in server state
### Prompts
- `summarize_notes` - Generate a summary of all stored notes
- Includes all note contents as embedded resources
- Returns structured prompt for LLM summarization
## Development
Install dependencies:
```bash
npm install
```
Build the server:
```bash
npm run build
```
For development with auto-rebuild:
```bash
npm run watch
```
## Installation
### Installing via Smithery
To install solana-docs-server MCP Server for Claude Desktop automatically via [Smithery](https://smithery.ai/server/@aldrin-labs/solana-docs-mcp-server):
```bash
npx -y @smithery/cli install @aldrin-labs/solana-docs-mcp-server --client claude
```
To use with Claude Desktop, add the server config:
On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`
```json
{
"mcpServers": {
"solana-docs-server": {
"command": "/path/to/solana-docs-server/build/index.js"
}
}
}
```
### Debugging
Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector), which is available as a package script:
```bash
npm run inspector
```
The Inspector will provide a URL to access debugging tools in your browser.
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_api_reference retrieves SDK API details, get_latest_docs fetches documentation sections, and search_docs performs searches across documentation. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with snake_case (get_api_reference, get_latest_docs, search_docs). The verbs 'get' and 'search' are appropriately used, and there are no deviations in naming conventions.
With only 3 tools, the server feels thin for a documentation domain that might benefit from more granular operations (e.g., filtering, version-specific docs, or content updates). While the tools cover basic needs, the count is borderline minimal for comprehensive documentation access.
The tools provide core documentation access: retrieving API references, latest docs, and searching. However, there are minor gaps such as no update or management tools for documentation content, and no filtering or categorization options, which agents might need for advanced workflows.