What an MCP changes

For practitioners, the relevant point isn't the protocol — it's what the protocol unlocks. Until now, agentic drafting lived inside Paximal's own application. To move from a draft to a related task — a figure clean-up, a quick examiner lookup, a formality check — you context-switched. With the MCP, those tasks happen in the same conversation, on the same matter, with the same draft in working memory.

In short: Paximal becomes composable with everything else you've connected to Claude. That's a different kind of tool than a standalone web app.

To be clear about what the MCP isn't: it isn't a relocation. Your projects still live in the Paximal app. The MCP gives you a second window onto the same matter — you can flip between the Cowork conversation and the Paximal app in real time, with both views reflecting the same project state. Use whichever surface fits the moment.

What you can do today

The MCP exposes Paximal's full platform, including capabilities we're releasing alongside the connector itself:

• Agentic application drafting. Start a new matter, run our alignment process, and produce a complete, fully-enabled draft — claims, specification, figures — in the same session you're already working in. Nothing about how Paximal drafts changes; what changes is where you sit while it happens.

• Complex example-embodiment diagrams. Ask for a new figure illustrating a specific embodiment described in the spec, and get a publication-quality diagram drawn from the description itself rather than from a stock library.

• Figure labeling for inventor-provided drawings. Upload the figures you got from the inventor and have them labeled — reference numerals, callouts, lead lines — consistent with the spec's nomenclature.

• Formality proofreading. Antecedent basis, reference-numeral consistency, claim-spec alignment, the kind of corrections you'd otherwise run through a dedicated proofreading tool. Now invokable inside the same conversation that drafted the document.

• Reviewer-feedback implementation. When a reviewing attorney or inventor marks up a draft, Paximal applies the changes consistently across claims, spec, and figures rather than leaving you to chase implications by hand.

• Native composability with Juristat. The strategic collaboration we announced earlier this year is now operational: if you have the Juristat MCP connected, Paximal's drafting agents can use examiner reports, art unit statistics, and office action histories as inputs — not as context you have to paste in, but as live data the drafting workflow can consult.

That last one is the lever we're most excited about. It's also the subject of a longer piece we'll publish in the next two weeks.

Who it's for

The MCP is available to all current Paximal customers at no additional cost. It works with Claude Cowork, Claude.ai, and any Claude-compatible client that supports MCP connectors. If you're not yet a customer and you want to try it, schedule a Paximal demo today — we'll get you set up with both the platform and the connector in the same call.

A note on what isn't changing

The attorney still owns the work. Paximal generates; the attorney decides what to file. Our position on this has been consistent since we started: AI in patent practice should amplify the attorney's judgment, not substitute for it. The MCP doesn't change that — it just removes the friction between the moments when judgment is needed and the moments when generation gets it done.

If you've been waiting for the right time to bring agentic drafting into your regular workflow, this is it. We built the MCP because that's where our customers were already trying to work.