Managed MCP Apps
Get your brand into ChatGPT, Claude, Cursor, and every MCP directory — on your domain.
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.
One relay — ChatGPT carousel and WebMCP on your homepage
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.
ChatGPT carousel + AI app stores
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
- Search/list/quote journeys we can implement server-side (API, feed, or relay from your site)
- mcp.yourbrand.com + /docs portal (we build both)
- Click-out rules for bookings and checkout on your main site
Best for: Brands that want the in-chat carousel and full directory sprint — with or without a formal public API.
Homepage + shared relay
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
- A public homepage or web app we can add a hosted script to
- Structured content helps — CMS, feeds, JSON-LD, sitemap (not blind scrape-everything)
- Defined journeys: find, quote, contact, click-out to checkout
Best for: Start on www, expand to ChatGPT/Claude on the same data path — especially when “API” means “our website”.
Shelf GEO, Citation GEO, directories, and WebMCP — not pick-one
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.
Shelf GEO
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.
- ChatGPT Apps submission with geo/category intent in name + subtitle
- Claude Connectors via Team portal playbook
- Interactive MCP App UI — carousel, detail, book on your site
- Example prompts aligned to how people search in a place
Citation GEO
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.
- Branded /docs with tool tables, privacy, troubleshooting
- llms.txt + sitemap for agent crawlers
- FAQ JSON-LD on owned subdomain
- Press and footer snippets for marketing activation
Directory coverage
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.
- cursor.directory + Cursor marketplace plugin
- Official MCP Registry DNS publish
- PulseMCP, Smithery, Glama, MCPBundles /skills, Hub listing, IndexNow
WebMCP
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.
- Well-known WebMCP manifest on your domain
- Tools aligned to on-site journeys (quote, find store, compare)
- Live on mcpbundles.com today
- Enterprise / add-on — scoped per brand
One launch sprint. Your brand on every row — including ours.
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 |
Build, publish, and measure — end to end
Build
Production MCP on mcp.yourbrand.com
- 1–5 read tools wired to your APIs
- JSON schemas + agent-facing skill content
- Staging on mcpbundles.com before cutover
- Custom domain, TLS, health checks
- ChatGPT IP allowlist + rate limits
Publish
Directory sprint + docs portal
- Branded / and /docs on your subdomain
- Store submission packs for ChatGPT + Claude
- Widget QA for iframe hosts
- Registry + Cursor plugin filing
- Launch kit for your marketing team
Measure
Growth retainer — optional after launch
- Directory listing health refresh
- Tool-call telemetry by host
- Click-out analytics (no chat content stored)
- Quarterly directory health refresh
- Store policy re-submission support
Your domain — MCP endpoint and docs site, both included
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.
- mcp.yourbrand.com/ — landing, MCP URL, store CTAs
- mcp.yourbrand.com/docs — overview, tools, examples (we build this)
- mcp.yourbrand.com/mcp — streamable HTTP endpoint for all hosts
- Click-outs to www.yourbrand.com for checkout and bookings
Published tiers — USD, sales-led kickoff
Entry engagements start from $5,000 — scope and timeline on a short call. Published full-launch tiers below cover ChatGPT, Claude, and the directory sprint. UK customers may invoice in GBP. Payment: 40% on SOW, 40% on staging UAT, 20% on store submission accepted.
Launch
Timeline: 4–6 weeks
Official MCP on your domain, docs portal, and consumer store submissions — text/JSON results.
- Up to 3 read tools
- mcp.{brand}.com/mcp — MCP endpoint on your subdomain
- mcp.{brand}.com/docs — full docs site we build and host
- ChatGPT Apps + Claude Connectors submission
- cursor.directory + directory sprint core
- 30-day hypercare
Launch + Widget
Timeline: 6–10 weeks
Interactive carousel, fullscreen detail, and click-out straight into your booking flow.
- Everything in Launch
- Up to 5 tools with MCP App UI
- Host compat QA (ChatGPT + Claude)
- MCP Registry + Cursor marketplace plugin
- IP allowlist + security review
Growth
Timeline: After launch
Keep directories healthy, APIs in sync, and telemetry flowing to marketing.
- Directory Coverage Report monthly
- PulseMCP · Smithery · Glama · MCPBundles /skills refresh
- Up to 8 hrs/mo engineering
- Business-hours incident response
Enterprise — From $180,000 / year
Multi-app portfolios, private networking, SLAs, and WebMCP at scale.
- Up to 5 apps or unlimited tools per app
- VPC / private link to customer APIs
- Dedicated PM + quarterly roadmap
- 99.9% SLA and on-call option
- Cross-brand analytics (e.g. comparison group)
Common add-ons
How our pricing compares — indicative anchors
Competitors rarely publish apples-to-apples tiers for brand MCP App launches. These anchors help CFOs sanity-check our published full-launch tiers ($45k–$85k).
| 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 |
MCPBundles vs specialist vendors, in-house, and dev shops
| 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 |
From intake to directory sprint
- 1
Intake + fit check
You submit the request form. We confirm fit, data path, and which directory tiers belong in scope.
- 2
Discovery + tool design
API access, geo/category prompt library, click-out rules, and compliance sign-off.
- 3
Build + staging UAT
MCP server, docs portal, widget if scoped — on staging before custom domain cutover.
- 4
Directory sprint + hypercare
Store submissions, Registry, Cursor, community dirs, /skills — then 30 days launch support.
Frequently asked questions
- Does this replace SEO or Google Business Profile?
- No. Shelf GEO adds the AI app store channel — ChatGPT Apps and Claude Connectors — where people already ask for your category in a place. Keep GBP, content marketing, and Citation GEO on your main site. The strongest programs run both.
- Do you use our brand and domain?
- Yes. The MCP endpoint lives on mcp.yourbrand.com (or your chosen subdomain on your domain). We build and host the docs portal at mcp.yourbrand.com/docs — overview, tool tables, quick starts, privacy, and example queries — not a PDF handover. Store listings appear under your brand name. Click-outs go to your main website with your tracking parameters.
- Do you take payments inside ChatGPT?
- Default is no — we deep-link to your checkout or booking flow so you keep payment relationships and compliance. Write/booking tools are scoped separately with legal review.
- What APIs do we need?
- You need a trustworthy server-side data path — not necessarily a public REST API. Documented search/list endpoints, a partner feed, a web-app backend, or structured site content (CMS, feeds, JSON-LD, sitemap) integrated through our relay all work. That same relay can power WebMCP on www.yourbrand.com and MCP tools on mcp.yourbrand.com that drive the ChatGPT carousel. We run discovery to see which shape fits before SOW.
- We only have a homepage — can we still get a ChatGPT carousel?
- Often yes, if we can build server-side tools from your site, CMS, or feeds via our relay — ChatGPT connects to mcp.yourbrand.com (remote MCP + widget), not WebMCP in the browser, but both surfaces can share one integration. Store review still requires useful live results in chat, so we scope honestly: static brochure sites need more structure (feed, CMS export) before a carousel is viable.
- We do not have an API — can you still help?
- Yes. WebMCP on www.yourbrand.com is one surface; ChatGPT carousel on mcp.yourbrand.com is another — both can call the same MCPBundles relay so you are not blocked on publishing OpenAPI docs first. Pure marketing copy with no structured inventory is still a weak fit for comparison-style carousels until we add a feed or backend.
- How is this different from Smithery or MintMCP?
- Smithery (now part of Arcade.dev) and MintMCP are infrastructure for developers or internal enterprise agents. Managed MCP Apps is an end-to-end brand launch — build, widget, consumer store submission, docs portal, and directory coverage for your customers.
- What is WebMCP and when do we need it?
- WebMCP exposes tools on your main marketing site for Chrome browser agents via document.modelContext — shoppers stay on www.yourbrand.com while agents invoke search, quote, or navigation tools. It complements mcp.yourbrand.com and the app stores. Strong fit when you have a site but no API yet; also an upsell for Enterprise multi-surface coverage.
- What does MCPBundles /skills give us?
- A public skill page on mcpbundles.com/skills/your-brand with SEO metadata, FAQ JSON-LD, and a connect path for developers using our Hub — another directory row agents and Google can find.
- How do we get started?
- Fill out the intake form at mcpbundles.com/business/managed-mcp-apps/request. We reply within one business day with next steps and a scoping call invite.
Ready for a directory launch?
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