I'm a Platform Engineer at a bank in Porto, Portugal.
On 3 of April I had an idea. Today it's a live product with 7,554 servers, partnerships with Railpush, Grafana and other coming.
Here's the full story.
The problem
The MCP (Model Context Protocol) ecosystem was exploding. Every week a new server appeared on GitHub, got 500 stars, and disappeared into the void.
Developers wanting to extend Claude, Cursor, or Windsurf had to dig through GitHub repos, Reddit posts, and scattered READMEs.
There was no discovery layer. No App Store for MCP.
The plan
Build the npm registry for MCP servers. Fast.
The criteria: buildable in days, real market timing.
MCPNest won.
What I built
Starting from zero, in two weeks:
Discovery
7,554+ MCP servers indexed from the official Anthropic registry and GitHub. Search by name, category, client compatibility. Quality Score A–F. Security badges — Verified, No Auth, Local Process, Remote.
Install
One-click install configs for Claude Desktop, Cursor, Windsurf, and VS Code. Copy one JSON snippet and you're done.
Bundle Sharing
Create a named bundle of multiple MCP servers and share it as a single link. Someone clicks it, gets the combined config for all servers at once. Useful for teams that want to share a standard MCP setup without going through the full Enterprise tier.
MCP Composer
Build your full multi-server config visually. Select servers, fill in your keys, copy once.
MCP Generator ← the one I'm most proud of
Describe what you want in plain english. Claude writes the full TypeScript MCP server — tool schema, error handling, stdio transport — plus the install config. From idea to published server in under a minute.
Collections
Curated starter packs. Install a full stack in one config.
Enterprise Workspace
This is the one I'm betting on long term.
A private MCP registry for teams. The idea came from a conversation with an AI leader at a large enterprise who said: "IT and security won't let us install third-party MCP. We just need the recipe to build it ourselves."
What's live:
- Private registry with a single URL — your whole team points their config to it
- Version control — publish v1.1 and every team member gets the updated config immediately, no manual updates
- GitHub sync — link a repo and pull the latest version with one click
- Health monitoring — hourly cron checks all remote server endpoints, updates UP/DOWN status automatically
- Audit log — every action tracked: who added what, when, from where
- Team management — owner, admin, and member roles
- Invite by email — add team members who already have an MCPNest account
The GTM strategy is bottom-up, like Slack. Individual enterprise employees start using it via open source. They build their own configs, use the Composer, share bundles with colleagues. When IT notices, the Enterprise tier gives them the governance layer they need — SSO, audit logs, private registry, version control.
Credential Manager
Store API keys per server. The biggest friction point in MCP tooling — solved.
Publisher Analytics
30-day install charts, client breakdown, weekly performance. Know what's working.
Reviews + Ratings
The first MCP marketplace with community reviews.
The stack
- Next.js 16 with Turbopack
- Supabase (database + auth)
- Vercel (hosting)
- Stripe (payments)
- FastAPI crawler on Railway
- Built almost entirely in Claude sessions
The honest part
Features are the easy part. Distribution is hard.
650 visitors a week is not enough. The product is good. The challenge now is getting people to find it.
If you're building with MCP — mcpnest.io
If you publish MCP servers — list yours
Solo founder. Platform engineer by day. Building as fast as I can.
Top comments (0)