Skip to main content
Glama

Search Docs MCP

Search Docs MCP Banner

Ever found yourself in a situation where your coding angel (or agent) stares blankly at you when you ask about the latest AI library? πŸ€” That's because they're still catching up with the training data from 2023!

This MCP (Model Context Protocol) tool is your secret weapon against outdated knowledge. It enables semantic search across multiple AI library documentations, ensuring your coding companion stays up-to-date with the latest tech. No more "I'm sorry, I don't have information about that" moments!

Simply configure your favorite libraries in the config file, and let your coding angel do the heavy lifting of finding the exact information you need from the official docs. It's like giving your AI assistant a direct line to the source of truth! πŸš€

Special thanks to Alejandro AO for his wonderful tutorial on creating MCP servers. This project was inspired by his work and uses his implementation patterns.

Features

  • πŸ” Search across multiple AI library documentations:

    • LangChain - A framework for developing applications powered by language models

    • LangGraph - A library for building complex AI workflows

    • CrewAI - A framework for orchestrating role-playing, autonomous AI agents

    • LlamaIndex - A data framework for LLM applications

    • OpenAI - Official documentation for OpenAI's API and models

  • ⚑ Fast and efficient search using Serper API

  • 🎯 Accurate results with semantic search capabilities

  • πŸ”„ Real-time documentation fetching

  • πŸ› οΈ Easy integration with MCP-based applications

  • βš™οΈ Easy configuration for adding new documentation sources

Related MCP server: SourceTap

Prerequisites

  • Python 3.12 or higher

  • Serper API key (for web search functionality)

  • MCP SDK 1.2.0 or higher

Installation

  1. Clone the repository:

git clone https://github.com/mostafa-ghaith/search-docs-mcp.git
cd search-docs-mcp
  1. Create and activate a virtual environment:

python -m venv .venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate
  1. Install dependencies:

pip install -e .
  1. Create a .env file in the project root and add your Serper API key:

SERPER_API_KEY=your_api_key_here

Configuration

The tool uses a configuration file (config.py) to manage documentation sources. You can easily add new documentation sources by editing this file:

DOCS_CONFIG = {
    "new_library": {
        "url": "docs.new-library.com",
        "description": "Description of the new library"
    }
}

Usage

As an MCP Server

The tool can be used as part of an MCP-based application. Here's an example of how to use it:

from mcp.server.fastmcp import FastMCP

mcp = FastMCP("docs")

# The tool will be available as part of your MCP application
# You can search documentation like this:
result = await mcp.get_docs(query="Chroma DB", library="langchain")

Connecting to Claude Desktop or Cursor

  1. For Claude Desktop:

    • Edit ~/Library/Application Support/Claude/claude_desktop_config.json:

    {
        "mcpServers": {
            "search-docs-mcp": {
                "command": "uv",
                "args": [
                    "--directory",
                    "/ABSOLUTE/PATH/TO/YOUR/search-docs-mcp",
                    "run",
                    "main.py"
                ]
            }
        }
    }
  2. For Cursor:

    • Navigate to Cursor Settings

    • Open the MCP tab

    • Click on "Add new global MCP server"

    • Add the server configuration similar to Claude Desktop

  3. Restart the application to apply changes

API Reference

get_docs(query: str, library: str)

Search documentation for a specific query in a given library.

Parameters:

  • query (str): The search query (e.g., "Chroma DB")

  • library (str): The library to search in (see config.py for supported libraries)

Returns:

  • Text content from the relevant documentation pages

Contributing

Contributions are welcome! Please feel free to submit a Pull Request. When adding new documentation sources, please update the config.py file with the appropriate URL and description.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Acknowledgments

  • Alejandro AO for the MCP server tutorial and implementation patterns

  • MCP for the framework

  • Serper for the search API

  • All the documentation providers for their valuable content

Available Tools

1 tool
get_docsA
Search the latest docs for a given query and library.

Supported libraries:
{supported_libraries}

Args:
    query: The query to search for (e.g. "Chroma DB")
    library: The library to search in (e.g. "langchain")

Returns:
    Text from the docs
ParametersJSON Schema
NameRequiredDescriptionDefault
queryYes
libraryYes

TDQS

A3.8/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

The description implies a read-only operation by saying 'Search', but it lacks details on behavior such as rate limits, authentication requirements, or result format. With no annotations to supplement, the description is insufficiently transparent for an agent to fully understand side effects or constraints.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and well-structured, with separate sections for purpose, arguments, and returns. It avoids unnecessary words, though the placeholder {supported_libraries} suggests dynamic generation.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the simplicity of the tool (2 parameters, no output schema), the description covers the basics. However, the return value is only vaguely described as 'Text from the docs', leaving ambiguity about whether it returns a single result or multiple, and in what format.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters4/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 0%, so the description must explain parameters. It does so effectively by providing examples for both 'query' and 'library', clarifying what each parameter expects. This adds value beyond the bare schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Search the latest docs for a given query and library.' It specifies the verb 'search', the resource 'docs', and the required parameters 'query' and 'library'. Even without sibling tools, the purpose is unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context on when to use the tool by giving examples of valid queries and libraries (e.g., 'Chroma DB', 'langchain'). It does not explicitly state when not to use it, but with no sibling tools, the guidance is adequate.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev0.1.0
    • First observedget_docs

TDQS

A3.8/5.0
Disambiguation5/5

Only one tool exists, so there is no risk of confusion or overlap between tools.

Naming Consistency5/5

With a single tool, naming consistency is not a concern; the name 'get_docs' clearly indicates its purpose.

Tool Count3/5

A single tool for searching docs is very minimal; it may be appropriate if the scope is strictly limited, but typically expects additional tools for browsing or managing documentation.

Completeness2/5

The tool only supports searching docs by query and library; missing capabilities like listing supported libraries, retrieving full documents, or filtering results, which limits its utility.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/mostafa-ghaith/search_docs_mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server