adk-docs-ext

This MCP server extension wires the Gemini CLI to the ADK documentation source via the MCP LLMS-TXT Doc Server. It uses a local copy of the ADK documentation (via the sample_llms_txt path in the extension) so Gemini can answer questions about ADK with up-to-date information drawn from the official ADK docs. The adk-docs-mcp server exposes a ready-made Doc Server configuration that points Gemini at the local llms.txt content and streams data back through stdio for communication.

To use it, install the extension into your Gemini CLI setup as described in the installation steps, ensuring the adk-docs-mcp MCP server is available. When you ask questions about ADK concepts, features, or APIs, Gemini will consult the ADK docs through the LLMS-TXT Doc Server and return responses aligned with the latest official documentation. The Local_ADK_Docs path can be swapped to point at a local copy of llms.txt if you maintain your own reference copy.

Prerequisites:

• A working Gemini CLI installation
• Python installed (for uvx usage) or an environment that supports the uvx-based MCP server
• Access to the internet to fetch dependencies if you use the uvx path

Install the extension into Gemini CLI:

1. Install via the Gemini extensions command:

gemini extensions install https://github.com/derailed-dash/adk-docs-ext

2. (Optional) Clone directly into your extensions folder for local development:

mkdir -p ~/.gemini/extensions
git clone https://github.com/derailed-dash/adk-docs-ext.git ~/.gemini/extensions/adk-docs-ext

3. Ensure the MCP server is configured (as shown in mcp_config) to use the local ADK docs or adjust the Local_ADK_Docs path to point at your environment. If you prefer to use the provided sample llms.txt path, keep the default extensionPath reference; otherwise, replace with your own absolute path to llms.txt and ensure proper permissions.

4. Restart Gemini so the extension and its MCP server become available. You should see the adk-docs-ext extension loaded on startup and the adk-docs-mcp MCP server ready to respond to queries.

Tips and notes:

• The MCP server name is adk-docs-mcp; you can adjust the server name in your Gemini configuration if needed, but the provided example uses adk-docs-mcp.
• If you maintain your own llms.txt, point to it using the Local_ADK_Docs: path syntax in the URLs setting to ensure Gemini uses your local docs.
• The extension relies on the ADK docs repository's llms.txt; ensure you have the correct file path and that the file is kept up to date to get the latest information.
• If you encounter issues with the uvx-based server, ensure your Python environment is correctly configured and that uvx can be invoked from your shell with the provided arguments.
• For troubleshooting, verify file permissions, path expansions (extensionPath), and that the STDIO transport is functioning in your Gemini environment.