MCP Server for Up-to-Date Library Documentation

by AmirUpSkill

53 downloads
Not rated
GitHub Website

About

# MCP Server for Up-to-Date Library Documentation [![Python Version](https://img.shields.io/badge/python-3.11%2B-blue.svg)](https://www.python.org/) [![License](https://img.shields.io/badge/License-MIT-yellow.svg)](LICENSE) <!-- Update license if different --> [![Built with…

Details

Author
AmirUpSkill
Downloads
53
Categories
Knowledge Base

- Implements the Model Context Protocol for seamless client integration.
- Exposes a get_docs tool for searching official documentation.
- Uses Serper API for site‑specific searches (Langchain, LlamaIndex, OpenAI).
- Fetches and parses documentation content with httpx and BeautifulSoup.
- Built with Python 3.11+, asyncio, FastMCP, and managed via uv.

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name MCP Server for Up-to-Date Library Documentation
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

Install Python 3.11+ and the uv package manager. Obtain a Serper API key from serper.dev and store it in a .env file as SERPER_API_KEY. Run the server with uv run main.py. Then integrate with an MCP client like Claude Desktop (via JSON configuration) or Claude Code (via claude mcp add).

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "mcp server for up-to-date library documentation": {
            "Mcp-Server": {
                "command": "uv",
                "args": [
                    "init",
                    "mcp-server"
                ]
            }
        }
    }
}

McpServers

{
    "Mcp-Server": {
        "command": "uv",
        "args": [
            "init",
            "mcp-server"
        ]
    }
}

MCP Server for Up-to-Date Library Documentation

Python Version
License <!-- Update license if different -->
Built with uv

This project implements a Model Context Protocol (MCP) server in Python. Its primary function is to provide Large Language Models (LLMs) like Anthropic's Claude with real-time access to the latest documentation for specified Python libraries (Langchain, LlamaIndex, OpenAI) before they generate code suggestions.

Problem Solved

LLMs often possess knowledge based on their training data cutoffs. This can lead to outdated code suggestions, especially for rapidly evolving libraries common in the AI/ML space. This MCP server addresses this challenge by acting as a tool that allows the LLM to dynamically fetch and incorporate the most current documentation snippets into its context before responding to coding queries.

Features

MCP Standard: Implements the Model Context Protocol for seamless integration with compatible clients (e.g., Claude Desktop, Claude Code).
get_docs Tool: Exposes a specific tool that searches official documentation sites.
Targeted Search: Uses the Serper API to perform site-specific Google searches, ensuring results come directly from the official docs for:
Langchain (python.langchain.com/docs)
LlamaIndex (docs.llamaindex.ai/en/stable)
OpenAI (platform.openai.com/docs)
Content Fetching: Retrieves and parses the text content from the top search results using httpx and BeautifulSoup.
Modern Tooling: Built with Python 3.11+, asyncio, FastMCP, and managed using the uv package manager.

Architecture Overview

This server functions as a specialized "toolbox" within the MCP ecosystem:

1. An MCP Host (e.g., Claude Desktop, IDE with Claude Code) initiates a request requiring coding assistance for a supported library.
2. The MCP Client within the Host connects to this running MCP Server.
3. The LLM, recognizing the need for potentially up-to-date information, decides to use the get_docs tool provided by this server.
4. The Client invokes the get_docs tool on this server, passing the user's query and the target library.
5. This MCP Server constructs a site-specific search query (e.g., site:python.langchain.com/docs <user_query>).
6. It queries the Serper API to get the top documentation page links.
7. It fetches the content of these pages using httpx and extracts the relevant text using BeautifulSoup.
8. The extracted text (context) is returned to the MCP Client/Host.
9. The LLM uses this fresh context alongside the original prompt to generate a more accurate and up-to-date response/code suggestion.

Prerequisites

Python 3.11+
uv Package Manager: Install from Astral.sh.
Serper API Key: Obtain a free or paid key from serper.dev.
Node.js/npx: Required only if you plan to use the MCP Inspector for debugging.

Installation & Setup

1. Clone the Repository (if applicable):

    git clone <your-repository-url>
cd <your-repository-name>

2. Initialize Project (if starting fresh):

    # If you haven't cloned a repo with pyproject.toml
uv init mcp-server
cd mcp-server

3. Create and Activate Virtual Environment:

    uv venv
# Activate (Linux/macOS):
source .venv/bin/activate
# Activate (Windows PowerShell):
. \.venv\Scripts\Activate.ps1
# Activate (Windows Cmd):
.\.venv\Scripts\activate.bat

4. Install Dependencies:

    uv add "mcp[cli]" httpx python-dotenv bs4
# Or, if dependencies are listed in pyproject.toml:
# uv sync

Configuration

1. Create a file named .env in the root directory of the project.
2. Add your Serper API key to this file:

    SERPER_API_KEY=your_actual_serper_api_key_here
    
(The .gitignore file is already configured to prevent committing this file)

Usage

1. Run the MCP Server:
Make sure your virtual environment is activated.

    uv run main.py

The server will start and listen for connections via standard input/output (stdio), as configured in main.py.

2. Integrate with MCP Clients:

Claude Desktop:
Go to Settings > Developer > Edit Configuration.
Add an entry under mcpServers. You'll need to provide the full path to your uv executable and specify the command arguments.
Example structure (adjust paths accordingly):

            {
"mcpServers": [
{
"name": "docs-helper", // Or any name you prefer
"command": [
"/full/path/to/your/.venv/bin/python", // Or full path to uv binary
"-m", // If using python -m uv ...
"uv",
"run",
"main.py"
],
"workingDirectory": "/full/path/to/your/mcp-server/project"
}
]
}

Restart Claude Desktop. A tool hammer icon should appear.

Claude Code (CLI):
Use the claude mcp add command interactively or with flags.
Example interactive session prompts:
Server Name: documentation-fetcher (or your choice)
Project Type: local
Command: Specify the full path to uv and arguments, similar to Claude Desktop (e.g., /full/path/to/uv run main.py within the project directory).
Working Directory: /full/path/to/your/mcp-server/project
Use claude mcp list to verify.
Run claude - the tool should be listed.

_Refer to the official Anthropic MCP documentation for the most up-to-date client configuration details._

Development & Debugging

The MCP Inspector is a valuable tool for testing your server's capabilities without needing a full client integration.

1. Ensure Node.js and npx are installed.
2. Run the inspector, pointing it to your server's run command:

    # Ensure your .venv is activated first
npx @model-context-protocol/inspector "uv run main.py"

3. Open your web browser to http://localhost:5173.
4. Connect to the server via the Inspector interface.
5. Navigate to the "Tools" section, select get_docs, provide test values for query and library, and click "Run Tool" to see the output.

License

This project is licensed under the MIT License - see the LICENSE file for details. (You'll need to add a LICENSE file with the MIT license text if you choose this)*

---

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.