Foxit MCP and PDF API stack
PMM workflow, built on Foxit's MCP plus API stack
Drop a press release draft into a folder. A Claude Code agent reads it, writes the launch brief, files the review task, and sends it for signature. One pass, around 56.5s, no copy-paste.
- Run time
- 56.5s
- Input
- 6-page draft PDF
- Foxit calls
- 3 APIs, 5 steps
- Output
- Brief, task, envelope
What it does
A product marketing manager gets a press release draft and has to turn it into a launch brief, a tracked review task, and a signature request. That is an hour of careful copy-paste across three tools, repeated for every launch.
This agent does the same work on its own. It runs on Claude Code as the host, calls the Foxit PDF API MCP Server to read the draft, and calls Foxit Document Generation and eSign over REST for the brief and the sign-off. The point is to show the Foxit stack doing real marketing work, not a toy demo.
How it works
Five steps run on every dropped PDF. The numbers and links below come from a real run, not a mockup.
- 01Read the draft
The agent picks up the dropped PDF and reads it through the Foxit PDF API MCP Server. It uploads the file, runs text extraction, and pulls the metadata back, all over the Model Context Protocol.
Foxit PDF Services, through the MCP server
- 02Pull the launch facts
Claude reads the raw text and returns structured facts: product name, launch date, the top three value props, the target buyer, and the leadership quote. The keys line up with the brief template.
Claude Code
- 03Generate the brief
The facts merge into a sales-enablement Word template and come back as a clean one-page PDF. No manual formatting, no copy-paste from the press release.
Foxit Document Generation
- 04File the review task
A row lands in the Notion Launch Briefs database with the product, the launch date, a link to the brief, and the signature status, ready for a content reviewer to pick up.
Notion, through the connected MCP server
- 05Route for sign-off
The brief goes out for legal sign-off as an eSign envelope, and the envelope ID is captured back on the Notion row so the whole trail lives in one place.
Foxit eSign
Last run extracted ROG Ally X and finished all five steps in 56.5s. The brief, the Notion task, and the eSign envelope all came out of that single pass.
Open the full run detail →Watch a run
A screen recording of one end-to-end pass, from dropped PDF to signed-off brief.
Run archive
Every run is archived with its input, the extracted facts, the generated brief, and the downstream links.
ROG Ally X launch brief
5 of 5 steps ok, 56.5s total
How I would ship this as Foxit developer marketing
Three concrete moves, written from the seat of the PMM who would own this launch.
A one-command quickstart that proves the stack in a minute
Ship this as a public template repo. A developer clones it, adds two keys, drops the sample PDF, and watches five Foxit calls run end to end. That first-minute win is what turns a docs visit into an account.
Lead with MCP, since that is the part developers have not seen
Most PDF APIs stop at REST. Foxit already ships an MCP server, so the story is that an agent can drive the whole stack with no glue code. A workflow like this one makes that concrete instead of abstract.
Frame every API around a job, not an endpoint
Document Generation is a launch brief. eSign is legal sign-off. PDF Services is reading the source. Tie each call to a task a buyer already does by hand, and the value reads in seconds.