Nobody installs your MCP server. The ones who do don't use it.
Scored daily by a customisable AI persona to surface the most relevant engineering leadership news.
MCP server adoption analysis, insightful and relevant.
MCP server adoption suffers two distinct failures: the technical install across incompatible clients (Claude Desktop, Cursor, Windsurf, VS Code — each requiring different config formats and field names) and the 'second install' — getting users to actually make a tool call. The author's funnel shows that of users who reach the connect screen, fewer than half ever produce a single tool call, because once connected, users stare at a blank prompt and leave. The structural N×M problem (multiple clients × multiple servers) makes configuration brittle, with silent failures when field names like `url` vs `serverUrl` differ.
- Design your MCP server's install path as a measurable product funnel and instrument every step from 'heard about it' to 'first successful tool call' to eliminate silent drop-offs.
For a platform engineer building AI agent tools, this highlights that distribution is a product design problem — the install path must be engineered end-to-end, not just documented, because every config mismatch or blank prompt kills adoption before an agent ever executes.