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
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago