Skip to main content
All MCP guides

MCP setup guide

Connect Claude Desktop

Add Attorly to Claude Desktop on macOS or Windows and use its tools for contracts, clauses and legal research in your conversations.

Before you start

  • An Attorly Pro or Enterprise plan.
  • Claude Desktop and Node.js 18 or later (run node --version to check).

Claude's Connectors settings add remote servers that sign in with OAuth. Attorly's MCP server uses API keys, so Claude Desktop connects to it through its configuration file, as below.

Steps

  1. Create a key

    Create a key in Settings › Developers and choose Claude Desktop. The settings page then shows the steps below with your key already filled in.

    Create a key for Claude Desktop

  2. Add Attorly to Claude Desktop

    Claude Desktop starts Attorly through the mcp-remote bridge, which needs Node.js on your computer.

    Add this to Claude Desktop's configuration file, then quit and reopen Claude Desktop

    macOS: ~/Library/Application Support/Claude/claude_desktop_config.json · Windows: %APPDATA%\Claude\claude_desktop_config.json
    {
  "mcpServers": {
    "attorly": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://attorly.ai/api/mcp",
        "--header",
        "Authorization:${ATTORLY_AUTHORIZATION}"
      ],
      "env": {
        "ATTORLY_AUTHORIZATION": "Bearer lbmcp_your_api_key"
      }
    }
  }
}

  3. Check that it works

    Quit Claude Desktop completely and open it again. Attorly appears under the tools button in a new conversation. Ask: “List my five most recent documents in Attorly.”

If it does not work

Claude Desktop shows an error about the configuration file.
The file must be valid JSON. If it already had other servers, add attorly inside the existing mcpServers object instead of adding a second one.
Attorly does not appear after restarting.
Check that Node.js is installed and that npx works in a terminal. Open Settings › Developer in Claude Desktop to see the server's log.
Something else went wrong.
Errors such as 401, insufficient_scope and rate_limited are explained in the MCP troubleshooting section. Every call also appears in Settings › Developers › Request logs, with the error it returned. MCP troubleshooting

Other clients