Docs

Documentation

Set up cadin as the legal search layer for your AI workspace. Connect through MCP, authenticate with OAuth or API keys, and retrieve legislation and case law from covered sources.

What cadin does

AI tools need primary legal sources before they can help with serious legal work. cadin gives them a search layer for legislation and case law instead of leaving them to rely on general web search.

Start with Swiss, German, and EU sources. Your AI can search across covered materials, retrieve the source text, and bring cited legislation and case law back into the workflow.

The MCP server exposes 4 document tools for source discovery, document search, and source retrieval.

Quickstart

Works with any MCP client that supports remote servers and OAuth.

  1. 1

    Go to Settings > Connectors and add a new custom connector.

    Claude docs
  2. 2

    Paste this URL as the server address:

    https://mcp.cadin.ai/mcp
  3. 3

    Sign in with OAuth when prompted. No API key needed.

Setup complete. 4 tools are now available. Full Claude guide

Client guides

Each client has its own setup flow. Pick yours.

Authentication

The server supports both OAuth and API keys. Pick whichever your client handles best.

OAuth

Best for Claude, Cursor, and Codex. No secrets in config files.

  • Paste the MCP URL and let the client handle the browser sign-in flow.
  • Dynamic client registration and protected-resource discovery are wired up.
  • Tokens are short-lived JWTs verified on every request.

API key

Best for Manus, custom integrations, and MCP SDKs.

  • Create a key in your dashboard, it starts with sk-.
  • Send it as Authorization: ApiKey <key> or x-api-key: <key>.

Document tools

Tool guides explain how cadin searches, browses, and opens legal source text for AI clients.

Troubleshooting