Mcp Server Ragdocs

Created By
sanderkoogera year ago
An MCP server that provides tools for retrieving and processing documentation through vector search, both locally or hosted. Enabling AI assistants to augment their responses with relevant documentation context.
Overview

What is Mcp Server Ragdocs?

Mcp Server Ragdocs is an MCP server that provides tools for retrieving and processing documentation through vector search, enabling AI assistants to enhance their responses with relevant documentation context.

How to use Mcp Server Ragdocs?

To use Mcp Server Ragdocs, set up the server by configuring the environment variables and deploying it locally or in the cloud. You can then utilize its API to perform documentation searches and retrievals.

Key features of Mcp Server Ragdocs?

  • Vector-based documentation search and retrieval
  • Support for multiple documentation sources
  • Local and cloud deployment options
  • Semantic search capabilities
  • Real-time context augmentation for AI models

Use cases of Mcp Server Ragdocs?

  1. Enhancing AI responses with relevant documentation.
  2. Building documentation-aware AI assistants.
  3. Implementing semantic documentation search for developers.
  4. Augmenting existing knowledge bases with contextual information.

FAQ from Mcp Server Ragdocs?

  • Can I deploy Mcp Server Ragdocs locally?

Yes! Mcp Server Ragdocs can be deployed locally using Docker Compose.

  • What types of documentation can be processed?

It supports various documentation formats and sources, allowing for flexible integration.

  • Is there support for cloud deployment?

Yes! You can deploy Mcp Server Ragdocs on cloud platforms with the appropriate configuration.

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