Zero-DevOps deployment
Push business logic.
mcpctl deploys it.
Connect your GitHub repo and mcpctl auto-deploys whenever you push. You write MCP tools. mcpctl handles deployment, auth, transport, and client compatibility at the edge. No infrastructure to manage.
How it works
Repo in. Hosted MCP layer out.
Connect your repo
Point mcpctl at the GitHub repo that holds your MCP server. mcpctl reads your repo and sets up the auto-deployment pipeline. No import scripts, no hand-rolled infrastructure.
Push your business logic
Write tool logic in your repo using your normal development workflow. When you push to your configured branch, mcpctl picks up the change and deploys automatically — no manual deploy step.
mcpctl deploys and handles the edge
Your server is live with a remote MCP URL. Auth, transport, and client compatibility are handled by mcpctl's hosted layer at the edge — not by your server. Every deployment includes a public /inspect endpoint showing what's running.
Why it works
Not a deploy script. A hosted MCP layer.
Generic hosting gives you a URL. mcpctl gives you auto-deployment from GitHub plus a hosted compatibility layer — auth, transport, client wiring, and /inspect built in.
Auto-deploy on push
Every push to your configured branch triggers an automatic deployment. No manual scripts, no CI/CD pipeline to build and maintain.
Hosted compatibility layer
Auth, transport, and client differences are handled by mcpctl at the edge. Your server never touches client-specific wiring.
Tenant-scoped control plane
Your services, your tenant, your API surface. No shared state with other operators.
Deployment history built in
Every deployment is traceable from /inspect — what version is live, when it was deployed, and what push triggered it.
Your repo is already halfway there.
Connect it to mcpctl and push to deploy. Auth, transport, and client compatibility are handled automatically at the edge.
Connect your repo