We build the MCP server on mcp.yourbrand.com, the full docs site at mcp.yourbrand.com/docs, and the interactive app UI — then run the directory sprint so consumers, developers, and agents find you with click-through to your site.
We run this playbook on ourselves first — our own apps are published and live in the ChatGPT app store, through the full review process.
ChatGPT does not call WebMCP in the browser — it calls a remote MCP server on mcp.yourbrand.com. But the data behind the carousel and the tools on www.yourbrand.com can be the same MCPBundles relay (CMS, feeds, your site, web-app backend). You do not need a separate public API if we can integrate server-side. Learn how WebMCP Hosting works.
Live MCP on mcp.yourbrand.com — data via API, feed, or our relay
ChatGPT and Claude connect to a remote MCP server on mcp.yourbrand.com, not to WebMCP in the browser. The carousel widget renders from structuredContent returned by MCP tools. That data can come from a documented API — or from the same MCPBundles relay we use for WebMCP: CMS, product feeds, JSON-LD, sitemap-backed fetch, or your web-app backend. One integration layer, two surfaces.
What you need
Best for: Brands that want the in-chat carousel and full directory sprint — with or without a formal public API.
www.yourbrand.com in Chrome — same backend can power ChatGPT too
WebMCP exposes tools on www.yourbrand.com for Chrome browser agents via document.modelContext. We host the relay; secrets stay server-side. That relay is not separate from store launch — it is often how we integrate brands that only have a homepage, CMS, or web app today. Wire the same relay to mcp.yourbrand.com and you get ChatGPT carousel without standing up a new REST API first.
What you need
Best for: Start on www, expand to ChatGPT/Claude on the same data path — especially when “API” means “our website”.
Most brands launch on consumer stores and docs, then stop — missing Cursor, the MCP Registry, community indexes, and developer discovery rows. We close that gap by default in the directory sprint.
Official apps where shoppers already ask AI
When someone asks ChatGPT or Claude for holidays from Manchester, broadband in SW1A, or insurance for a van — your brand should be the app that answers, not a footnote in a generic paragraph.
Owned content AI can cite with confidence
Shelf presence is not a replacement for structured docs, FAQs, and third-party mentions. We ship a customer docs portal on mcp.yourbrand.com with llms.txt, FAQ schema, and launch kit — surfaces vendor-built deployments often skip.
Everywhere developers and agents search for MCP
A beautiful endpoint with zero directory presence is a dead launch. We list you on Cursor, the official MCP Registry, PulseMCP, Smithery, Glama, and MCPBundles /skills — Hub connect paths, SEO, and IndexNow on our directory alongside community indexes.
Browser agents on your main website
Chrome and other browser agents can invoke tools declared on www.yourbrand.com via document.modelContext — no separate install step. Optional add-on for brands that want discovery on the marketing site itself.
Building the MCP server is roughly 40% of the job. Getting into the directories where humans and agents actually look is the other 60%.
| Directory | Audience | Package |
|---|---|---|
| ChatGPT Apps | Consumer shelf | Launch |
| Claude Connectors | Research & business shelf | Launch |
| cursor.directory | Cursor users browsing MCP | Launch |
| Official MCP Registry | VS Code, Copilot, crawlers | Launch + Widget |
| Cursor marketplace plugin | IDE + Cloud agents | Launch + Widget |
| PulseMCP · Smithery · Glama · MCPBundles /skills | Community indexes + developer SEO | Growth |
| WebMCP on www.{brand}.com | Chrome browser agents | Growth |
Production MCP on mcp.yourbrand.com
Directory sprint + docs portal
Growth retainer — optional after launch
You keep your brand on your subdomain. We build and operate mcp.yourbrand.com for the live MCP server and mcp.yourbrand.com/docs for the full docs portal — tool tables, geo-shaped example queries, ChatGPT and Claude quick starts, privacy, troubleshooting, plus llms.txt and FAQ schema. Not a PDF handover.
Indicative project fees below. UK customers may invoice in GBP. Payment: 40% on SOW, 40% on staging UAT, 20% on store submission accepted.
Timeline: 4–6 weeks
Official MCP on your domain, docs portal, and consumer store submissions — text/JSON results.
Timeline: 6–10 weeks
Interactive carousel, fullscreen detail, and click-out straight into your booking flow.
Timeline: After launch
Keep directories healthy, APIs in sync, and telemetry flowing to marketing.
Multi-app portfolios, private networking, SLAs, and WebMCP at scale.
Competitors rarely publish apples-to-apples tiers for brand MCP App launches. These anchors help CFOs sanity-check our $45k–$85k project fees.
| Provider / path | Typical cost | What you get | Gap vs managed launch |
|---|---|---|---|
| Specialist MCP app vendors | Sales-led — no public tiers | Vertical MCP build, ChatGPT + Claude, docs on customer domain | No published pricing; weak Cursor, Registry, and community directory coverage |
| Smithery (Arcade.dev) | Free tier; paid plans in transition | Developer MCP registry and hosting — Smithery joined Arcade.dev in August 2026; smithery.ai still lists and hosts servers | Not a brand app build, consumer store submission, or widget program |
| MintMCP Teams | ~$1,250/mo (50 seats) | Internal enterprise MCP gateway | Employee agents — not consumer ChatGPT Apps for your brand |
| Generic AI app agency | $40k – $150k+ project | Custom ChatGPT-style app or RAG wrapper | Rarely includes Claude, Cursor, Registry, or directory ops |
| In-house build | 2–3 FTE × 4–6 months | Internal team owns full stack | Store review cycles, widget CSP, and directory maintenance often slip |
| Dimension | MCPBundles | Specialist vendor | In-house | Dev shop |
|---|---|---|---|---|
| Time to live stores | 4–10 weeks fixed scope | Similar (estimated) | 4–6+ months typical | 3–8 months |
| ChatGPT + Claude listings | Included | Included | If prioritized | Sometimes ChatGPT only |
| Cursor + MCP Registry | Launch + Widget default | Usually skipped | Often deferred | Rarely included |
| MCPBundles /skills SEO | Growth tier | No | No | No |
| Citation GEO (llms.txt, FAQ schema) | Included | Partial (docs only) | Varies | Rare |
| Published pricing | Yes — this page | No | Internal budget | Quote only |
You submit the request form. We confirm fit, data path, and which directory tiers belong in scope.
API access, geo/category prompt library, click-out rules, and compliance sign-off.
MCP server, docs portal, widget if scoped — on staging before custom domain cutover.
Store submissions, Registry, Cursor, community dirs, /skills — then 30 days launch support.
Submit the intake form — we confirm fit and schedule a scoping call. No HubSpot; same secure form pipeline as our other contact pages.
Request a directory launch