> ## Documentation Index
> Fetch the complete documentation index at: https://api.lawtte.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Claude Desktop (macOS)

> Run the Lawtte connector locally with an API key instead of the web connector.

Most firms should use the [web connector](/mcp/connect-claude) — it needs no
install and no key. This local path exists for macOS pilots that need Lawtte inside
Claude Desktop, and the same `mcp-remote` pattern works for any other stdio-only
client. The [protocol reference](/mcp/server) has the generic version.

## Guided setup

<Steps>
  <Step title="Create a key">
    As the Studio account owner, open **Dashboard → Connect**, create a labeled key,
    and copy its one-time value. Lawtte stores only a hash — if you lose it, create
    a new one.
  </Step>

  <Step title="Run the helper">
    Download and run
    [`lawtte-claude-mac.sh`](https://www.lawtte.ai/claude-desktop/lawtte-claude-mac.sh)
    from the Connect page. It requires Node.js, installs a pinned `mcp-remote` into
    Claude's support folder, prompts for the key without echoing it, writes a
    `0600` header file, and adds `lawtte-studio` to your existing Claude Desktop config.
  </Step>

  <Step title="Restart Claude Desktop">
    Quit fully and reopen, then check **Settings → Developer** for a running
    `lawtte-studio` server.
  </Step>
</Steps>

## Manual setup

If you prefer to wire it yourself, put the key in a file readable only by you and
point `mcp-remote` at it:

```json theme={null}
{
  "mcpServers": {
    "lawtte-studio": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://www.lawtte.ai/api/mcp",
        "--header-file", "/absolute/path/to/lawtte-header",
        "--transport", "http-only"
      ]
    }
  }
}
```

The header file contains one line:

```
Authorization: Bearer lawtte_sk_...
```

<Warning>
  Never put the key in a URL, a command argument, or a chat message. Command
  arguments are visible to every process on the machine.
</Warning>

## Removing access

Delete the key on **Dashboard → Connect**. The local config stops working
immediately, whether or not you remove it from the Claude Desktop config file.


## Related topics

- [Connect Claude](/mcp/connect-claude.md)
- [Protocol reference](/mcp/server.md)
- [Authentication](/authentication.md)
- [Quickstart](/quickstart.md)
- [Troubleshooting](/mcp/troubleshooting.md)