May 20, 2026
Article
What the Paximal MCP Changes About a Patent Attorney's Week
By Ian Schick, PhD, Esq
The interesting thing about putting Paximal behind an MCP is not the protocol. It's what disappears when you do — namely, the context switching that used to surround every drafting task. The matter you're working on, the figures you need cleaned up, the formality pass you keep meaning to run, the prior-art question that's been nagging at you since the disclosure call — they all live in one conversation now, with the draft as shared working memory.
This post is for practitioners who want to know what that actually looks like on a Tuesday. We'll walk through four workflows that change the most, and then close with what doesn't change.

1. Disclosure to first-draft review, same afternoon
A new disclosure lands. In the traditional rhythm, you read it, schedule an inventor call, take notes, sketch claim scope on paper, then spend a day or two stitching the spec together. Two dozen hours isn't an unreasonable estimate from disclosure to a draft worth reviewing.
With Paximal in Cowork, the rhythm compresses. You open a conversation, attach the disclosure, and start a Paximal project. The alignment process — Paximal's structured back-and-forth that replaces prompt engineering with attorney-directed decisions — runs in the same chat. You're answering questions about claim scope, technical vocabulary, and embodiment nuance. You're not writing prose. Shortly after you've finished alignment, Paximal has produced a complete, fully-enabled, on-brand draft ready for prefiling review.
What's new with the MCP isn't the drafting — it's that the draft now lives in a conversation you can keep working in. You can ask follow-up questions across the spec ("did we cover the alternative configuration the inventor mentioned in section 3?") without leaving the surface. You can pull related matters from your firm's document system if you have it connected. You can drop in a recent reference and ask how it changes the claim landscape before you ever set up the next inventor call.
And the project itself doesn't move. It stays accessible in the Paximal app at the same time — you can flip between the Cowork conversation and the Paximal view in real time, with both reflecting the same matter as it evolves. Use whichever surface fits the task at hand. The substantive judgment is yours.
2. Figures that match the spec, not the inventor's PowerPoint
Figures are where the gap between what an inventor provides and what an application needs is most painful. Either you get nothing usable — a napkin sketch, a slide with arrows pointing at icons — or you get something dense and unlabeled, full of internal naming that means something to the engineering team and nothing to an examiner.
Two new capabilities address this directly inside the MCP.
The first is example-embodiment diagram generation. When the spec describes an embodiment in detail but no corresponding figure exists, you can ask for one. Paximal reads the relevant section, drafts a figure that depicts the embodiment as described, and labels it consistently with the spec's reference numerals. It's not stock art; it's a figure derived from your own text.
The second is figure labeling. Drop in the figures the inventor sent — a CAD render, a flowchart, a screenshot — and ask Paximal to add reference numerals, callouts, and lead lines aligned with the spec. If the spec hasn't fully named the components yet, Paximal proposes naming and updates both the figure and the relevant spec passages together.
For most attorneys, this is the workflow that frees up the most time per matter. Figures used to be the part of drafting that benefited least from AI tools, because the bottleneck wasn't writing — it was drawing. That's not the bottleneck anymore.
3. The reviewer round-trip, without re-typing
Send a draft to a reviewing attorney or to the inventor, and a marked-up version comes back. Sometimes it's a clean tracked-changes Word file. More often it's a PDF with handwritten notes, an email with bullets, or a Slack message that says "fine but change the third claim and pull the second embodiment into a separate section."
Implementing those edits used to be the slowest part of the cycle. Not the changes themselves — the consequences. Renaming a component in claim 1 means touching the spec, the figure labels, the dependent claims, and the summary. Pulling an embodiment out means restructuring the spec hierarchy and re-checking antecedent basis throughout.
With the MCP, you describe the changes in plain language in the same conversation that holds the draft. Paximal implements them across the entire application — claims, spec, figures — and flags the places where a change in one section forces a change in another. You review the diff; you don't author it.
This is where the time savings stop being incremental and start being structural. The interior of a revision cycle used to require hours of careful, error-prone work. It now requires careful review of an automatically-generated, internally-consistent revision.
4. The formality pass, before it becomes a problem
Antecedent basis. Reference numeral consistency across claims, spec, and figures. Claim-term usage that drifts subtly between the summary and the detailed description. These are the issues that turn into office action grounds, or worse, into client questions about why the spec says one thing and the claims another.
Dedicated proofreading tools solve part of this problem well. The MCP integrates that category of check directly into the drafting conversation. You ask for the formality pass; you get back a list of issues with proposed corrections, applicable across the document. Apply, review, move on.
The practical effect is that the formality pass stops being a separate event that happens at the end of a draft. It becomes something you run mid-stream, after each substantive revision, because it's a single message in the same conversation. The errors that compound when you wait until the end stop compounding.
What doesn't change
The attorney still decides what to file. The MCP does not produce a draft that doesn't need attorney review, and we have never claimed that it should. What it produces is a draft that needs review — not authorship.
For firm leaders running the math on this: the variable that changes is what an attorney's hour produces, not what the attorney is responsible for. A senior practitioner who used to author and revise now reviews and directs. The strategic and judgment-heavy work — claim scope, prosecution posture, portfolio fit — is exactly where attorney time still concentrates. The mechanical work — re-typing edits, chasing reference numerals, redrawing figures — is exactly where it doesn't.
We built Paximal this way on purpose. The MCP just removes one more layer of friction between deciding what should happen and having it done.
If you want to see what your week looks like with this in it, schedule a demo. For current customers, the MCP is available now at no additional cost — sign in to the platform for setup instructions.
