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, ChatGPT,
Grok, Gemini Apps / CLI,
Perplexity, Harvey,
or another MCP client.

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:

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

Use an ID returned for your own account:

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

Check three facts and two source references from the
downloadable synthetic fixture.
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:

{"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

{"name":"search","arguments":{"query":"onboarding"}}
{"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.

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.