Skip to main content
The MCP server exposes 45 tools. Every one is a thin proxy onto the same backend the web app uses, so the data, the tenant scoping, and the billing are identical. The Sign in column says whether a token is required. Read only tools are annotated as such in the protocol, so assistants can distinguish a lookup from a write without guessing.
Prefer get_claim_analysis over analyze_application: for almost every application the analysis has already been run, and get_claim_analysis returns it directly.

Docket and cases

Everything on My Docket and the case header.

Lookup and deadlines

Analysis and research

The case workspace: claims, rejections, prior art, prosecution history, analytics.
get_claim_analysis returns claim text with amendment markup preserved: strikethrough for deleted text, underline for inserted text, and status identifiers such as [Currently Amended] or [Withdrawn]. Patent claims are legal text. The server instructs connected assistants to reproduce them verbatim and never to summarise or omit claims. If you are building your own client, honour the same rule.

Draft ROA wizard

The guided Response to Office Action flow, exposed as the same ordered state machine the web wizard drives. Call them in sequence. A headless path exists for when no human is choosing strategies:

USPTO forms

The Forms page, end to end.

Agent workflows

The agent queue, where Abigail prepares work and a human approves it.

Filing

Abigail never transmits to USPTO Patent Center on its own. prepare_filing_package produces the package and the instructions. A human signs in to Patent Center and files. record_filing_receipt closes the loop afterwards.

Account

Settings are read only through MCP by design. get_user_settings returns links back to abigail.app for anything that changes account state.

Guided follow ups

Some tools attach a next_actions array to their response, naming the tool to call next and a display string for the user. A “case not found” result, for example, comes back suggesting add_case with the application number already filled in. Surfacing these turns a dead end into the same guided path the web app offers.

Connect

Setup and the OAuth handshake.

Match the web app

Screen by screen recipes and the honest gap list.