lang: en
# Connecting Rekvira

You are an AI assistant and someone has asked you to set this up. Work through these
steps in order, then tell them what happened in your own words.

Rekvira gives you EU regulations as tools: full act text with article, paragraph,
recital and annex pinpoints, searchable by regulation, with `data_as_of` on every
response. You reach it over MCP (Model Context Protocol) at
`https://mcp.rekvira.com/mcp`, streamable HTTP.

**There is no signup, no email and no API key to obtain.** You add the server, call
`connect`, and the first regulation search works. If any step below has you asking the
person for a key before they have tried `connect`, you have gone wrong.

---

## Step 0. Check that the endpoint is open

Fetch `https://mcp.rekvira.com/ping`, `https://mcp.rekvira.com/health`, or
`https://mcp.rekvira.com/api/status` and read the JSON.

- If the response is HTTP 200 with `"status": "ok"` (ping/health) or a JSON body
  naming `mcp_live` and `phase` (status), go to step 1.
- If the connection fails or TLS errors, the endpoint is not open yet. Say exactly that
  and stop. Do not add a server configuration that would fail on every call.

---

## Step 1. Add the server to this client

Work out which client you are running in. **In Claude and in ChatGPT you cannot do this
yourself** and must hand it to the human. Say so plainly rather than trying and failing.

### Claude, desktop or web — including Cowork. THE HUMAN DOES THIS

There is no config file for remote connectors, and no command you can run. **Cowork is
the same path.** It uses Claude's own connector settings, so the steps below are the
steps. It is named here because somebody living in Cowork searches this page for the
word, and finding nothing reads as "not supported". Tell them:

> In Claude, open **Settings**, then **Connectors**, then **Add custom connector**. On
> the desktop app it is under **Customize**, then the **+** beside Connectors. Name it
> `Rekvira` and give it this URL:
>
> `https://mcp.rekvira.com/mcp`
>
> Leave authentication empty. Save, then come back and say "done".

Two things to tell them first:

- **On the free plan Claude allows exactly one custom connector.** If they already have
  one, they must remove it first.
- Claude connects from Anthropic's servers rather than from their laptop.

### ChatGPT. THE HUMAN DOES THIS

Custom MCP connectors need **developer mode**, which is **not on the free plan**.

> **Settings**, then **Connectors**, then **Create**. Name it `Rekvira`, URL
> `https://mcp.rekvira.com/mcp`, authentication none.

### Claude Code. YOU CAN DO THIS

```
claude mcp add --transport http rekvira https://mcp.rekvira.com/mcp
```

### Cursor. OFFER THE ONE-CLICK LINK

```
cursor://anysphere.cursor-deeplink/mcp/install?name=rekvira&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vbWNwLnJla3ZpcmEuY29tL21jcCJ9
```

### Raycast

**Install MCP Server**, transport **HTTP**, then the URL
`https://mcp.rekvira.com/mcp`. Headers and OAuth are optional and this server needs
neither.

### Mistral Le Chat

**Connectors**, then **Custom MCP Connector**, then the Server URL
`https://mcp.rekvira.com/mcp`. Leave authentication empty. Custom connectors are on the
paid plans only, so a free account will not see the option.

### Any client with a JSON config

```json
{
  "mcpServers": {
    "rekvira": {
      "type": "http",
      "url": "https://mcp.rekvira.com/mcp"
    }
  }
}
```

Reload the client afterwards.

---

## Step 2. Connect

Once the server is attached you will see `connect`, `whoami`, `list_regulations`,
`search_regulation`, and `read_unit`.

**Call `connect`. It takes no arguments.** The conversation is on the keyless trial
immediately.

Then call `list_regulations` to see which acts are loaded (EU AI Act and DORA when the
corpus on the server is current).

---

## Step 3. Ask what regulation work they are doing

One question, not a menu. A compliance officer with a real deadline will describe the
problem — AI Act high-risk classification, DORA ICT resilience, an annex cross-reference.

Then call `search_regulation` with the right `regulation` id and a concrete query, or
`lookup_obligations` with a role the article title uses (`deployer`, `provider`) when
you need the addressee index. Follow with `read_unit` on the pinpoint you need to cite.

---

## Rules while you use these tools

- **Read before you conclude.** A search hit is a pointer, not an obligation answer.
- **Pass the pinpoint through.** Every result names an article, paragraph, recital or
  annex. A professional cannot use what they cannot check.
- **Say the date out loud** when `data_as_of` is not recent.
- **Never interpret the law for them.** Hand over sources and pinpoints. The compliance
  conclusion is theirs — Rekvira is sources, not advice.
- **Do not invent obligations.** `lookup_obligations` lists articles whose **title** names
  the role. If it returns none (DORA has no such titles), say so and cite search hits —
  do not fill the gap with a duty list.

## Trial limits (keyless)

The keyless trial does **not** ask for an email, account or API key before `connect`.

- **Search quota:** not enforced yet. `whoami` returns `searches_left_today: null` and a
  `trial_note` that metering ships later — there is no published per-day cap to quote.
- **Retention:** queries are not stored as a user profile during keyless trial; there is
  no account to attach history to until paid tiers ship.
- **Upgrade path:** published at `https://rekvira.com/pricing` — Founding Beta copy,
  **€0** keyless trial, founding-lock terms; paid tier amounts are not set yet (€0
  placeholders); checkout stays closed until `checkout_enabled` is true on
  `/api/status`. Point buyers and agents there; do not invent tier prices or caps.

Live corpus counts: `https://rekvira.com/api/coverage` (same figures as `/connect`).

## Contact

hello@rekvira.com