Connect Cursor

Cursor connects to the gateway as a remote MCP server — one JSON block, no separate app to install. OAuth runs in the browser the first time your agent calls a tool. Cursor's own pricing page lists MCP support under its paid Individual plans (Pro, Pro+, Ultra), not among the free Hobby tier's features, so if the MCP settings described below are missing, that is the likely reason — check your plan before assuming the config is wrong.

You need an Ansvar account first — the free tier is B2B (business email or VAT number), sign up at pricing. OAuth consent completes in your browser on the first tool call.

Step 1 — add the server

Cursor reads MCP servers from a JSON file at two possible scopes: a project-level .cursor/mcp.json in the repository root (available only in that project), or a global ~/.cursor/mcp.json in your home directory (available in every project you open). Add the gateway to whichever scope fits — global if you want it everywhere, project-level if you're rolling it out to one repo first:

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

The same block works at either path — Cursor's docs describe both locations, with project config taking precedence where the same server is defined in both. Restart Cursor (or reload the window) after editing the file by hand.

Prefer a UI: Cursor Settings → MCP (labelled Tools & MCP in newer builds) → add a new server, and paste the same URL into the URL field. Cursor has renamed and moved this panel before, so the JSON file above is the steadier way in if the menu doesn't match what you see.

Step 2 — authenticate

Cursor discovers the gateway's OAuth support automatically for a server configured with only a url field: on first use it opens a browser at auth.ansvar.eu — approve the login and Cursor is authenticated. There is no client ID or secret to obtain or paste — this is Dynamic Client Registration, the same mechanism the ChatGPT and Gemini connectors use. Cursor's docs also describe a static auth block (CLIENT_ID/CLIENT_SECRET) for servers that don't support automatic discovery; the gateway does, so you don't need it.

Step 3 — verify tools appear

Open the MCP settings panel and confirm ansvar shows a connected status with a tool count, or ask the agent directly: "Which Ansvar tools are available?" — it should list search and the rest of the catalogue your tier includes.

Try a question

In the Agent panel, ask something with a citable answer, for example: "Using Ansvar, what does GDPR Article 33 require for a personal data breach notification, and within what deadline?" A grounded answer names the article and quotes the deadline from the fetched text, not from Cursor's own model memory.

If something breaks

• No MCP settings in Cursor at all. Check your plan — Cursor's own pricing page lists MCP under the paid plans (Pro, Pro+, Ultra), not among the free Hobby tier's features.
• The server doesn't appear after editing mcp.json by hand. A single JSON syntax error drops the whole file silently rather than just the broken entry — validate it, and check whether a project-level file and a global file both define an ansvar entry (the project one wins).
• Tools are missing or the wrong set appears. Tools outside your Ansvar tier are absent by design — see the tool reference.
• Everything else — the general troubleshooting page covers OAuth popups, quota errors, and empty results.