🐝 Swarms MCP Documentation Server

Created By
Ransom-Alphaa year ago
MCP server to connect AI agents to any github corpa
Overview

What is Swarms MCP?

Swarms MCP is a documentation server designed to connect AI agents to various GitHub corpora, enabling efficient retrieval of information from documentation databases.

How to use Swarms MCP?

To use Swarms MCP, clone the necessary repositories into the corpora/ directory, configure your environment, and start the server using the provided commands.

Key features of Swarms MCP?

  • Hybrid retrieval combining semantic and keyword search.
  • Dynamic loading of markdown and other file types.
  • Local-first design for low-latency access.
  • Automatic reindexing on file changes.
  • Healthcheck endpoint to ensure server readiness.

Use cases of Swarms MCP?

  1. Enabling AI agents to query documentation efficiently.
  2. Supporting local knowledge bases for AI applications.
  3. Facilitating seamless integration of various documentation formats.

FAQ from Swarms MCP?

  • Q: What types of files can be indexed?
    A: Swarms MCP supports various file types including .py, .ipynb, .md, .txt, .yaml, and more.

  • Q: How does the reindexing work?
    A: The server automatically reindexes when files in the corpora/ directory are modified, added, or deleted.

  • Q: Is there a healthcheck feature?
    A: Yes, there is a healthcheck endpoint to verify the server's operational status.

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