MCP Servers Collection

Created By
mows21a year ago
Collection of Model Context Protocol (MCP) servers for Cline, Roo, and Claude Desktop
Overview

What is MCP Servers Collection?

MCP Servers Collection is a suite of Model Context Protocol (MCP) servers designed for AI assistants to interact with local and remote resources through a standardized protocol.

How to use MCP Servers Collection?

To use the MCP Servers, clone the repository and start the servers using Docker or manually install the requirements and run each server individually.

Key features of MCP Servers Collection?

  • Cline MCP Server for internal workflow orchestration and memory management.
  • Roo MCP Server for web scraping, automation, and browser control.
  • Claude Desktop MCP Server for local file operations and LLM integration.

Use cases of MCP Servers Collection?

  1. Automating web scraping tasks.
  2. Managing AI agent workflows.
  3. Executing shell commands and managing local files.

FAQ from MCP Servers Collection?

  • What is the purpose of the MCP servers?

They enable AI assistants to interact with various resources through a standardized protocol.

  • How do I start the servers?

You can start the servers using Docker or by manually installing the requirements and running them individually.

  • Is there documentation available?

Yes, API documentation is provided for each server in the repository.

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