Skip to content
  1. Home
  2. Developers

Build on the same client records your firm works in

The REST API works on the same clients, tasks, documents and invoices your staff use, and webhooks tell your system when something changes. The MCP server lets your own agents work in Firmary under your firm’s rules, as the person who connected them or as a firm agent with its own name.

Product preview. Fictional client data.

Tom’s terminalClaude Code
> Make Megan a task: review Ogden Dental's Q3 books by Friday.

⏺ firmary · firmary_catalog_write (MCP)
  ⎿ Task created for Megan Carter, due Fri, Nov 13

'Review Q3 books' is on Ogden Dental Group's record, assigned to Megan, under your name.
ActivityOgden Dental Group
  • TH

    Claude Code as Tom Hale created “Review Q3 books” for Megan CarterJust now · over MCP · on Tom Hale’s rules

  • AO

    Dr. Anne Ogden uploaded 3 bank statementsYesterday, 4:40 PM · in PocketFirm

  • MC

    Megan Carter sent the Q3 bank statements requestNov 7, 9:30 AM

The API uses your permissions

Every request runs with the connected identity’s current permissions, at your firm’s own Firmary address under /api/v1.

Your first requestcurl
curl --fail-with-body --silent --show-error \
  "$FIRMARY_ORIGIN/api/v1/clients?limit=25" \
  -H "Authorization: Bearer $FIRMARY_API_KEY" \
  -H "Accept: application/json"

# 200 OK
{
  "data": [
    {
      "id": "3f6c2a1e-8b4d-4c7a-9e21-5d0b7f3a6c14",
      "name": "Ogden Dental Group",
      "kind": "business",
      "status": "active",
      "email": "[email protected]",
      "phone": null,
      "address": null,
      "ein": null,
      "entityType": "s_corp",
      "createdAt": "2026-03-02T15:04:11Z",
      "updatedAt": "2026-11-06T21:40:12Z",
      "archivedAt": null,
      "tags": [],
      "fieldValues": {},
      "summary": {
        "openTasks": 3,
        "openInvoices": 1,
        "openDocRequests": 1,
        "lastActivityAt": "2026-11-06T21:40:12Z"
      }
    }
  ],
  "page": { "nextCursor": null },
  "fieldDefinitions": []
}
WhatHow it works
KeysSomeone allowed to manage API credentials (administrators and owners, by default) makes them under Admin › Integrations › API credentials, once API access is on for your firm. Give each key only the scopes it needs. Each key is shown once.
PagesLists come back with page.nextCursor. Send it back unchanged until it’s null.
The referenceThe API reference and the OpenAPI schema are in the app for signed-in staff.

Webhooks tell your system when a client uploads, signs or pays

Create an endpoint with the events you want. Before you trust a delivery, check its Firmary-Signature header: an HMAC of the timestamp and the raw request body, made with the endpoint’s signing secret. An endpoint receives events for the whole firm by default, or only for the clients you list.

  • document.uploaded
  • signature.completed
  • payment.succeeded
  • payment.failed
  • invoice.sent
  • proposal.accepted
  • form.submitted
  • client.created
Subscribe to uploadsPOST
curl -X POST "$FIRMARY_ORIGIN/api/v1/webhooks/endpoints" \
  -H "Authorization: Bearer $FIRMARY_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "Files into our DMS",
    "url": "https://hooks.brightwatertax.com/firmary",
    "eventNames": ["document.uploaded", "document.accepted"]
  }'

A delivery when a client uploads a document looks like this:

Firmary-Signature: t=1786000000,v1=5f2c…

{
  "id": "7c1d9e42-5a3b-4f60-8d2e-b14a6f0c3e97",
  "type": "document.uploaded",
  "occurredAt": "2026-11-06T21:40:12Z",
  "sequence": 1842,
  "data": {
    "uploadId": "e2b84f1a-6d3c-4a95-b07e-91c5d2f8a364",
    "requestId": "5f0a3c87-1e9b-4d26-a8f4-3b6e0d7c2a19",
    "clientId": "3f6c2a1e-8b4d-4c7a-9e21-5d0b7f3a6c14"
  }
}

Your agents sign in as a person at your firm, or under their own name

Firmary’s MCP server is listed in the official MCP Registry as app.firmary/mcp. An agent a person connects signs in as them and works within their access and your agent rules: what it may do on its own, what asks first, and what it never does. A firm agent works under its own name, with the clients and rules you give it. The log names the agent on every call, and the person it acts for when there is one.

  • Serverhttps://os.firmary.app/api/mcp
  • Works withClaude, ChatGPT, Claude Code, Codex, Cursor, VS Code, and other clients with remote MCP connectors
  • RulesSet in Firmary, not in the agent. Agent rules

firmary, the command line, for staff who work in a terminal

It signs in with your staff account and works with the same records and the same approvals. Install it from firmary.app/download, with Homebrew on a Mac or Scoop on Windows. The current version is shown on the download page.

Command line guide
Megan’s terminalfirmary
$ firmary auth login
  Signed in as Megan Carter · Brightwater Tax

$ firmary clients list
  Ogden Dental Group        Dr. Anne Ogden
  Harbor & Pine Bakery      Sam Whitford
  Laura & Mark Ryan         Laura Ryan
  Northgate Pediatrics      Dana Brooks

Connect your first agent

Set the rules in Firmary, then point any MCP client at one address.

Leave your work email.