source-linked
GitHub MCP
Canonical source should be verified before feature-level publication.
Source ↗MCP servers
Legacy routes are retained, while publication status follows canonical-source verification. Each entry below is labeled with its actual review state rather than assumed to be current.
How to read the status labels
source-linked means a first-party or canonical repository is identified, but the server's current capabilities have not been independently re-verified against that source. refreshing means the route is preserved for continuity while a canonical upstream is actively being re-confirmed — treat the linked source as a starting point, not a settled fact.
refreshing
PostgreSQL MCP
Legacy route preserved; current maintained upstream needs verification.
Source ↗refreshing
Slack MCP
Legacy route preserved; current maintained upstream needs verification.
Source ↗source-linked
Filesystem MCP
Reference-server lineage; verify current package/source before deployment.
Source ↗source-linked
Notion MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗refreshing
Excel MCP
Legacy URL retained while a canonical upstream is verified.
Source ↗refreshing
Shopify MCP
Legacy URL retained while an official MCP source is verified.
Source ↗source-linked
Google Drive MCP
Reference-server lineage; verify current package/source before deployment.
Source ↗source-linked
Google Maps MCP
Reference-server lineage; verify current package/source before deployment.
Source ↗source-linked
Brave Search MCP
Reference-server lineage; verify current package/source before deployment.
Source ↗source-linked
Puppeteer MCP
Reference-server lineage; verify current package/source before deployment.
Source ↗source-linked
Memory MCP
Reference-server lineage for a knowledge-graph-backed persistent memory server.
Source ↗source-linked
GitLab MCP
Reference-server lineage; verify current package/source before deployment.
Source ↗source-linked
Sentry MCP
Reference-server lineage for error-tracking data access.
Source ↗source-linked
Cloudflare MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
SQLite MCP
Reference-server lineage; verify current package/source before deployment.
Source ↗source-linked
Fetch MCP
Reference-server lineage for web content fetching and conversion.
Source ↗source-linked
Time MCP
Reference-server lineage for timezone conversion utilities.
Source ↗refreshing
Redis MCP
Legacy route preserved; current maintained upstream needs verification.
Source ↗source-linked
AWS Knowledge Base Retrieval MCP
Reference-server lineage for Bedrock knowledge base retrieval.
Source ↗refreshing
EverArt MCP
Legacy route preserved; current maintained upstream needs verification.
Source ↗source-linked
Linear MCP
Reference-server lineage for Linear issue tracking.
Source ↗source-linked
Context7 MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Playwright MCP
First-party Microsoft repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Docker MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Terraform MCP
First-party HashiCorp repository link retained; capabilities should be read from upstream.
Source ↗refreshing
Asana MCP
Legacy route preserved; current maintained upstream needs verification.
Source ↗refreshing
Todoist MCP
Legacy route preserved; current maintained upstream needs verification.
Source ↗refreshing
Obsidian MCP
Legacy route preserved; current maintained upstream needs verification.
Source ↗source-linked
Everything MCP
Reference-server lineage used as a comprehensive test and demo server.
Source ↗source-linked
Sequential Thinking MCP
Reference-server lineage for structured, step-by-step reasoning support.
Source ↗source-linked
Pinecone MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Stripe MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Neon MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Supabase MCP
Community-maintained repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Vercel MCP
First-party documentation link retained; capabilities should be read from upstream.
Source ↗source-linked
HubSpot MCP
First-party documentation link retained; capabilities should be read from upstream.
Source ↗source-linked
Grafana MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Browserbase MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Firecrawl MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Apify MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Chroma MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Heroku MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Cloudinary MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Atlassian MCP
First-party documentation link retained; capabilities should be read from upstream.
Source ↗source-linked
Elasticsearch MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Snowflake MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
BigQuery MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗refreshing
Wikipedia MCP
Legacy route preserved; current maintained upstream needs verification.
Source ↗source-linked
Google Calendar MCP
Community-maintained repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Datadog MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
PagerDuty MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
Kagi MCP
First-party repository link retained; capabilities should be read from upstream.
Source ↗source-linked
DuckDuckGo MCP
Community-maintained repository link retained; capabilities should be read from upstream.
Source ↗MCP topic clusters
The wider MCP hub is organized around five clusters. Each links back to source-linked entities rather than independent editorial claims about capability or performance.
| Core protocol | Clients, servers, tools, resources, prompts, transports and authorization. |
|---|---|
| Server directory | Source-linked MCP implementations with canonical upstreams. |
| Agent frameworks | How frameworks expose or consume MCP without treating MCP as a framework replacement. |
| Local LLMs | MCP with local inference, with performance claims held until reproducible benchmarks exist. |
| India | Sovereignty, Indic-language workflows and DPDP-aware architecture without automatic compliance claims. |
A wider MCP server registry
For discovery across a broader catalog of MCP servers beyond this evidence-graph context, see MCPServer.in, a companion directory dedicated specifically to MCP server listings.