Docs

Integrations

Integrate Cadin into your own application. These examples show how to connect the MCP server to your system so your LLM can discover and call all 4 legal research tools automatically.

Setup

  1. 1

    Install an LLM SDK that supports remote MCP servers using MCP 2026-07-28.

  2. 2

    Create an API key in your Cadin dashboard.

  3. 3

    Include Cadin in your tools and start calling.

Usage

Anthropic TypeScript SDK
Installnpm
npm install @anthropic-ai/sdk
ExampleTypeScript
import Anthropic from "@anthropic-ai/sdk";

const client = new Anthropic();
const response = await client.beta.messages.create({
  model: "claude-sonnet-4-6",
  max_tokens: 4096,
  mcp_servers: [
    {
      type: "url",
      url: "https://mcp.cadin.ai/mcp",
      name: "cadin",
      authorization_token: "YOUR_CADIN_API_KEY",
    },
  ],
  tools: [{ type: "mcp_toolset", mcp_server_name: "cadin" }],
  messages: [
    { role: "user", content: "Find EU regulations about the right to erasure" },
  ],
  betas: ["mcp-client-2025-11-20"],
});

console.log(response);

Authentication

HeaderFormatNotes
AuthorizationApiKey sk-...Recommended for SDK usage
x-api-keysk-...Alternative header
AuthorizationBearer eyJ...OAuth tokens (for browser-based flows)

Do not send API keys as Authorization: Bearer sk-... , the server rejects that format.

Good to know

Cadin handles each request independently. Retry a request interrupted by a deploy or restart. Clients must support MCP 2026-07-28 and include protocol metadata and authentication with every request.

Tool responses are plain text formatted for LLM consumption, not JSON. Search results include pagination hints embedded in the text (e.g., "Use offset: 20 to see more").

Discovery and tool listings include a one-minute private cache lifetime. Tool calls always check the authenticated caller's quota.