No tracking. No cookie wall.·100 % EU-hosted on Hetzner
Setup

Connect Ansvar AI to your AI client

Pick your client. Paste a URL. Sign in once. Your client now sees the gateway as a tool.

Gateway essentials

Three things every client needs

Server URLhttps://gateway.ansvar.eu/mcp
AuthOAuth 2.1 with Dynamic Client Registration (PKCE). The client opens a browser once, you sign in, the client stores the token and refreshes silently after that.
Tier visibilitytools/list is filtered by tier. Free covers single-source search (100 searches/day); Premium adds multi-source fan-out plus case law, preparatory works, and agency guidance; Team adds workflow plus upload tools; Company adds the audit ledger. See pricing.
Designed forMCP-native AI clients (Claude, ChatGPT, Cursor, VS Code Copilot), Copilot Studio agents, and custom MCP clients your team builds. MCP (Model Context Protocol) is the open standard that lets AI assistants call external tools.
Tier-1 walkthroughs

Step-by-step for the four most-used clients

Claude (web + Desktop) via Connectors
Prerequisites. Claude.ai Pro / Team / Enterprise (web), or Claude Desktop with Connectors enabled. Any Ansvar account works — Free is enough to evaluate (single-source answers, 100 searches/day); Premium unlocks multi-source fan-out plus case law, preparatory works, and agency guidance.
Settings → Connectors → Add custom connector
Name: Ansvar
URL: https://gateway.ansvar.eu/mcp
OAuth. After saving, Claude opens a browser for OAuth sign-in at auth.ansvar.eu. Approve the consent screen. The connector flips to Connected; tokens refresh silently after that.
Verify. Ask Claude: "Do you see Ansvar tools available?" Expected: Claude lists ansvar.search and the other tools your tier includes.
Claude (web + Desktop) via Connectors showing Ansvar tools
Claude Code
Prerequisites. Claude Code CLI installed (`npm i -g @anthropic-ai/claude-code`), an Ansvar account (any tier)
Run in your project root
claude mcp add --transport http ansvar https://gateway.ansvar.eu/mcp
OAuth. The --transport http flag is required — without it the CLI defaults to stdio. After adding the server, start Claude (claude), type /mcp, select "Ansvar MCP Server", choose Authenticate. A browser opens for OAuth at auth.ansvar.eu; approve and return to the terminal. The token is stored in ~/.claude.json.
Verify. In the /mcp menu, the Ansvar MCP Server status should read "connected" with Auth: authenticated. Expected: Tools become available in the next message — try: "List the Ansvar tools you can call."
Claude Code showing Ansvar tools
VS Code (GitHub Copilot agents mode)
Prerequisites. VS Code 1.92+, GitHub Copilot agents mode enabled, an Ansvar account (any tier)
Create or edit .vscode/mcp.json
{
  "servers": {
    "ansvar": {
      "url": "https://gateway.ansvar.eu/mcp"
    }
  }
}
OAuth. Trigger a Copilot agent action that touches an MCP server. VS Code opens the OAuth flow on first use.
Verify. In Copilot Chat (agents mode): "What MCP tools do I have?" Expected: Copilot enumerates the Ansvar tool catalogue.
VS Code (GitHub Copilot agents mode) showing Ansvar tools
Cursor
Prerequisites. Cursor 0.42+, an Ansvar account (any tier)
Settings → MCP → Add Server
Name: ansvar
URL: https://gateway.ansvar.eu/mcp
OAuth. Cursor opens the OAuth flow when you save the server entry.
Verify. In Composer or Chat: "List tools registered under ansvar." Expected: Cursor shows the tool list inline.
Cursor showing Ansvar tools
Tier-2 quick configs

Other MCP-capable clients

ChatGPT (custom connectors)

Prereq. ChatGPT Plus / Team / Enterprise with custom connectors enabled

Where. Settings → Connectors → Add MCP server

URL: https://gateway.ansvar.eu/mcp

Auth. OAuth dance opens in a popup on first call.

Verify. Ask: "Which Ansvar tools are available?"

Continue

Prereq. Continue extension installed in your IDE

Where. config.json → mcpServers

{
  "ansvar": { "url": "https://gateway.ansvar.eu/mcp" }
}

Auth. Browser-based OAuth on first use.

Verify. Ask the agent to list its MCP tools.

Open WebUI

Prereq. Self-hosted Open WebUI 0.5+ with MCP support enabled

Where. Admin → Tools → Add MCP server

https://gateway.ansvar.eu/mcp

Auth. OAuth via browser; token stored per user.

Verify. Trigger a workflow and inspect the tool-call panel.

Custom MCP client (stdio / HTTP)

Prereq. Any client implementing the MCP spec

Where. Wherever your client registers MCP servers

Endpoint: https://gateway.ansvar.eu/mcp
Transport: streamable-http
Auth: OAuth 2.1 + Dynamic Client Registration (PKCE)

Auth. Discovery via /.well-known/oauth-authorization-server.

Verify. Call tools/list and confirm the catalogue is non-empty.

Microsoft Copilot Studio

Publish an Ansvar-backed agent to your tenant

Build a Copilot Studio agent that calls Ansvar through the gateway, then publish to Teams, web, or M365 Chat. Same citation contract, M365 native UX. The walkthrough has its own page because it has more steps than every other client combined.

Open the Copilot Studio guide →
My client isn't here

Tell us which one

The clients below are reachable via the gateway in principle but not yet documented end-to-end. Email us and we will add the walkthrough.

  • GeminiMCP support not yet verified by Ansvar
  • Microsoft Copilot for M365Different surface from Copilot Studio — not yet documented
  • ZedMCP support landing — walkthrough not yet captured
Trouble?

Triage the three most common problems

The OAuth window did not open

Your client may be blocking popups, or the OAuth redirect URI may be unreachable from your network. Check your firewall allows outbound HTTPS to auth.ansvar.eu.

Tools do not appear in my client

Restart the client after editing config. Most MCP clients only re-read config on launch. If tools are still missing, check the client's MCP-server status panel for an error.

401 unauthorized

Your token expired or the OAuth flow did not complete. Sign out of the client and reconnect; the token will be refreshed.

Now that you are connected

Ask your first cross-jurisdiction question — every answer comes back with sources.

See tiers →