Search Docs MCP
Enables semantic search across CrewAI documentation for orchestrating autonomous AI agents.
Enables semantic search across LangChain documentation for AI application development.
Enables semantic search across LangGraph documentation for building complex AI workflows.
Enables semantic search across OpenAI documentation for API and models.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Search Docs MCPLook up LangChain's documentation on how to use Chroma DB."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Search Docs MCP
![]()
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
Clone the repository:
git clone https://github.com/mostafa-ghaith/search-docs-mcp.git
cd search-docs-mcpCreate and activate a virtual environment:
python -m venv .venv
source .venv/bin/activate # On Windows: .venv\Scripts\activateInstall dependencies:
pip install -e .Create a
.envfile in the project root and add your Serper API key:
SERPER_API_KEY=your_api_key_hereConfiguration
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
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" ] } } }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
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 toolget_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
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | ||
| library | Yes |
TDQS
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.
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.
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.
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.
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.
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 tool update
v0.1.0- First observed
get_docs
TDQS
Only one tool exists, so there is no risk of confusion or overlap between tools.
With a single tool, naming consistency is not a concern; the name 'get_docs' clearly indicates its purpose.
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.
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
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
Versioned documentation registry and semantic search for AI tools and coding assistants.
Provide your AI coding tools with token-efficient access to up-to-date technical documentation forβ¦
Token-efficient search for coding agents over public and private documentation.
@latest documentation and code examples to 9000+ libraries for LLMs and AI code editors in a singlβ¦
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables AI assistants to semantically search through indexed documentation websites and local code repositories using OpenAI embeddings and ChromaDB vector storage.-
- FlicenseBqualityDmaintenanceEnables AI assistants to query and search library documentation from GitHub repositories or web pages using RAG and web scraping.2-
- AlicenseNot gradedqualityDmaintenanceEnables LLMs to search and retrieve information from large technical documentation (OpenAPI specs, markdown) via intelligent chunking and semantic search.MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI assistants with access to design documentation across multiple code libraries, enabling discovery of existing utilities and patterns to avoid reimplementation.2MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
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