Awesome MCP Servers

Created By
nalluri333a year ago
Overview

What is Awesome MCP Servers?

Awesome MCP Servers is a curated list of Model Context Protocol (MCP) servers that facilitate AI models to interact with local and remote resources through standardized server implementations.

How to use Awesome MCP Servers?

To use Awesome MCP Servers, explore the curated list of MCP servers available on the GitHub repository, and follow the provided links to access documentation, tutorials, and community resources.

Key features of Awesome MCP Servers?

  • Comprehensive directory of production-ready and experimental MCP servers.
  • Categorized listings for easy navigation (e.g., Browser Automation, Cloud Platforms, Developer Tools).
  • Community support through Discord and Reddit.

Use cases of Awesome MCP Servers?

  1. Integrating AI models with various APIs for enhanced functionality.
  2. Automating tasks through browser automation servers.
  3. Accessing and managing databases securely.

FAQ from Awesome MCP Servers?

  • What is the Model Context Protocol (MCP)?

MCP is an open protocol that enables AI models to securely interact with local and remote resources through standardized server implementations.

  • How can I contribute to Awesome MCP Servers?

Contributions can be made by submitting pull requests on the GitHub repository with new server implementations or improvements to existing ones.

  • Is there a community for support?

Yes! You can join the Discord server or the subreddit for discussions and support.

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