hosted compatibility layer

Intelligent Edge.
Zero Client Chaos.

mcpctl hosts the auth, transport, and client compatibility layer at the edge. Claude, Cursor, Windsurf — each client sees the interface it expects. You write tools. mcpctl handles the rest.

Start for freeSee how it works

Connect your repo. Free to start. Built for developers who want to ship tools, not manage infrastructure.

server.tsTypeScript runtimeGitHub repo
1// my mcp server code
2const server = { name: 'docs-assistant' }
3server.tool('search_docs', (query) => searchDocs({ query }))
4export default server
server.pyPython runtimeGitHub repo
1# my mcp server code
2server = {"name": "docs-assistant"}
3def search_docs(query):
4 return search_docs_index(query)

mcpctl edge layer

One clean server surface in. Validated client surfaces out.

Auth adaptationTransport shapingContext optimizationClient compatibility + governance

validated across supported clients

Claude logo

Claude

OAuth 2.0

Validated
Cursor logo

Cursor

API key

Validated
Windsurf logo

Windsurf

API key

Validated
Cline logo

Cline

API key

Validated

How it works

Client chaos is not a feature.

Neither is deployment toil. Connect your repo. mcpctl handles the rest.

Deploy

Deployment toil is not the product.

Connect your repo. mcpctl handles deploys, routing, SSL, and scale so you can ship the tool, not the plumbing.

Compat

Client chaos is not your problem.

Auth, transport, and client quirks live in mcpctl's edge layer. Your server stays clean. Clients get what they expect.

Inspect

Guesswork is not observability.

Every deployment gets /inspect, so the live tool surface, version, and client support are visible without digging.

Hosted at the edge

Hosted upstream. Clean downstream.

mcpctl hosts the edge layer that absorbs client differences before they hit your server.

Fig. 1 — Traffic flows through mcpctl Endpoints & Policy
mcp clients
initialize
tools/list
tools/call · search_docs
resources/read

Claude · Cursor · Inspector

mcpctl
mcpctl control plane
https://docs-assistant.mcp.mcpctl.io
Auth · OAuth 2.1
Rate Limit · 60/min
Tool Policy · allow search_docs
Compat Layer · SSE ↔ streaming-http
Inspect · capture trace
Forward → docs-assistant
server.ts · TypeScript runtime
cold-start warm
server.py · Python runtime
concurrency 1
your mcp servers
docs-assistant
billing-tools
crm-lookup

GitHub · deploys from push

activeblocks requestconfigured

What mcpctl kills

Zero yak shave. Zero client drama.

Shipping an MCP service usually means burning time on deployment glue and per-client compatibility hacks. mcpctl takes both off your plate so your team stays on product work.

🛡️

Skip the protocol yak shave

OAuth flows, API key validation, and transport negotiation run in mcpctl's layer. Your server exposes tools. mcpctl handles the auth and transport surface.

🔁

Push code. Skip ops.

Connect your GitHub repo and mcpctl auto-deploys on every push. No container orchestration, SSL, routing, or scaling detour before users can hit your tools.

Learn more →
📋

Your tenant. Your blast radius.

Your services, your tenant, your API surface. Scoped access tokens support CI/CD and automation without bleeding state across operators.

Scope

What mcpctl owns. What stays in your server.

mcpctl removes deployment toil and MCP compatibility overhead. Your server owns tool logic and business data. mcpctl handles the rest at the edge — deployment, auth, transport, and client wiring.

mcpctl owns

  • Deployment and container orchestration
  • Auth registration and OAuth wiring
  • Transport and session compliance
  • Client-specific compatibility at the edge
  • Public /inspect trust surface
  • Tenant-scoped access controls

Stays in your server

  • Tool definitions and business logic
  • Data access and API integrations
  • Response formatting and model behavior
  • Domain-specific error handling
  • Application context window strategy

mcpctl does not fix bugs inside your tool logic or replace framework debugging. It removes deployment toil and MCP compatibility overhead so your team can focus on tools.

Push business logic. mcpctl handles the rest.

Connect your GitHub repo and mcpctl auto-deploys on every push — with auth, transport, and client compatibility handled at the edge. No DevOps. No compatibility toil.

Start for free

Connect your repo first. Free to start.