MCP Servers Collection

Created By
XyAgenta year ago
Overview

What is MCP Servers Collection?

MCP Servers Collection is a repository that hosts a collection of Model Context Protocol (MCP) servers, each providing specific functionality through a standardized interface, implemented in Python with Server-Sent Events (SSE) transport.

How to use MCP Servers Collection?

To use the MCP Servers Collection, clone the repository from GitHub, and follow the provided guidelines to create new servers based on the template server. Each server can be run independently with its own configuration.

Key features of MCP Servers Collection?

  • Standardized implementation across all servers
  • Built with Python 3.12+ and modern language features
  • Exclusively uses Server-Sent Events for communication
  • Modular design for self-contained server modules
  • Consistent documentation structure
  • Docker support for containerization

Use cases of MCP Servers Collection?

  1. Creating custom MCP servers for various functionalities.
  2. Utilizing the YouTube server for video search and transcript retrieval.
  3. Developing educational tools or services using the template server.

FAQ from MCP Servers Collection?

  • Can I contribute new servers to the collection?

Yes! Contributions are welcome, and you can start by using the template server.

  • What are the requirements to run the servers?

All servers require Python 3.12+ and optionally Docker for containerization.

  • Is there documentation available for each server?

Yes, each server follows a standardized README structure for documentation.

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

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago