solana-docs-mcp-server
Related Servers
Alternatives to solana-docs-mcp-server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceProvides curated documentation access via the Gemini API, enabling users to query and interact with technical docs effectively by overcoming context and search limitations.14-
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to access and search up-to-date Solana documentation, get canonical spec references, and fix Anchor/Pinocchio Solana programs via MCP tools.1280MIT
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol server for ingesting, chunking and semantically searching documentation files, with support for markdown, Python, OpenAPI, HTML files and URLs.-
- FlicenseNot gradedqualityDmaintenanceA simple Model Context Protocol server that enables searching and retrieving relevant documentation snippets from Langchain, Llama Index, and OpenAI official documentation.-
- AlicenseNot gradedqualityCmaintenanceA unified context layer that connects your local data — repositories, documents, remote machines, and notes — to LLM interfaces through the Model Context Protocol (MCP).3MIT
- AlicenseAqualityBmaintenanceAccess to 819+ documentation sources from devdocs.io with semantic search capabilities.9MIT
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.