Documentation MCP Server

Created By
SubaashNaira year ago
An MCP server for accessing updated documentation of popular libraries
Overview

what is Documentation MCP Server?

Documentation MCP Server is a server designed for developers to access updated documentation of popular libraries through a unified interface.

how to use Documentation MCP Server?

To use the Documentation MCP Server, you can either run it using an installation script, Docker, or manually install it. After installation, access the web interface at http://localhost:3000 or use the RESTful API for programmatic access.

key features of Documentation MCP Server?

  • Documentation Aggregation from various library sources
  • Search Functionality across all libraries
  • Version Management for different library versions
  • Automatic Updates for the latest documentation
  • API Access for programmatic documentation retrieval
  • Interactive Web Interface for browsing documentation

use cases of Documentation MCP Server?

  1. Developers looking for a centralized documentation source for multiple libraries.
  2. Teams needing to access and manage documentation for different versions of libraries.
  3. Automating documentation updates for continuous integration workflows.

FAQ from Documentation MCP Server?

  • How do I install the Documentation MCP Server?

You can install it using an installation script, Docker, or manually following the instructions in the Installation Guide.

  • Can I access the documentation programmatically?

Yes! The server provides a RESTful API for programmatic access to the documentation.

  • Is there a web interface available?

Yes, you can access the web interface by navigating to http://localhost:3000 after running the server.

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