MCPNest launches MCP Composer to eliminate multi-server config pain
Ricardo Rodrigues built the MCP Composer at mcpnest.io/compose after launching MCPNest on April 4th, 2026, replacing error-prone manual JSON editing with a visual tool that generates complete multi-server `claude_desktop_config.json` setups in under 30 seconds.
Score breakdown
After launching MCPNest on April 4th, 2026, author Ricardo Rodrigues found the most-requested feature was the ability to install multiple MCP servers at once — a pain point that was causing even experienced platform engineers to spend 30-45 minutes on what should take seconds. His solution, the MCP Composer (available at `mcpnest.io/compose`), lets users visually search, add, and configure multiple MCP servers and generates the correct config format for their chosen client — Claude Desktop, Cursor, and others — without touching JSON. The tool also spawned a Bundle Sharing feature, where developers can share pre-composed server stacks via a link, making team onboarding dramatically simpler. A Gateway is planned to launch June 16, 2026, replacing per-developer local configs with a single authenticated workspace URL.
Ricardo Rodrigues, a platform engineer at a bank, launched MCPNest on April 4th, 2026 as a central registry for MCP servers. Within 48 hours, his DMs were flooded with one question: "How do I install multiple servers at once?" The problem was clear — a typical developer setting up Claude for serious work wants five or more servers simultaneously (GitHub, Postgres, filesystem, docs, search), each requiring its own JSON block inside `claude_desktop_config.json`. Writing that config by hand is fragile: a missing comma breaks everything, a wrong argument crashes Claude on startup, and error messages offer little guidance. Rodrigues watched experienced platform engineers spend 30-45 minutes on a task that should take 30 seconds.
It eliminates six specific failure categories: JSON syntax errors, wrong config format per client (Claude Desktop's `claude_desktop_config.json` lives in different paths on Mac vs.
The MCP Composer, accessible at `mcpnest.io/compose`, solves this with a four-step visual flow: search and add servers, configure each one (environment variables, connection strings, etc.), choose a target client, then copy or download the generated config. It eliminates six specific failure categories: JSON syntax errors, wrong config format per client (Claude Desktop's `claude_desktop_config.json` lives in different paths on Mac vs. Windows; Cursor uses its own format), missing required arguments, multi-server conflicts, the knowledge barrier around `npx -y` vs. `node` command syntax, and the inability to share or replicate setups. As a concrete example, the author describes building a three-server stack with `github-mcp-server` (28,700+ stars), Postgres, and Context7 in under two minutes — work that would have taken 20-30 minutes manually.
An emergent behavior after launch became its own dedicated feature: Bundle Sharing. Developers composed their ideal stacks, generated shareable bundle links, and posted them on Reddit and Twitter for others to clone in one click. Browsable at `mcpnest.io/bundle-sharing`, bundles are especially powerful for team onboarding — a platform engineer can generate a company-approved MCP stack link and drop it into the engineering onboarding doc so every new hire gets an identical, correctly configured setup instantly. The Composer currently handles local servers run via `npx` or `node`, but a Gateway feature is slated to launch June 16, 2026, replacing local per-developer configs with a single authenticated URL per workspace.