Repo in.
MCP out.

Point mcpctl at your MCP GitHub repo. Get a compliant MCP server URL that works across clients.

Built for developers shipping real MCP services

GitHub-first
Repo-native workflow
Spec-compliant
Compliant MCP server
Secure
API-key, OAuth
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

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 ships a compliant MCP server URL from your repo.

Works across clients. Stays on spec.

No boilerplate auth grind, no client-by-client debugging, no manual spec catch-up. mcpctl keeps the server deployable and compliant for you.

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

MCP without the yak shave

Eliminate the ops toil. Git push, done.

🔁

GitHub-first delivery

Preview in PRs. Ship from repo.

🧭

CLI or MCP

Run ops where you work.

🛡️

Secure by default

Automatic scans, built-in identity, and fine-grained access keep every MCP and skill secure before approval.

🔎

Controlled rollouts

Gate releases with preview and rollback built in.

🌐

Any MCP, anywhere

Use local MCPs or hosted ones without changing how your team works.

⚙️

Lean context

Cut token bloat from tool calls and retrievals.

No more MCP side quests.

Less hidden machinery. Less ops glue. More shipping.

Built for teams that want MCP delivery to feel like software delivery.