Skip to main content
Connect · Claude.ai

Connect Claude.ai to Krexel.

Wire Claude.ai to Krexel in five steps using MCP. Once connected, Claude can list your sites, read files, ship deploys — anything Krexel's API does. No code, no OpenAPI copy-paste.

Open Claude.ai Connectors →See the 9 tools

What you need

  • Claude.ai (free, Pro, Team, or Enterprise) with Connectors enabled. MCP support shipped to all tiers in 2025.
  • A Krexel account with at least one site (free at krexel.com/signup).
  • A Krexel API key — mint one at krexel.com/keys. Use a dedicated key per connector so you can rotate independently.

The five steps

  1. 01

    Open Claude.ai → Settings → Connectors

    In Claude.ai, click your profile picture → Settings → Connectors. Click Add custom connector (or Browse connectors in newer builds).
  2. 02

    Name it "Krexel"

    Give the connector a recognisable name. “Krexel” is fine. The icon and description are optional — Claude uses the name to surface the connector in tool-calling decisions.
  3. 03

    Paste the MCP server URL

    In the Server URL field paste exactly:
    https://api.krexel.com/api/v1/mcp
    Leave the transport selector on Streamable HTTP.
  4. 04

    Add your Krexel API key as Bearer auth

    In the Authentication section choose Bearer. Paste your Krexel key as the token:
    krx_your_key_here

    The bearer token is sent as Authorization: Bearer krx_… on every MCP request. Claude.ai stores it encrypted at rest.

  5. 05

    Verify, then ask Claude to use Krexel

    Save the connector. Claude will run the MCP initialize handshake and surface the 9 Krexel tools. Open any chat and try:
    • “What Krexel sites do I have?”
    • “Show me the last deploy on my homepage site.”
    • “Create a site called blog.”

    Claude will call list_sites / get_deploy / create_site as appropriate, then summarise the result.

What Claude can do once connected

The Krexel MCP server exposes 9 tools. Claude picks the right one from your natural-language request:

  • list_sites — List every site on your Krexel account.
  • get_site — Fetch one site's metadata.
  • list_deploys — Recent deploys for a site.
  • get_deploy — One deploy record + log URL.
  • create_site — Mint a new empty site.
  • trigger_deploy — Re-deploy a site from its current files.
  • get_deploy_logs — Build/runtime log text.
  • list_domains — Custom domains + SSL status.
  • attach_domain — Attach a custom domain to a site.

Troubleshooting

"Could not connect to MCP server" or "Handshake failed"

Confirm the URL is exactly https://api.krexel.com/api/v1/mcp. If you're on a corporate network, confirm api.krexel.com is reachable from your browser (visit api.krexel.com/readyz, should return 200).

"Unauthorized" or "Invalid API key"

Mint a fresh key at krexel.com/keys. Paste it carefully — Claude hides part of the token as you type, so verify the prefix and suffix match what's on the keys page. If the key works in the dashboard but fails in Claude, your org may have IP-allowlisted the worker's egress.

"Tools listed but not actually called"

Some Claude.ai builds surface the tools in the connector settings panel but don't invoke them in regular chats unless you explicitly mention Krexel. Try “Use Krexel to list my sites.” The word Krexel is the connector name Claude uses to match.

Your key stays yours

Claude stores the bearer token encrypted. Revoke any time from krexel.com/keys — the worker's auth check rejects the old key instantly.

Same tool set across clients

ChatGPT, Cursor, Windsurf, VS Code, and Claude Code all hit the same MCP endpoint with their own bearer tokens. One tool catalogue.

Stateless transport

Streamable HTTP, no WebSocket. Each Claude turn is one request/response to api.krexel.com/api/v1/mcp.

Ready to wire it up?

Five steps. About two minutes. Claude can ship your sites by the time your coffee's ready.

Open Claude.ai Connectors →Same setup for ChatGPT →