# MCP Quickstart - Relex

> Get the Relex MCP server running in under 5 minutes. Installation, configuration for Claude Desktop and Cursor, and usage examples.

[Home](/) / [Docs](/docs/a2a) / MCP Server

### Connectors

- [All agents](/docs/connectors)
- [Claude](/docs/connectors/claude)
- [GPT](/docs/connectors/gpt)
- [Grok](/docs/connectors/grok)
- [Gemini](/docs/connectors/gemini)

### MCP Server

- [Overview](/docs/mcp/)
- [Quickstart](/docs/mcp/quickstart/)

### A2A Protocol

- [Overview](/docs/a2a)

#### On this page

- [1\. Authorize the right connection](#section-1)
- [2\. Read saved context](#section-2)
- [3\. Save work before switching agents](#section-3)
- [Discover other operations](#clause-5)
- [Troubleshooting and revocation](#clause-6)

# MCP Server Quickstart

Use a synthetic matter before connecting a real client workflow.
Endpoint: `https://relex.legal/api/mcp`.

## 1\. Authorize the right connection

Follow the guide for your exact host:
[Claude](/docs/connectors/claude), [ChatGPT](/docs/connectors/gpt),
[Grok](/docs/connectors/grok), [Gemini Apps / CLI](/docs/connectors/gemini),
[Perplexity](/docs/connectors/perplexity), [Harvey](/docs/connectors/harvey),
or [another MCP client](/docs/connectors/mcp).

An administrator may need to enable the connection; each user's permissions must
be appropriate for that account. Review OAuth scopes and start read-only.
Visiting the website does not install or authorize a connector.

## 2\. Read saved context

The following are tool-call examples, not shell commands:

```json
{"name":"list_matters","arguments":{"limit":10}}
```

Use an ID returned for your own account:

```json
{"name":"read_matter_context","arguments":{"caseId":"YOUR_MATTER_ID"}}
```

Check three facts and two source references from the
[downloadable synthetic fixture](/guides/portable-legal-context).
Missing documents should be reported as missing, not reconstructed from memory.

## 3\. Save work before switching agents

When there is an existing Relex steering session and you have authorized writes:

```json
{"name":"conclude_matter_session","arguments":{"caseId":"YOUR_MATTER_ID"}}
```

Verify the result in the workspace. This concludes an existing session; it is not
a generic import of everything said in a host chat. Reconnect through another
supported host and read the same matter to check continuity.

## Discover other operations

```json
{"name":"search","arguments":{"query":"onboarding"}}
```

```json
{"name":"execute","arguments":{"method":"GET","path":"/onboarding/status"}}
```

Use the returned route schemas rather than guessing fields. Both interfaces
retain authorization and privacy guards. See the [tool table](/docs/mcp).

## Troubleshooting and revocation

- No setup control: check plan, region and administrator policy in the host guide.
- OAuth fails: use the exact HTTPS endpoint, inspect discovery and sign in to the
intended Relex account. Never paste an access token into a conversation.
- Insufficient scope: authorize the needed operation separately; do not replace
the connection with a colleague's API key.
- Missing matter: verify account and matter permissions; a public profile is not
private matter access.
- Sealed-data guidance: open the workspace route for originals and identity steps.
- Old tool list: refresh the host's connection after a deployed server change.
- Disconnect: remove the host connection **and** revoke its corresponding key in
Relex Settings → API Keys. Verify further access is denied.

Static API keys remain a separate CI/headless option under Settings → API Keys.
Keep them in your client's secret configuration, never source control or chat.
Client-side privacy and server/custom processing boundaries are explained in the
[verification guide](/guides/verify-legal-ai-privacy).

---

_[View this page on relex.legal](https://relex.legal/docs/mcp/quickstart)_