Skip to main content

​
What MCPCloud provides

MCPCloud is a managed platform for building, shipping, and operating MCP servers and skills at team scale. It is two products in one workspace:
  • Server factory — paste an API spec and get a typed, deployed MCP server.
  • Skill Studio — author reusable, versioned agent behaviors that run on those servers.
Around both sits a registry/marketplace, a global edge runtime, auth, observability, versioning, and a CLI for CI/CD.

​
From spec to shipped tools

MCPCloud build pipeline: import, generate, deploy

Import a spec, enrich tool descriptions, generate a typed server, and deploy to the edge.

The pipeline is deliberately codegen, not codegen theater: MCPCloud extracts every endpoint as a typed tool, generates a ready-to-deploy server, and pushes it to a global edge runtime — no scaffolding files to maintain, and the generated source stays yours. Once servers exist, you manage them all from one org-level entry point:
MCPCloud Servers hub

The Servers hub — every project-scoped MCP server across the workspace.

​
What you get beyond a self-hosted server

Platform features: transports, auth, static analysis, versioning

The platform stays opinionated where reliability matters.

Edge-native deployment

Generated servers run on a global edge runtime with sub-5ms cold starts, distributed across 300+ locations.

Multi-transport support

Every server ships with Streamable HTTP (default), SSE for legacy clients, and a stdio adapter for local dev.

Auth built-in

API Key, OAuth 2.0, custom headers, and mTLS. Secrets are encrypted and injected at runtime — never in source.

Static analysis on every build

ESLint security rules and Semgrep scan every generated server before deployment. No eval(), no dynamic imports.

Semantic versioning

Publish immutable snapshots. Major bumps flag breaking changes; clients pin to exact versions.

Usage analytics

Track install counts, active usage, error rates, and latency per tool per version in the dashboard.

Trigger-based skill dispatch

Skills carry trigger phrases so agents route to the right behavior without hardcoded mappings.

CLI for CI/CD

mcp deploys from GitHub Actions, lists servers in scripts, and manages keys. Every command supports --json.

​
Why teams use MCPCloud

  • Faster than self-managing infra for every MCP server you ship.
  • Shared governance across engineering and security with audit logs and role-based access.
  • Consistent patterns across many clients and many servers.
  • Portable output — keep the generated source and the deployable bundle.

​
Typical team setup

1

Create projects per product domain

Projects hold servers, skills, members, and settings for a single workspace.
2

Build and deploy servers

Import specs, enrich tools, and deploy to the edge runtime.
3

Issue scoped API keys

One key per client integration or CI pipeline, rotated regularly.
4

Monitor and govern

Watch health, usage, and audit events; publish reusable assets to the registry.
Next: learn the key concepts that the platform is organized around.