MCP Documentation Server

Created By
esakrissaa year ago
Model Context Protocol documentation server for LangGraph and MCP.
Overview

what is MCP Documentation Server?

MCP Documentation Server is a customized server that facilitates integration between LLM applications and documentation sources via the Model Context Protocol (MCP).

how to use MCP Documentation Server?

To use the MCP Documentation Server, clone the repository, set up a virtual environment, install the package, and run the server with the provided configuration commands.

key features of MCP Documentation Server?

  • Access to specific documentation files for LangGraph and MCP.
  • Tools to fetch documentation from URLs within those files.
  • Integration capabilities with LLM applications like Cursor.

use cases of MCP Documentation Server?

  1. Providing documentation support for LangGraph applications.
  2. Enabling LLM applications to fetch and utilize documentation dynamically.
  3. Facilitating easy access to Model Context Protocol documentation.

FAQ from MCP Documentation Server?

  • What is the purpose of the MCP Documentation Server?

It serves as a bridge between LLM applications and documentation sources, allowing for efficient information retrieval.

  • How do I run the server?

You can run the server using the command provided in the setup instructions after configuring it with the necessary parameters.

  • Is there any security feature in place?

Yes, strict domain access controls are implemented to ensure secure access to documentation.

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