# Connect your AI software

## Install the skill

Extract the ZIP, preserving the `case-commander/` folder with its `SKILL.md`, `references/`, and `scripts/` files. Import that folder with your AI software's skill installer or place it in its documented skills directory. If the client supports ZIP skill import, import the ZIP directly. Reload skills if required. For a client without skill support, supply `SKILL.md` and this reference as project instructions; MCP support is still required to call tools.

Skill formats, install locations, and MCP configuration differ by client. Inspect the client's existing configuration or current official documentation before editing it; preserve existing servers and settings. Installing these instructions alone does not connect the account.

## Choose the app and create a token

- CourtBriefly: `https://app.courtbriefly.com/developers/tokens`
- Custody Commander: `https://app.custodycommander.com/developers/tokens`

Create a dedicated token with only the needed permissions. Start with read access for inspection. Write access may allow deletion; full access includes future operations. Save the token privately when shown once, select a suitable expiration, and revoke unused tokens. Do not ask the user to paste the token into the AI conversation. The client and its model provider may receive case data returned by tools.

## Remote MCP

For clients supporting Streamable HTTP with custom authorization headers:

```text
URL: <APP_URL>/api/mcp
Transport: Streamable HTTP
Authorization: Bearer <YOUR_API_TOKEN>
```

Replace `<APP_URL>` with the chosen app origin. Use the client's private token/header setting. This server uses personal tokens, not OAuth sign-in. A client supporting only OAuth connections will need the stdio option if it supports local servers.

## Local stdio option

Requires Node.js 20 or newer. The ZIP includes `scripts/case-commander-mcp.mjs`, the dependency-free official adapter. Use its absolute path; no npm install is needed.

For a client accepting `mcpServers` JSON, merge this entry into its existing configuration:

```json
{
  "mcpServers": {
    "case-commander": {
      "command": "node",
      "args": ["/absolute/path/case-commander/scripts/case-commander-mcp.mjs"],
      "env": {
        "CASE_COMMANDER_URL": "https://app.courtbriefly.com",
        "CASE_COMMANDER_API_TOKEN": "YOUR_API_TOKEN"
      }
    }
  }
}
```

For Custody Commander set `CASE_COMMANDER_URL` to `https://app.custodycommander.com`. Have the user enter their token privately or use the client's supported secret mechanism. JSON placeholders are not automatically expanded. For other config formats use the same command, arguments, and environment values in the client's documented format. Restart/reconnect the server after saving.

## Verify safely

Discover tools and make a read request such as listing the current case (`get_case`, if exposed by this token). A connection is verified only after a successful response, not merely after saving configuration. Missing tools may indicate insufficient scopes; check token expiration/revocation and account email verification. Do not perform a test upload, deletion or paid AI operation just to verify setup.

Setup and live API reference: `<APP_URL>/developers/mcp` and `<APP_URL>/developers/api`. Public contracts are available at `https://courtbriefly.com/api.html` and `https://custodycommander.com/api.html`.