Source: https://method.chakril.site/docs/client-compatibility

**Documentation** [Host an existing MCP](https://method.chakril.site/docs/host-existing-mcp) [Client compatibility](https://method.chakril.site/docs/client-compatibility) [Agent-assisted setup](https://method.chakril.site/docs/agent-onboarding) [Quickstart](https://method.chakril.site/docs/quickstart) [Authentication](https://method.chakril.site/docs/authentication) [Deployment lifecycle](https://method.chakril.site/docs/deployment-lifecycle)

Guide

# Client compatibility

Check transport, authentication and upstream access independently before connecting a client.

## The supported contract

Current hosted endpoints use HTTPS /mcp, Streamable HTTP with JSON responses and scoped bearer API keys. Configure the endpoint and Authorization header in a compatible client. Run initialization and tools/list before a real tool call.

## What is not supported

Legacy /sse endpoints, long-lived event streams and end-user MCP OAuth are not supported by the current gateway. OAuth-only clients need a completed, tested OAuth implementation; signing into the MCP Ops website is not that implementation.

## API integrations are not directory approval

OpenAI and xAI document remote MCP support in their developer APIs. That is not evidence of automatic signup inside ChatGPT or Grok, acceptance into a directory, or verified end-to-end compatibility with this service. Test the exact client and auth settings before distribution.

## Keep upstream authorization separate

The MCP Ops consumer key controls access to a hosted endpoint. It does not by itself give each consumer a separate Basecamp or other upstream account. Enforce tenant and object permissions in the MCP and upstream system.

Ready to put this into practice? [Open MCP Ops](https://method.chakril.site/login)