[FEATURE]

Preflight Checklist

• [x] I have searched existing requests and this feature hasn't been requested yet
• [x] This is a single feature request (not multiple features)

Problem Statement

When building agentic AI workflows with Claude, developers face
6 recurring problems with MCP servers:

1. No central discovery — finding the right MCP server requires

digging through GitHub repos, Reddit posts, and scattered READMEs

1. Distribution is manual — JSON configs shared via Slack messages,

no standard way to distribute approved servers across a team

1. No version control — no way to pin a server version, track

changes, or rollback when something breaks

1. Zero audit trail — no visibility into which AI tools are running,

who installed them, or when

1. Configs fail silently — misconfigured servers break without

useful errors before they hit production

1. No governance — no approval process, anyone installs anything,

no health monitoring

Proposed Solution

MCPNest (mcpnest.io) — a marketplace and governance layer built
on top of the MCP ecosystem.

7,561+ MCP servers indexed, one-click install for Claude Desktop,
Cursor, and Windsurf.

Free tools:
— Composer: full multi-server config in 30 seconds
— Config Validator: catches errors before production
— Bundle Sharing: share your entire stack as one link
— AI Discovery: plain English to ready-to-paste config
— MCP Generator: scaffold new servers with AI
— Registry Status: live health dashboard

Enterprise workspaces: private registry per team, version
control per server, full audit log, role-based access, and
health monitoring.

Coming June 16 — the Gateway: one authenticated URL per
workspace with full tool call logging at the MCP protocol level.

Built to complement the official Anthropic registry, not
replace it. The registry is the source of truth — MCPNest
is the UX, governance, and tooling layer on top.

mcpnest.io · @MCPNest · malasartes@mcpnest.io

Alternative Solutions

_No response_

Priority

High - Significant impact on productivity

Feature Category

CLI commands and flags

Use Case Example

Example scenario:

1. A platform engineer at a company wants to standardise which

MCP servers their team uses with Claude Desktop and Cursor

1. Without MCPNest, they manually write JSON configs, share them

via Slack, and have no way to enforce versions or track what
is installed across the team

1. With MCPNest, they create an Enterprise workspace, add approved

servers, and share one authenticated registry URL with the team.
Every developer points their Claude Desktop config to that URL
once — and gets all approved servers automatically

1. When a server is updated or deprecated, the platform engineer

changes it in one place. The entire team gets the update
without touching their local config

1. The audit log shows exactly who installed what, when — which

satisfies IT and security requirements

This saves hours per week and removes an entire class of
"it works on my machine" problems with MCP tool configurations.

Additional Context

<img width="1200" height="630" alt="Image" src="https://github.com/user-attachments/assets/c69bdd77-2ac4-4dd7-b355-7564b1c51728" />