Ansvar AI docs
ansvar.eu →

Connect ChatGPT

ChatGPT connects to the gateway as a custom connector with Developer mode switched on: paste one URL, approve one browser login, and the tool catalogue appears. It works on every paid plan — Plus, Pro, Business (the plan formerly called Team), Enterprise, and Edu; the Free tier cannot add custom connectors. Two naming notes so the menus match what you read here: OpenAI renamed "Connectors" to Apps in late 2025, and both labels still appear in the product.

Step 1 — turn on Developer mode

Settings → Apps (or "Apps & Connectors") → Advanced settings → toggle Developer mode.

Developer mode is what gives ChatGPT full MCP support. Without it, custom connectors are restricted to tools literally named search and fetch — the deep-research interface — and the gateway's real surface (get_provision, validate_citation, list_coverage, the workflow tools on Team and Company) would be invisible. With Developer mode on, ChatGPT can call every tool your Ansvar tier includes, and asks you for confirmation before consequential actions by default.

Step 2 — create the connector

Settings → Connectors → Create, then fill in:

Name:            Ansvar
Description:     EU law, regulation, and standards — cited answers
MCP server URL:  https://gateway.ansvar.eu/mcp
Authentication:  OAuth

There is no client ID or secret to obtain — ChatGPT registers itself with the gateway's login service automatically on save. If the form shows a Client ID field as required, leave it empty and submit anyway; that field is a known cosmetic quirk of the connector form. The browser opens for the OAuth login at auth.ansvar.eu; approve it, and ChatGPT lists the tools your tier includes. A connector added on the web is available in the ChatGPT mobile apps automatically.

Verify: ask "Which Ansvar tools are available?" — ChatGPT should enumerate the catalogue, starting with search.

Rolling out to Business or Enterprise

On Business (formerly Team), only workspace admins and owners can enable Developer mode, and each admin enables it for themselves — the toggle is not workspace-wide. On Enterprise and Edu, apps are off by default: an admin enables them, grants Developer mode to named members via Workspace Settings → Permissions & Roles, and can scope per-app access with role-based access control.

Two things your admin will want to know. First, OpenAI does not review custom connectors — the console tells admins to add one only if they know and trust the developer, which for the gateway means us: EU-hosted, licensing-audited, no training on your data. Second, ChatGPT's default per-app permission level ("Important actions") auto-approves reads but asks before actions with external effect — the gateway's tools are read-only research and workflow calls against your own tenant, so the prompts you see will be proportionate.

Codex CLI

OpenAI's coding agent connects in two commands:

codex mcp add ansvar --url https://gateway.ansvar.eu/mcp
codex mcp login ansvar

Codex detects the gateway's OAuth support, registers itself automatically, and opens the browser login — we verified this discovery flow against the live gateway with codex-cli 0.142.5 on 2026-07-02. Tokens are stored by Codex, not written into config.toml. For CI or containers with no browser, codex mcp add ansvar --url … --bearer-token-env-var ANSVAR_TOKEN takes a static credential instead — that path needs a managed service credential, since gateway tokens expire in minutes (see Clients without OAuth).

Building on the OpenAI API

The Responses API and Agents SDK attach remote MCP servers with a static bearer token — neither runs the OAuth flow for you, and the Responses API discards the credential after every request, so your application must resupply a live token each call:

response = client.responses.create(
    model="gpt-5.5",
    input="What does DORA require for ICT incident classification?",
    tools=[{
        "type": "mcp",
        "server_label": "ansvar",
        "server_url": "https://gateway.ansvar.eu/mcp",
        "authorization": ansvar_access_token,  # your app obtains + refreshes this
        "allowed_tools": ["search", "get_provision"],
    }],
)

Because gateway tokens are short-lived by design, headless setups should use a managed service credential rather than a pasted token — the same shape as n8n or CI. See Clients without OAuth.

If something breaks

  • The connector connected once, then authentication fails and re-linking doesn't help. ChatGPT has a known issue with published workspace connectors: it pins the original client registration and won't re-register if that client is ever invalidated. Deleting and recreating the connector fixes it.
  • Tools are missing. Check Developer mode is on (without it you'll see at most a crippled two-tool view), then check your Ansvar tier — tools outside it are absent by design (see the tool reference).
  • Everything else — the general troubleshooting page covers OAuth popups, quota errors, and empty results.