Directory coverage
Building the server is roughly forty percent of the job. Directory coverage is the coordinated sprint across consumer stores, developer IDEs, the official MCP Registry, MCPBundles /skills, and community indexes — so humans and agents actually find mcp.yourbrand.com.
Coverage is a matrix, not a single listing. These four facts decide how much of it you hold after launch.
Consumer shelf (ChatGPT, Claude), developer IDE (Cursor, Registry, VS Code), and open-web agent search (PulseMCP, Smithery, Glama, MCPBundles /skills, docs crawl). Each mode uses different directories — one launch sprint covers all rows.
PulseMCP, Smithery, Glama, and MCPBundles /skills are the same sprint row — public skill page, Hub connect path, IndexNow, and cross-list refresh alongside third-party community directories.
Official MCP Registry publish on customer DNS feeds VS Code, Copilot curation, and crawlers that mirror the canonical index — put geo keywords in the server name, not only the description.
Launch sprint covers consumer stores, Registry, Cursor, MCPBundles /skills, and community indexes — not just mcp.yourbrand.com going live. Most brands skip IDE and registry rows until someone coordinates the full matrix.
Exact checklist varies by package — Launch + Widget and Growth include the full consumer + developer sweep.
Confirm directory goals, competitor shelf presence, and which tiers belong in scope — stores, Registry, Cursor, /skills, community dirs, docs.
Registry and remote MCP health first; consumer store JSON; Cursor plugin pointing at mcp.yourbrand.com/mcp.
Customer-branded remote URL on PulseMCP, Smithery, Glama, and MCPBundles /skills — full-text search surfaces matter for agent discovery.
Growth tier includes telemetry and directory maintenance; fix rejected listings and stale metadata.
Shelf GEO is consumer stores specifically. Directory coverage is the full matrix — stores plus developer and community indexes. Managed MCP Apps includes both.
Google long-tail (“{brand} mcp”), FAQ schema, and Hub connect paths drive developer discovery. We eat our own cooking on every managed launch.
Official registry search matches server name first — encode category and geo intent in the published name (e.g. travelsupermarket-holidays-mcp), not a generic acronym.
Launch covers consumer Tier A. Skipping Cursor and Registry leaves IDE agents on a competitor’s endpoint — we scope honestly in intake.
Fill out the intake form — we reply within one business day to confirm fit and recommend a package.
Request a directory launch