# jurisly-mcp

Lets an AI assistant — Claude Desktop, ChatGPT, Cursor, or anything else that speaks MCP —
work inside your Jurisly workspace. Ask it to draft an invoice, find a hearing date, or edit a
document, and it does the work in Jurisly.

## Setup

**1. Get a token.** In Jurisly: **Profile → Integrations → New token**. Give it a label
you'll recognise ("Claude Desktop — work laptop"), pick the workspace it may act in, and copy
the token. It's shown **once**.

**2. Build.**

```bash
pnpm install
pnpm build
```

**3. Point your assistant at it.** For Claude Desktop, add this to
`claude_desktop_config.json` (macOS: `~/Library/Application Support/Claude/`,
Windows: `%APPDATA%\Claude\`):

```json
{
  "mcpServers": {
    "jurisly": {
      "command": "node",
      "args": ["C:/path/to/jurisly-mcp/dist/index.js"],
      "env": {
        "JURISLY_MCP_TOKEN": "jrsly_mcp_…"
      }
    }
  }
}
```

Restart the assistant. It should list Jurisly's tools.

## Configuration

| Variable | Required | Notes |
|---|---|---|
| `JURISLY_MCP_TOKEN` | yes | From Profile → Integrations. Starts `jrsly_mcp_`. |

It connects to Jurisly at `https://apijurisly.omnimorph.org`. Nothing else to configure.

## What it can and can't do

It can do **whatever you can do** in the workspace the token is pinned to: cases, files,
finance, calendar, tasks, members, and document editing. Every action re-checks your
permissions server-side, so the assistant is never able to do more than you.

It **cannot** change your account email or password, delete a workspace, or buy a plan. That's
deliberate — this token sits in a plaintext config file that often gets cloud-synced, so a leak
must not become an account takeover or a purchase.

The token is **pinned to one workspace**. To work in a second workspace, mint a second token.

You can hold **two tokens at a time**. At the limit, revoke one before creating another — Jurisly
will not silently retire an existing token, since that would break a working integration.

## If a token leaks

Revoke it in **Profile → Integrations**. It stops working immediately — nothing is cached.
The list also shows **last used**, which is how you'd notice a token being used when you
weren't using it.

## Notes

- Runs on **your** machine, not Jurisly's servers. The protocol never touches the backend,
  which only sees ordinary REST calls.
- MCP tool calls don't consume Jurisly AI credits — your assistant pays for its own inference.
  Calls are rate-limited per token.
- Node 20+.

## Licence

Apache License 2.0 — see [LICENSE](LICENSE). "Jurisly" and "Omnimorph" are trademarks of
Omnimorph Private Limited and are not licensed for use (Apache-2.0 §6).