Connect an AI client over MCP

Connect claude.ai, Claude Code, Cursor, or ChatGPT to WEXTL over the Model Context Protocol so an assistant can create, run, and inspect your workflows.

Endpoint

Every organization gets a single regional MCP endpoint, scoped to its data-plane region. Pick your region with the control at the top of this page — samples update to match. Pattern: `https://<shard>.wextl.com/api/mcp`. Requests are authenticated the same way as the REST API — see Authentication.

text

https://eu1.wextl.com/api/mcp

PAT vs. OAuth — which to use

Two ways to authenticate an MCP connection:

Personal Access Token (PAT) — fastest to set up; paste a token into a client that supports bearer-token MCP connections (Claude Code, Cursor).
OAuth 2.1 — required for the hosted claude.ai and ChatGPT custom connectors, which drive an interactive consent flow (org + scope picker) rather than accepting a pasted token.

claude.ai custom connector

Add WEXTL as a custom connector from claude.ai's connector settings using the MCP endpoint above. You'll be redirected through the OAuth consent screen to pick an organization and approve the scopes the connector requests.

Claude Code

bash

claude mcp add wextl --url https://eu1.wextl.com/api/mcp --header "Authorization: Bearer wextl_..."

Cursor

Add the same endpoint + bearer token to Cursor's MCP settings (mcp.json) as a remote server entry.

json

{
  "mcpServers": {
    "wextl": {
      "url": "https://eu1.wextl.com/api/mcp",
      "headers": { "Authorization": "Bearer wextl_..." }
    }
  }
}

ChatGPT connector

Add WEXTL from ChatGPT's connector settings using the MCP endpoint. Like claude.ai, this drives the OAuth consent flow — no pasted token.

Connecting more than one organization

A key or OAuth grant is scoped to exactly one organization and one regional endpoint. If you work across multiple organizations, add one connection per organization — each shows up as a separate MCP server entry in your client.