Model Context Protocol (MCP) is an open protocol that lets AI applications such as Claude, ChatGPT, Cursor and Windsurf connect to local and remote tools and data through servers.

Browse it as a searchable site: sagargupta.online/awesome-mcp-servers, with search, category and language filters, and live stars. It is rebuilt from this README every hour.

This list is curated, not exhaustive, and open to anyone. Bigger MCP lists exist. The point of this one is that everything on it has been checked. Curated does not mean famous: your project needs no minimum star count or age, and submitting your own server is welcome. Every entry:

• implements MCP for real -- not a README with a server.json next to it
• states an open-source licence -- a LICENSE file, or a licence field in its package manifest
• was pushed within the last 180 days, and is not archived
• documents how to install and configure it, so someone else can actually run it
• appears exactly once, in one category

Hosted servers with no public source are the one exception, marked Remote. Instead of a licence and a push date, each links the operator's own documentation naming the endpoint, the authentication and the tools; CI checks the endpoint answers; and, like every entry, it merges itself only once its author has starred the repository.

Those rules are enforced by CI, not by good intentions: a pull request that breaks the format, adds a dead link, or submits an unlicensed repo fails its checks. A monthly audit re-checks every listed repository and files what has rotted.

An MCP server runs as a trusted extension of your assistant, with your files and your credentials. Read the source before you configure one -- a place on this list is a filter, not an audit. See SECURITY.md.

• Official
• Servers
  • Data & Databases
  • Developer Tools
  • Cloud & Infrastructure
  • Productivity
  • Search & Knowledge
  • Communication
  • File Systems & Storage
  • AI & ML
  • Finance
  • Monitoring & Observability
  • Design & Creative
  • Testing & QA
  • Security
  • Web Browsing & Scraping
  • Media & Entertainment
  • Travel & Location
  • E-commerce
  • Game Development
  • IoT & Home Automation
  • Marketing & Analytics
  • Knowledge Management
• Frameworks & Libraries
• Clients
• Tutorials & Articles
• Videos
• Community

• MCP Specification - The official protocol specification.
• MCP Servers (Reference) - Official reference server implementations (everything, fetch, filesystem, Git, memory, sequentialthinking, time).
• MCP Inspector - Visual testing tool for MCP servers.
• MCP Registry - Official community-driven registry for MCP servers.
• MCP Apps - Official MCP Apps spec and SDK for interactive UIs in AI clients.
• MCP Bundles (MCPB) - Official bundle format for one-click local MCP server installs.
• MCP Quickstart Resources - Official quickstart weather servers and clients in five languages.
• MCP Conformance Suite - Official conformance test suite for MCP implementations.
• MCP Example Remote Server - Official reference MCP server covering all features plus OAuth 2.0.

Support tiers reflect which MCP primitives each client implements, verified against its own docs: Full tools, resources, prompts, plus sampling or elicitation. Standard tools, resources and prompts. Tools + resources no prompts. Tools only tools alone. Partial tools plus some but not all of resources and prompts.

• Introduction to MCP - Official introduction to the protocol.
• Building Your First MCP Server - Step-by-step server tutorial.
• MCP for Claude Desktop - Getting started as a user.
• Build an MCP Server (Python / Node / Java) - Multi-language build guide.
• MCP for Beginners - Microsoft open curriculum with hands-on MCP lessons and labs.
• Writing Effective Tools for AI Agents - Anthropic guide to designing effective tools for AI agents.
• Code Execution with MCP - Anthropic write-up on calling MCP tools as code to cut token usage.
• MCP Architecture Overview - Official docs on how MCP hosts, clients, servers and transports fit together.
• MCP Authorization Spec - OAuth 2.1 authorization requirements for remote MCP servers.
• MCP Security Best Practices - Spec threat model and mitigations for token passthrough and confused deputy.
• MCP Course (Hugging Face) - Hugging Face course covering MCP theory, SDKs and deployment.
• MCP Tool Poisoning Attacks - Security write-up on hidden instructions in MCP tool descriptions.

• The Model Context Protocol (MCP) -- Anthropic - Official overview of Model Context Protocol.
• Build a Real-world MCP Server in One TypeScript File - Full tutorial by Nader Dabit.
• Building Agents with MCP - Full Workshop - Mahesh Murag (Anthropic) full workshop on building MCP servers and agents.
• What is MCP? Integrate AI Agents with Databases and APIs - IBM Technology explainer on MCP connecting agents to databases and APIs.

• MCP GitHub Discussions - Official community discussions.
• r/ClaudeAI - Reddit community with MCP discussions.
• MCP Servers Directory - Web directory of MCP servers.
• MCP Contributors Discord - Official Discord for MCP spec, SDK and working group discussion.
• Glama MCP Registry - Searchable registry of open-source MCP servers.
• Smithery - Hosted MCP server registry and marketplace for agent tool connections.
• Socketlist - Directory of MCP servers from the official MCP Registry, scored 0-100 on maintenance, security hygiene and adoption.
• Awesome Agent Skills - The sister list: Agent Skills, curated and checked by the same CI.

Anyone can contribute, including your own server. Your project needs no minimum star count and no minimum age -- if it works, is licensed and is documented, it qualifies. A hosted server with closed source qualifies too, under the hosted-server rules. Read CONTRIBUTING.md for the details.

To add a server:

1. Fork the repo and branch off main.
2. Add one row to the most appropriate existing category. Alphabetical order is preferred, not required.
3. Follow the format: | [Name](URL) | Description | Language | with the description at 80 characters or fewer.
4. Run python scripts/validate.py and fix what it reports.
5. Star the repository. A pull request only merges itself once its author has starred.
6. Open a pull request and answer the affiliation question. Submitting your own project is welcome; not disclosing it is not.

What happens after that, from the checks to the website:

The spec behind the picture is docs/diagrams/submission-pipeline.yaml, rendered with orrery.

Once it merges, a bot thanks you on the pull request with a badge for your project's README. It links back here, so people who find your server can find the rest of the list:

[![Listed in Awesome MCP Servers](https://sagargupta.online/awesome-mcp-servers/badge.svg)](https://github.com/Sagargupta16/awesome-mcp-servers)

A star is what lets your pull request merge itself. Without one it waits, labelled missing-star, until you star or a maintainer merges it by hand.

Other ways to help, no pull request needed: report rot (a dead link, an archived upstream, a project that no longer speaks MCP) by opening an issue, since pruning is as useful as adding; fix a description that is too terse or reads like marketing; fill a thin category, of which the Clients and Tutorials sections are the thinnest; or triage the monthly health report, where confirming or dismissing an item is a real contribution.

Two shapes cover the list. A stdio server is one your client starts itself and talks to over stdin and stdout. A remote server is hosted by the vendor, so the client needs only the endpoint; those rows carry Remote in the Language column.

Two stdio servers, run straight from their published packages:

{
  "mcpServers": {
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/allowed/dir"]
    },
    "fetch": {
      "command": "uvx",
      "args": ["mcp-server-fetch"]
    }
  }
}

A remote server. type is not optional here: an entry with a url and no type is read as a stdio server and skipped by Claude Code, which reports that the server has a url but no type.

{
  "mcpServers": {
    "example": {
      "type": "http",
      "url": "https://mcp.example.com/mcp"
    }
  }
}

Where that JSON lives, and which extra keys it takes, differs per client -- check your own client's docs. The protocol's guide to connecting a local server walks through the stdio case, and each server's README lists the arguments, tokens and environment variables it expects.