Global edge runtime
Generated servers run on a global edge runtime with sub-5ms cold starts and automatic distribution across 300+ locations worldwide.
{ Spec, GraphQL, or just your repo }
Paste a spec — or point MCPCloud at a repo that hasn’t got one. Every endpoint becomes a typed tool with a description Claude rewrote for agents, deployed to a global edge runtime with auth, secrets, and observability already wired.
Spec to first live deployment.
OpenAPI, GraphQL, or a repo with no spec at all.
No scaffolding, no config files to maintain.
tally-mcp
Live
21 tools · global edge
$ claude mcp add tally --transport http \
https://tally.mcp.mcpcloud-demo.com/mcp
$ claude mcp add tally \
--transport http \
https://tally.mcp.mcpcloud-demo.com/mcp
✓ Connected — 21 tools available
confirm_payment_intent
Enriched+ 20 more rewritten for agents
{ How it works }
Paste a spec. MCPCloud extracts every endpoint as a typed tool, generates a ready-to-deploy MCP server, and pushes it to a global edge runtime — no scaffolding, no config files.
Confirm Payment Intent
Confirm a payment intent to process the associated payment. This operation finalizes a payment intent that was previously created, optionally binding it to a specific payment method. Once confirmed, the payment will be charged against the customer’s account. This is a critical operation in the payment workflow and should only be called when you are ready to commit the transaction.
Tally is a real MCP server, built on MCPCloud end to end. That run wasn't a mockup — here's the live deployment.
Next · Push v1.1 → drift detection diffs the added /disputes group.
Point Spec Studio at your repository. It inventories your routes, infers a reviewed OpenAPI spec per endpoint — confidence-annotated, verified against your live API — and hands you a spec you keep. Then it becomes an MCP server on the platform: policy proxy, keys, observability, distribution.
Convex · FastAPI · Express · NestJS · anything (LLM fallback) — scanning is free, generation ≈ 1 credit per route, and the spec is yours either way.
$ mcpcloud spec scan acme/api@main
inventoried 121 routes · adapter: convex · free
$ mcpcloud spec generate --all
✓ 118 generated · 3 to review · 2m 41s
✓ verified against the live API · 34 endpoints matched
$ mcpcloud server create --from-spec
● acme-api.mcp.acme.dev — live, policy-fronted, observable
We pointed MCPCloud at the published Stripe and GitHub OpenAPI specs, curated a useful subset, and shipped both. Toggle between them below — every call hits the real upstream through the deployed MCP server.
A skill is a reusable, versioned agent behavior package. Skill Studio is a visual composition canvas: pick MCP server dependencies, drop step nodes onto the graph, and wire success and fallback edges. The canvas compiles into a structured package with triggers, guardrails, and an editable SKILL.md.
Workflow topology
Success edges follow step order. Dashed edges show fallback.
Entry
linear · on_issue_closed
validate_lead
validator
enrich_company
enrichment-mcp
update_deal
crm-mcp
Generated skill package
Meeting Notes → Action Items
Trigger phrases
Dependencies
Guardrails
3 stop conditions ship inside the package — written into SKILL.md and versioned with it, not left as comments in a prompt.
Read the skill formatGeneration gets a server to live. The platform keeps it there — deployment, auth, rate limits, secret injection, versioning, and observability, opinionated where reliability matters.
Generated servers run on a global edge runtime with sub-5ms cold starts and automatic distribution across 300+ locations worldwide.
API Key, OAuth 2.0, and custom headers — all supported. Secrets are encrypted and injected at runtime, never in source.
Track install counts, active usage, error rates, and latency per tool per version — directly in the dashboard.
Streamable HTTP by default, SSE for legacy clients, stdio for local development.
Major bumps flag breaking changes, clients pin exact versions, and any deploy rolls back in one click.
Deploy from GitHub Actions and script everything — every command supports --json.
Publish once, install anywhere. The registry handles versioning, discovery, and dependency-aware activation — so you can focus on building.
Live registry
Real public listings on MCPCloud right now — every card opens the actual marketplace page.
MCPCloud ships as an MCP server on its own marketplace — the official MCPCloud listing plus five official skills. Connect Claude, Cursor, or any MCP client with one approval: a scoped key is minted and custodied server-side, every destructive action stays guarded, and everything runs in your workspace under your role.
Zero-paste connect · revocable any time · the official server is write-locked, so an agent can never modify the thing it speaks through.
$ mcp connect-agent
✓ connected — key custodied, agent never sees it
claude mcp add mcpcloud --transport http https://…/mcp
$ “ship an MCP server for our payments API”
● spec ingested · descriptions enriched · tests 12/12
deploy is guarded — your agent asks before going live
{ Pricing }
Start free, move into hosted billing, and scale into governed collaborative access.
A credit is $0.10 — about one generated tool. Running them costs far less: 0.15 credits per 1,000 tool calls. A 20-endpoint API is roughly 20 credits to build, then pennies to keep serving.
Individual builders
Test the full platform end-to-end with 30 included credits — no card required.
{ Includes }
No credit card required
Choose FreeSmall teams
Private registry, shared projects, and seat-based pricing for shipping real agents.
{ Includes }
Ship faster with shared workspaces
Choose ProRegulated orgs
Dedicated infrastructure, self-hosted export, and governance for compliance and scale.
{ Includes }
On the roadmap — SAML SSO.
Custom rollout — tell us what you need
Talk to usMarketplace creators keep 75% of revenue once paid listings launch. Contact us for enterprise rollout support.
{ Ready to ship? }
Start free, keep the generated source, and go from imported spec to a live deployment in one pass.