AI agents & MCP

Everything you do on a case — arranging its board, cleaning it up, following watches, weighing hypotheses — an AI client can do as well, over the MCP server: Claude, Cursor, Codex or your own agent. The assistant in the app uses the very same tools, and asks you before every change it makes.

An agent’s changes are ordinary board changes: they land on the timeline under mcp, other people’s open boards update, and a closed case stays read-only.

Give the client a token

Settings → MCP Server → Create token. Switch All tools off and tick what the client needs:

A client that should only read and arrange boards still needs Cases to find a case by name (search_cases); without it, give it the case id.

Read the board

get_case_board returns the board as a labelled summary: every item with what it stands for, so a client never has to join ids across lists.

{
  "board": { "caseId": "3f5c…", "version": 12, "readOnly": false, "caseStatus": "OPEN" },
  "counts": { "evidence": 3, "findings": 7, "hypotheses": 1, "notes": 1, "frames": 1, "links": 1, "stances": 2, "unplaced": 1 },
  "items": [
    {
      "id": "8f0c…", "kind": "EVIDENCE", "label": "payroll-2024.xlsx", "x": 40, "y": 60, "parentId": "c2d1…",
      "assetId": "a9e2…", "findingCount": 2,
      "findings": [{ "findingId": "f-17", "type": "IBAN", "value": "AT61 1904 3002 3457 3201", "severity": "HIGH", "state": "new" }]
    },
    {
      "id": "5b7e…", "kind": "HYPOTHESIS", "label": "Payroll left via the share", "unplaced": true,
      "status": "PROPOSED", "stances": { "supports": 2, "contradicts": 0, "neutral": 0 }
    }
  ],
  "links": [], "stances": [], "relations": [{ "source": "8f0c…", "target": "a41b…" }]
}

• A finding’s state is the one the board shows: open, new, gone, resolved, dismissed or deleted (see Evidence & findings).
• Positions: x/y of an item with a parentId — inside a frame, or a comment pin — are relative to that parent. unplaced items have no position yet.
• relations are the lines the platform draws between evidence (lineage, duplicates). Nobody can change those on the board.
• board.version goes back as baseVersion when changing the board.
• view: "full" returns the raw board instead; snapshotId reads a snapshot in the same shape.

Change the board

apply_case_board_ops takes a batch of changes, applied in order in one go. Each change succeeds or is refused on its own (rejected, with a reason), so one stale item never sinks the rest.

{
  "caseId": "3f5c…",
  "baseVersion": 12,
  "ops": [
    { "type": "item.create", "id": "0b6e2a7c-0f4e-4c2a-9a55-3c1d2e4f5a6b", "kind": "NOTE", "x": 900, "y": 40,
      "content": { "text": "Both exports carry the same IBAN. Who ran them?" }, "style": { "color": "yellow" } },
    { "type": "link.create", "id": "9d1fb3e2-7c4a-4f1e-8b2d-5e6f7a8b9c0d", "kind": "related_to", "certainty": "SUSPECTED",
      "source": { "itemId": "0b6e2a7c-0f4e-4c2a-9a55-3c1d2e4f5a6b" }, "target": { "itemId": "8f0c…", "findingId": "f-17" } },
    { "type": "stance.set", "hypothesisItemId": "5b7e…", "target": { "itemId": "8f0c…" }, "stance": "SUPPORTS", "note": "Same IBAN" }
  ]
}

• Ids are the client’s: every new item or link gets a fresh UUID, so a batch sent twice changes nothing twice, and later ops of the same batch can refer to it (the link above points at the note created before it).
• Undo is the matching restore; removed evidence comes back with its findings, notes and stances.
• x/y can be left out when adding evidence, hypotheses or comments; then let the board place them.

Arrange the board

tidy_case_board replaces the arrangement people made. Run it with dryRun: true first to see every move, and take a snapshot first if the current layout matters. Each move reports where the item was (from), so a tidy can be walked back with item.update.

Trace connections

trace_case_connections is Show connections for an agent: what the case’s assets connect to beyond the board, upstream (what feeds them), downstream (what they feed) and alongside (duplicates, look-alikes), hop by hop. Every node says whether it is in the case already (inCase, with its board item). An agent brings one in with evidence.add. See Connections & neighbours.

Clean-up, filters and escalation

Every rule that takes things out of a case can be previewed first, without changing anything:

clear_case_escalations takes escalation marks off once they are dealt with. The rules themselves are explained in Clean-up & filters and Escalation.

Watches and hypotheses

• Hypothesis rules: list_case_hypothesis_rules, add_case_hypothesis_rule, update_case_hypothesis_rule and remove_case_hypothesis_rule hand a watch’s answers to a hypothesis as supporting, contradicting or neutral, and land them beside it on the board. See Hypothesis rules.
• Watches: link_case_inquiries links questions; set_case_inquiry_auto_pull turns a watch’s auto-add on or off; unlink_case_inquiry stops the case following it (its per-watch rules go with the link).
• Verdicts: update_case_thread sets a hypothesis’s status (Supported, Refuted, …) and confidence, and writes the change in its log. add_case_thread_entry adds notes, or a new statement of the claim.
• Stances on the board are stance.set / stance.remove.

Snapshots

take_case_board_snapshot freezes the board as it is; list_case_board_snapshots lists them (closing a case takes one by itself), and get_case_board with a snapshotId reads one back.

What stays with people

Some things are deliberately not open to agents: deleting a case, deleting a hypothesis with its whole log (an agent can take the card off the board, which keeps the thread), deleting a global relationship everywhere, and exporting the board as an image. They destroy history the case exists to keep, so they stay a person’s decision in the app.

Tool reference

Generated from the MCP server itself. Open a tool for its parameters (* = required).