Docs

Manus

Give Manus access to covered legislation and case law for autonomous multi-step legal research.

Setup

  1. 1

    Create an API key in your cadin dashboard under Settings > API Keys.

  2. 2

    In Manus, go to Settings > Integrations > Custom MCP Servers > Add Server.

  3. 3

    Enter "cadin" as the server name and paste the MCP URL below.

  4. 4

    Enter your API key in the Authentication field (format: ApiKey sk-...).

  5. 5

    Click Test Connection, Manus verifies the server and discovers all available tools.

MCP Server URL

Paste this as the custom MCP server address.

https://mcp.cadin.ai/mcp

Authentication

Manus custom MCP servers use static credentials, API key or Bearer token. OAuth is only available for Manus prebuilt connectors, not custom servers. To connect cadin, create an API key in your cadin dashboard and paste it into the Authentication field in Manus using this format:

Authentication header valuepaste into Manus auth field
ApiKey sk-...

How Manus uses tools

Manus selects tools autonomously based on their descriptions. When you assign a research task, Manus reads the tool descriptions cadin exposes and decides which ones to call without per-tool approval. This makes it well-suited for multi-step legal research, for example, finding relevant documents, reading cited passages, then broadening the search across jurisdictions, all in a single task.

There are no documented tool count limits. Manus has access to all 4 cadin document tools and can chain them across jurisdictions as needed.

cadin tools search and retrieve legal sources without modifying your account data or source materials.

Good to know

HTTPS is required for all custom MCP servers. cadin serves over HTTPS by default at mcp.cadin.ai.

Sessions are managed server-side. After a server deploy, Manus will re-initialize the session automatically on the next tool call.

Manus also offers a REST API at open.manus.im for programmatic task execution if you want to trigger research tasks from your own code.