Integrations
Every client your team already uses, pointed at one endpoint
One MCP endpoint and one agent token. The clients that take a static header connect in a single command. The ones that insist on OAuth get an authorization server built for their exact checklist. The bindings, the policy and the journal are the same in all of them.
Pick your client
- Claude CodeA static bearer, one command, and the terminal opens your browser when a call needs you.
- claude.aiA custom connector over OAuth, with the two metadata flags the connector actually checks.
- ChatGPTOAuth only, and it works because the authorization server was built for this case first.
- CursorOne JSON file, a static bearer, and the same tool list your terminal agent gets.
- Codex CLIA gated identity for the agent that touches your repositories and your deploys.
- Gemini CLIThe longest documented patience of any client, and the gateway still answers with a link.
- VS CodeCheck the config into the repository. The secret is not in it.
- Claude API MCP connectorYour own product calls the model, the model calls the gateway, and your customer keys stay yours.
- OpenAI ResponsesA remote MCP tool in the Responses API, with the approval card in front of anything that writes.
Running something that is not on this list? Anything that speaks MCP over streamable HTTP works, and anything that can make an HTTP request works through the proxy.
Connect the client you have open right now
One command writes the config, imports the keys you point at, and tells the agent what it may use.
Connect my first agent
Free for 10,000 calls a month. No card.