Gemini Docs MCP Server
Related Servers
Alternatives to Gemini Docs MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables users to search Groq's API documentation using natural language queries through an MCP-compatible interface.MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to fetch, index, and perform semantic RAG-based searches on API documentation from various sources. It provides tools for hybrid search and collection management, allowing users to access up-to-date documentation from projects like Gemini and FastMCP.-
- AlicenseNot gradedqualityDmaintenanceProvides RAG (Retrieval Augmented Generation) access to technical documentation through MCP, enabling LLMs to search and retrieve relevant documentation on-demand.4MIT
- AlicenseAqualityDmaintenanceProvides access to Agno framework documentation for AI agents, enabling search and retrieval of SDK references, API endpoints, code examples, and integration guides through MCP-compatible tools.73MIT
- AlicenseNot gradedqualityDmaintenanceMCP server providing Gemini API documentation lookup and ready-to-use code snippets.GPL 2.0
- AlicenseNot gradedqualityDmaintenanceEnables searching and fetching Claude and Anthropic documentation with intelligent relevance scoring, optimized for MCP development, APIs, and examples.10 npm6MIT
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes with no overlap: fetch_gemini_doc retrieves and parses specific documentation pages, while search_gemini_docs searches across the documentation index to find relevant pages. The descriptions explicitly guide users to use search first when unsure of the path, then fetch for detailed content, creating a logical workflow without confusion.
Both tools follow a perfect verb_noun pattern with consistent snake_case naming: fetch_gemini_doc and search_gemini_docs. The naming clearly indicates the action (fetch/search) and the target (gemini_doc/gemini_docs), making them predictable and easy to understand as a set.
With only 2 tools, this server feels thin for a documentation exploration domain. While the tools cover the core workflow of search-then-fetch, additional operations like listing available documentation categories or getting metadata about the documentation set would enhance completeness. The count is borderline minimal but functional.
For a documentation server, the surface covers the essential workflow: searching for relevant pages and fetching detailed content. The main gap is the lack of a tool to browse or list available documentation sections without searching, which could help agents discover content. However, the search tool with its comprehensive examples mitigates this gap reasonably well.