The Problem The MCP ecosystem is expanding at an extraordinary pace. Anthropic, Microsoft, Google, AWS, and Cloudflare are all publishing official MCP servers. Hundreds of open source servers exist for every conceivable integration. Developers are connecting AI tools — Claude, Cursor, Windsurf — to internal databases, codebases, APIs, and filesystems. The infrastructure for doing this exists. The governance layer does not. Today, at most engineering teams: Every developer runs MCP servers on their own machine There is no central record of what servers are active There is no audit trail of what tools were called, by whom, or when Credentials — GitHub personal access tokens, database connection strings, API keys — are stored in JSON files on developer laptops There is no approval process for which servers developers can use There is no isolation — MCP servers run with the full permissions of the local user This is the gap MCPNest fills. MCPNest is the governance and infrastructure platform for MCP servers. It operates across three layers: a marketplace for discovery, a gateway for control, and a hosted infrastructure layer for isolation and centralisation. What it is A searchable catalogue of 7,500+ MCP servers indexed from the official Anthropic registry and GitHub. Every server has a quality score, compatibility matrix, publisher profile, and install configuration. What problem it solves Without a central catalogue, developers find MCP servers through GitHub searches, Reddit posts, and blog articles. There is no quality signal, no verification, no compatibility information. Teams end up with inconsistent tooling and no visibility into what is actually being used. Features 7,500+ servers indexed with quality scores and compatibility filters One-click install for Cursor and VS Code Publisher profiles with verified badges Server of the Week editorial picks Collections and curated starter packs Config Validator — validates syntax, endpoints, and arguments before installation MCP Composer — build multi-server configurations and share via link Trending servers with weekly install data What it is A single authenticated HTTPS endpoint per workspace. Every developer on the team points their AI client at the same Gateway URL. The Gateway authenticates the request, checks the tool allowlist, proxies to the correct upstream server, and logs the call. What problem it solves Without a gateway, every developer maintains their own local configuration. When a server changes, everyone updates manually. There is no central authentication, no audit, and no way to enforce which tools developers can use. Features Single endpoint per workspace Bearer token authentication (SHA-256) Per-member tokens Tool allowlists per member Full audit log per tool call Tool namespacing Workspace RBAC What it is MCP servers running in isolated Docker containers on central infrastructure, managed by the MCPNest Orchestrator. Developers deploy servers from a catalogue via the workspace dashboard. The AI client connects to the Gateway, which proxies to the hosted container. What problem it solves Running MCP servers locally means no isolation, no central credential management, no shared infrastructure, and no visibility into what is actually running. When a developer's laptop is lost or stolen, every credential in every local config file is exposed. When a developer leaves the company, there is no clean offboarding process. Features 12 verified servers available for one-click deploy Container isolation Credential management Real-time deploy console Per-instance log viewer Terminate with cleanup MCP Bridge Infrastructure Token security Data handling Container security Self-host One month. 14 versions shipped. 7,500+ MCP servers indexed. Enterprise Gateway live. 12 hosted servers operational. Partnerships with Grafana, RailPush, and Context7 confirmed. The MCP ecosystem needed a governance layer. MCPNest is it. mcpnest.io