GitHub-first workflow
Ship remote MCP from the workflow
your team already uses.
mcpctl wraps spec checks, deployment, auth, and public /inspect around the repo workflow your team already uses. You write the server. GitHub is the operator surface. mcpctl ships the rest.
The model
Repo in. Trusted MCP URL out.
Connect your repo
Point mcpctl at the GitHub repo that holds your MCP server. No import scripts, no hand-rolled deploy config. mcpctl reads your repo and sets up the delivery pipeline from it.
Review spec, auth, and deploy in a PR
Spec checks, auth wiring, and access controls surface as pull request feedback before anything ships. Your team reviews the full change — code and ops config together — in the workflow they already use.
Merge → trusted remote MCP URL
Merge the PR and mcpctl publishes a remote MCP server URL. Every deployed service automatically gets a public /inspect endpoint so clients and operators can verify exactly what's running.
Why it works
Not a deploy script. A control plane.
Generic hosting gives you a URL. mcpctl gives you a reviewed, governed path from code to running service — with visibility into what shipped and why.
Public /inspect
Every service gets a public /inspect endpoint at merge. No separate step, no manual wiring.
Governed changes
Nothing ships without a PR merge. Auth, spec, and access changes are part of the review cycle.
Tenant-scoped control plane
Your services, your tenant, your API surface. No shared state with other operators.
Deployment history built in
Every merged change produces a versioned deployment record. History is visible from the control plane.
Your repo is already halfway there.
Connect it to mcpctl and ship a trusted remote MCP URL without the ops detour.
Ship from GitHub