GitHub-first control plane

Ship trusted remote MCP
from GitHub.

Build, review, and ship remote MCP services from the repo workflow your team already uses — with spec-safe delivery, public /inspect, and a control plane built for real operations.

Ship from GitHubSee how it works

Built for developers shipping real MCP services

GitHub-native
Repo → PR → merge
/inspect
Public by default
Tenant-scoped
Your control plane
server.tsTypeScript runtime
1// my mcp server code
2const server = { name: 'docs-assistant' }
3server.tool('search_docs', (query) => searchDocs({ query }))
4export default server
server.pyPython runtime
1# my mcp server code
2server = {"name": "docs-assistant"}
3def search_docs(query):
4 return search_docs_index(query)

Step 1

Your GitHub Repo

↓

Step 2

Check spec compliance

↓
↑

back to your code

mcp-svr.mcpctl.io

↑

Step 4

Review and merge

←

Step 3

Generate pull request

GitHub-first

Build, Review & Ship from GitHub

mcpctl wraps spec compliance, security, and deployment around the repo workflow your team already uses, so your MCP server ships through pull requests instead of platform guesswork.

Build

Build in GitHub

Build, version, and ship your MCP server right from GitHub.

Review

Review in GitHub

Spec, auth, and deploy changes flow through a pull request before merge.

Ship

Ship from GitHub

Merge the PR and mcpctl publishes a remote MCP server URL with public /inspect — no manual deploy step.

Works across supported clients

Ship once. Validate where it works.

MCP clients differ in auth, transport, and capability support. mcpctl helps you understand and manage those differences from one control plane — without chasing spec changes or debugging client-by-client by hand.

Claude logo

Agent / Client

Claude

Cursor logo

Agent / Client

Cursor

Windsurf logo

Agent / Client

Windsurf

Cline logo

Agent / Client

Cline

mcpctl

GitHub-native MCP delivery

MCP spec-first

Security

Observability

Governance

Why mcpctl

Trusted delivery, not manual assembly

Skip the second ops stack. Ship MCP services through a governed path from day one.

🔁

GitHub-first delivery

Repo → PR → live remote MCP URL. Your ship path runs through pull requests, not manual deploy scripts.

Learn more →
🔎

Public /inspect

Every deployed service exposes a public /inspect endpoint. Clients and operators can verify what's running — no console access needed.

Learn more →
🛡️

Secure by default

Spec checks, auth wiring, and access controls run before anything ships — not as a post-deploy afterthought.

📋

Tenant-scoped control plane

Your MCP services live in your tenant. Scoped API tokens for automation. No shared state with other operators.

🌐

Works across supported clients

Ship once and validate what works where. Manage client differences from one control plane instead of chasing them per integration.

Learn more →
⚙️

Lean context

Scope what tools a server exposes. Keep context focused and overhead low as your toolset grows.

Learn more →

Ship remote MCP like software, not like a side project.

Connect your repo and mcpctl handles the deploy, auth, and review path — so you ship a trusted remote MCP URL without the ops detour.

Ship Now

Built for developers shipping real MCP services.