Image: VoltAgent
Why it mattersAn MCP server reads your data and acts for you, so trust in who wrote it matters, and a vendor-built list cuts the search for the right one down to a decision about which product you already use.
A developer picking an MCP server reads a repository name they have never seen before and makes a trust decision. VoltAgent, an open-source agent framework, released a curated directory this week that answers one half of that: every entry is built by the company behind the product the server talks to, or by a widely used open-source project. The repository is at VoltAgent/official-mcp-servers on GitHub under MIT and sits at 211 stars in the five days since its public release.
VoltAgent calls the list "the curated directory of official MCP servers. No unofficial forks, no abandoned projects, just servers you can trust". The README's own count puts it at 286 servers across 14 categories. The categories: Cloud and DevOps, Databases and Data, Observability and Analytics, Browser Automation and Web Data, Search and Research, Developer Tools, Security and Code Quality, Productivity and Project Management, Finance and Payments, Communication and Messaging, AI and Media, Design and Collaboration, Travel and Lifestyle, and Web Marketing and Product.
Why "official" is the whole point
A Model Context Protocol server is a program an AI assistant can call that exposes what a product can do: query a database, create a ticket, send an email. Any MCP client, including Claude, ChatGPT and Cursor, can connect to one. The protocol does not identify the author of a server a client is talking to. A fork of a legitimate server is indistinguishable from the real one at the protocol level, and the server reads whatever data the user has authorised the client to pass to it.
VoltAgent states the rule plainly: "An MCP server can read your data and act on your behalf, so who built it matters. Every entry here is an official server from the company behind the product, or a widely used open source project". Where a company publishes no source but hosts an MCP endpoint directly, the directory links the vendor's official MCP documentation page.
What a Cloud and DevOps row looks like
The first category runs 31 entries. The names are the ones a developer recognises: google/mcp, cloudflare/mcp-server-cloudflare, vercel/next-devtools-mcp, supabase/mcp, Microsoft's Azure MCP, hashicorp/terraform-mcp-server, docker/mcp-gateway, netlify/netlify-mcp, CircleCI-Public/mcp-server-circleci, buildkite/buildkite-mcp-server, OctopusDeploy/mcp-server, GitLab's own MCP server, aliyun/alibabacloud-devops-mcp-server, and Railway's hosted endpoint. Each entry gives the repository and a one-line description of what the server exposes.
The format repeats across every category: a GitHub owner slash name, a short sentence, and, where the server is available through Claude's own connector marketplace, a direct link to the connector page.
What a reader still has to check
The list does not score servers. "Official" means the author is the vendor. Whether a given server is safe to grant every permission a client asks for is a separate question, and a security review of the specific tools a server exposes and the data a client is sending it is still the reader's job. The directory shortens the first step of that work: a list of 286 names that come from the places a reader was already going to look.
VoltAgent accepts submissions through GitHub pull requests to the repository. New entries have to meet the same vendor-built bar as the existing ones.
Source
- VoltAgent/official-mcp-servers on GitHub (the project README)
- Model Context Protocol specification
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.