Why we sunsetted mcpt

Takeaways

• Mintlify built mcpt.com (MCP server registry) in one week after viral MCP generator launch; shut down five days later despite ~3,000 day-one visitors.
• Three fatal reasons: marketplace ops exceeded lean-team capacity; diverted focus from core docs/dev-tools product; marketplace building isn’t Mintlify’s strength.
• Validation still useful—proved MCP discoverability demand—but focus beat momentum; share the “messy middle” of sunsetting moderate successes.
• Lesson: easy to lose north star during rapid growth; experiments OK if you pull plug quickly when misfit.

Notes

Han Wang post-mortem; relevant counterweight to “build every MCP directory” instinct. Pairs with vault Raindrop-as-remote-bookmarks (no local MCP registry) stance.

Open questions

• Does vault need any MCP server catalog beyond Raindrop + local .cursor/mcp.json config?