Connect your AI to Krexel.
Pick your AI client. Each path has a step-by-step guide. All paths use the same Krexel MCP server, same bearer-token auth, same 9 tools.
ChatGPT (Apps SDK / OAuth 2.1)
The native ChatGPT connector is in development. Until it ships, ChatGPT customers should use the legacy Custom GPT (OpenAPI) path or install the local stdio MCP in Codex — both link to the same Krexel APIs.
Claude.ai (web)
Claude.ai's custom connector. Add the URL, paste a Bearer token, Claude picks up Krexel's tools.
Claude Code, Cursor, Windsurf, VS Code
Install the npm package and point your client at the krexel-mcp binary. Best for local development — your AI sees the file tree directly.
ChatGPT Custom GPT (OpenAPI Actions)
The pre-MCP path. Still works for per-workspace pinned installs but most users should switch to the MCP-native path above.
What stays the same
Every connect path talks to the same backend. The differences are only transport (HTTP vs stdio) and how the client surfaces the tools.
One auth scheme
Bearer token. Same Krexel API key works in every client. Mint or revoke at krexel.com/keys.
One tool set
9 tools: list_sites, get_site, list_deploys, get_deploy, create_site, trigger_deploy, get_deploy_logs, list_domains, attach_domain.
One server
Streamable HTTP MCP at api.krexel.com/api/v1/mcp — stateless, no WebSocket, every request is a single round-trip.
About Krexel API keys
Every connect path authenticates with a Krexel API key prefixed krx_. The key maps to your account via the same Postgres-backed table the dashboard uses. Mint a dedicated key per connector so you can rotate independently if any one leaks.
The Krexel MCP server runs on Cloudflare Workers and validates every request through the same bcrypt-hashed key check as the dashboard. Free plan = 50ms CPU/request budget; Paid plan = 30s. If you hit rate-limit errors, switch to the stdio path (uses the same npm package, hits the same worker) and the client-side call is the same.