Client compatibility
Ship once across the MCP clients
your users actually use.
MCP clients differ in auth, transport, and capability support. mcpctl helps you validate and communicate what works where — so you reduce client-specific surprises before they reach your users.
The reality
Not every client is the same.
An MCP server that works perfectly in Claude may behave differently in Cursor or Windsurf. Auth flows, transport assumptions, and supported capabilities vary — and those differences don't show up until a user hits them.
One ship, validated everywhere
Deploy once from your GitHub repo. mcpctl tells you which clients your service is validated against — no separate per-client deploy cycles.
Fewer client-specific surprises
Auth schemes, transport assumptions, and capability surface vary across clients. mcpctl surfaces those differences so you can handle them proactively.
Honest about what's not supported
We say 'supported clients', not 'all clients'. The compatibility table is accurate, not aspirational — and /inspect shows live validation evidence.
Supported clients
Validated, not aspirational.
This table reflects current validation status. Client support varies by feature, auth, and transport — not all capabilities are equally validated across every client.
Status key: Validated — confirmed working end-to-end. Targeted — auth and transport confirmed; full feature parity in progress. In progress — under active testing. Client support varies by feature, auth scheme, and transport. Check /inspect for live validation evidence on your deployed service.
Ship once. Know where it works.
mcpctl validates your service against supported clients and surfaces the differences — so you can ship with confidence instead of finding out from users.
Ship Now