MCP Docs Search Server

Created By
RohitKrish46a year ago
This is a lightweight, plug-and-play MCP server that empowers any LLM to dynamically search and retrieve up-to-date documentation from popular AI libraries such as LangChain, LlamaIndex, and OpenAI.
Overview

What is MCP Docs Search Server?

MCP Docs Search Server is a lightweight, plug-and-play server that enables Language Learning Models (LLMs) like Claude or GPT to dynamically search and retrieve up-to-date documentation from popular AI libraries such as LangChain, LlamaIndex, and OpenAI.

How to use MCP Docs Search Server?

To use the MCP Docs Search Server, clone the repository, set up a virtual environment, install the necessary dependencies, and configure your environment variables with your Serper API key. You can then integrate it with LLMs to query documentation in real-time.

Key features of MCP Docs Search Server?

  • Web Search Integration using the Serper API to fetch relevant documentation.
  • Clean Content Extraction to provide human-readable text from HTML.
  • A structured get_docs tool for querying specific libraries in real-time.

Use cases of MCP Docs Search Server?

  1. Enabling LLMs to access the latest documentation for AI libraries.
  2. Assisting developers in finding relevant information quickly.
  3. Enhancing the capabilities of LLMs by providing them with real-time data.

FAQ from MCP Docs Search Server?

  • Can MCP Docs Search Server work with any LLM?

Yes! It is designed to work with various LLMs that can communicate using the Model Context Protocol (MCP).

  • Is there a limit to the number of libraries supported?

No, additional libraries can be easily added by updating the configuration.

  • How does the content extraction work?

It uses BeautifulSoup to parse HTML and extract clean, readable text.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
RohitKrish46
Star
0
Language
Python
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