MCP Server for Documentation Search

Created By
deepmihira year ago
Overview

MCP Server for Documentation Search is a custom server that allows users to search through documentation for popular Python libraries such as LangChain, LlamaIndex, and OpenAI using the Model Control Protocol (MCP).

How to use MCP Server?

To use the MCP Server, you need to install the uv package manager, set up the project, and run the server. After that, you can connect it to Claude Desktop for documentation searches.

Key features of MCP Server?

  • Search documentation for specific queries across supported libraries.
  • Integration with Google Search API via Serper for finding relevant documentation pages.
  • Web scraping capabilities to extract content from documentation pages.
  • Designed to work seamlessly with Claude Desktop through MCP.

Use cases of MCP Server?

  1. Searching for specific functions or classes in Python libraries.
  2. Finding relevant documentation quickly without manual browsing.
  3. Assisting developers in understanding library usage through direct queries.

FAQ from MCP Server?

  • What libraries does the MCP Server support?

It supports popular Python libraries including LangChain, LlamaIndex, and OpenAI.

  • Is there a specific Python version required?

Yes, Python 3.10 or higher is required to run the MCP Server.

  • How do I troubleshoot connection issues with Claude Desktop?

Check the configuration file path, verify the absolute path, ensure uv is installed, and check Claude Desktop logs for errors.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
deepmihir
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago