MCP SERVER

Created By
JeanVittorya year ago
With this MCP, you can debug your application by querying any issue to an LLM using the latest documentation available on the web. We currently support LangChain, LlamaIndex, and OpenAI docs, but you can add any other sources as needed.
Overview

What is MCP SERVER?

MCP SERVER is a tool that allows developers to debug their applications by querying issues using the latest documentation available on the web. It currently supports LangChain, LlamaIndex, and OpenAI documentation, with the ability to add more sources as needed.

How to use MCP SERVER?

To use MCP SERVER, clone the repository from GitHub, set up a Python virtual environment, and install the necessary dependencies. You will also need to set up an API key from Serper to access the documentation.

Key features of MCP SERVER?

  • Query any issue using the latest documentation.
  • Support for multiple documentation sources.
  • Easy installation and setup process.

Use cases of MCP SERVER?

  1. Debugging applications by referencing up-to-date documentation.
  2. Integrating additional documentation sources for customized queries.
  3. Assisting developers in resolving issues quickly with accurate information.

FAQ from MCP SERVER?

  • What programming languages does MCP SERVER support?

MCP SERVER is built with Python, but it can be used to query documentation for any programming language.

  • Is there a cost to use MCP SERVER?

No, MCP SERVER is free to use.

  • How can I add more documentation sources?

You can add more sources by modifying the 'docs_urls' variable in the constants folder of the project.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
JeanVittory
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