MCP tools

analyze_form uploads the blank PDF once; the result is cached on your machine. fill_form and fill_template stamp the answers into a new, flattened PDF on your machine. Ids in values may be shortened to an unambiguous prefix of 4 or more characters, as in the examples below.

Analyze a blank PDF form. Analyze a blank PDF form with fenfill and list its fillable fields (ids, types, labels). Uploads only the blank form. Costs one page scan per analyzed page unless cached or the PDF has native form fields (no page scans; detect_extra_blanks adds a paid scan of the chosen pages for blanks without a native field); pass estimate: true first to see the cost without uploading. Results are cached locally, so repeat calls and narrowing with pages use no page scans. If it returns status "running", call it again with the same arguments. To correct the layout and keep the corrections, analyze with save_as_template: true (edits on an unsaved analysis can be used for filling/preview but can't be saved). A rate-limit or busy refusal is waited out automatically (up to about a minute) before it is reported.

Inputs

Returns

The form's fields with their ids, types and labels, by section (with each section_id). status: "running" means the result isn't ready yet: call again with the same arguments. With estimate: true: page_count, likely_mode, estimated_scans and scans_remaining, and nothing is uploaded.

Example

{  "path": "~/Documents/blank-application.pdf",  "pages": "1-3"}

Fill an analyzed PDF locally. Fill a PDF you analyzed with analyze_form and write a new, flattened PDF. Runs entirely on this machine and the values never leave it; the only network use is a one-time download of the public Japanese font from fenfill.com, the first time a value needs it (it carries no form data). values maps field ids to: text/multiline = string, stamped exactly as given (a date in a text field goes in the format its label or placeholder asks, e.g. "mmddyyyy" → "10042026"); date = "YYYY-MM-DD", printed in the field's date_format (shown on the field, e.g. DD/MM/YYYY); comb = string, one character per cell; checkbox = boolean; radio = option id or label, or the bare option text ("No" for "Smoke? No"); multiselect = array of those; table = {cellId: value}; table_rows = [{columnId: value}, …]; signature = {"image_path": "/abs/sig.png"} (PNG or JPG). A signature with signing_requirement "external" is signed outside fenfill (on paper or by e-sign) and stays blank. Returns filled/skipped counts and warnings, including text shrunk hard or running past its box and filled boxes that overlap; pass check_pdf to see the result.

Inputs

Returns

Filled and skipped counts and warnings: keys that matched nothing (with candidates), text shrunk hard or running past its box, filled boxes that overlap, required fields left empty. The new PDF is written to output_path on your machine.

Example

{  "path": "~/Documents/blank-application.pdf",  "values": {    "3f9a2c": "Ada Lovelace",    "b71e04": "1990-05-17",    "c02d9e": true,    "e45a10": "No"  },  "output_path": "~/Documents/application-filled.pdf",  "check_pdf": true}

Fill a saved template locally. Fill a saved fenfill template and write a flattened PDF. The blank PDF and field schema are downloaded; filling happens on this machine and the values are never sent anywhere. values maps field ids to: text/multiline = string, stamped exactly as given (a date in a text field goes in the format its label or placeholder asks, e.g. "mmddyyyy" → "10042026"); date = "YYYY-MM-DD", printed in the field's date_format (shown on the field, e.g. DD/MM/YYYY); comb = string, one character per cell; checkbox = boolean; radio = option id or label, or the bare option text ("No" for "Smoke? No"); multiselect = array of those; table = {cellId: value}; table_rows = [{columnId: value}, …]; signature = {"image_path": "/abs/sig.png"} (PNG or JPG). A signature with signing_requirement "external" is signed outside fenfill (on paper or by e-sign) and stays blank.

Inputs

Returns

The same report as fill_form. The blank PDF and fields are downloaded; the values are stamped on your machine, with the workspace's branding as in the fenfill web app.

Example

{  "template_id": "6c1d2e8a-4b7f-4e21-9a3c-5d0e7f8b9a12",  "values": {    "3f9a2c": "Ada Lovelace",    "9d40b1": [      {        "1a2b": "Notebook",        "5c6d": "2"      }    ]  },  "output_path": "~/Documents/order-filled.pdf"}

Make a fillable PDF from a saved template. Turn one of your saved fenfill templates into a blank fillable PDF: the original form with a real form field on every blank, so it can be filled in any PDF reader. The fields are empty; this tool takes no values and never sends any (only the template id goes to fenfill). Uses the template as saved in fenfill: unsaved local edits (edit_template) are not in it, so save_template first. Needs the Team plan or above; to fill the form yourself, use fill_template (any plan). If some fields couldn't be placed, the result has skipped_fields and a skipped_note saying how to fix them.

Inputs

Returns

output_path and bytes of the blank fillable PDF written there: the form with an empty form field on every blank, to fill in any PDF reader. Only the template id is sent. edited_note when you have unsaved local edits, which the PDF doesn't include.

Example

{  "template_id": "6c1d2e8a-4b7f-4e21-9a3c-5d0e7f8b9a12",  "output_path": "~/Documents/order-fillable.pdf"}

List saved templates. List the workspace's saved fenfill templates, newest first. analyzed_pages lists the pages fenfill analyzed: a page missing from it (compare page_count) was never analyzed, so it has no fields yet (reanalyze_template fixes that).

Inputs

Returns

The workspace's templates, newest first, each with page_count and analyzed_pages, and a next_cursor for the next page.

Example

{  "limit": 20}

Get a template's fields. Get a saved template's fillable fields (ids, types, labels) for fill_template. Use pages to narrow a large form. With local edits (edit_template) it lists your working copy, as fill_template and preview_page use it (edited: true): new ids, deletions, sections and order show before you save; version: "saved" lists fenfill's saved version instead. unanalyzed_pages (when present) lists pages fenfill never analyzed: they have no fields yet; reanalyze_template with kind scratch analyzes them.

Inputs

Returns

The fields in sections, in fenfill's order, with field_count (entries listed) and field_count_total (the whole form). unanalyzed_pages when some pages were never analyzed; edited: true when it lists your local working copy.

Example

{  "template_id": "6c1d2e8a-4b7f-4e21-9a3c-5d0e7f8b9a12",  "pages": "1"}

Create a recipient link. Create a personal fill link for one recipient of a restricted template (analyze_form with save_as_template: true and access: "restricted" makes one; a public template answers template_not_restricted). Needs a plan with recipient links. Track it with get_recipient_status.

Inputs

Returns

A personal fill link for that recipient. It is a working access link to the form: treat it as a secret and share it only with that recipient.

Example

{  "template_id": "6c1d2e8a-4b7f-4e21-9a3c-5d0e7f8b9a12",  "label": "Applicant 1",  "expires_at": "2026-12-31T23:59:59Z"}

Recipient link status. List a template's recipient links and their status (pending, opened, completed).

Inputs

Returns

The template's recipient links, each with its status: pending, opened or completed.

Example

{  "template_id": "6c1d2e8a-4b7f-4e21-9a3c-5d0e7f8b9a12"}

Account and limits. Show this API key's plan, page scans left and limits. To price an analysis, call analyze_form with estimate: true instead: it counts the pages and detects native fields locally, with no upload, and compares that with scans_remaining.

Inputs

None.

Returns

The plan, the page scans left and the limits for this API key.

Example

{}

Preview a page with its field boxes. Render one page as a PNG with every field box outlined (green filled, orange warning, red skipped, grey empty) and tagged with its id prefix, plus a legend: tag → id, type, label, box (page fractions, top-left origin), format and font_pt; options, table cells (row, col), table_rows columns and (in a crop) comb cells with their own boxes. placement_warnings ([] = checked, clean) covers every box shown: text much larger than its neighbours', a box over printed text (not on scans; a pale hint at its left edge is a placement_note), a box past its ruled cell, an option box on the wrong side of its caption. Read-only audit; values stamp test values. overlay: "outline" drops the tags, "none" shows only the stamped page (e.g. after check_copy_failed). crop + zoom magnify a region; legend: "changed" lists only what changed since your last preview of the page (moved_into: fields now in a table or group). Renders the edit_template working copy if any, else the saved or analyzed version (edited: true/false). Local: nothing is written to disk, values are never sent; the sole network use is a one-time download of fenfill.com's public Japanese font when a value first needs it (no form data).

Inputs

Returns

A PNG of the page plus a legend: each box's tag, id, type, label and box, with formats, options and table cells. warnings and placement_warnings are always present ([] = checked and clean). width, height and dpi describe the image; edited says whether it shows your local working copy.

Example

{  "path": "~/Documents/blank-application.pdf",  "page": 1,  "overlay": "full"}

Correct a form's fields locally. Correct a form's fields on this machine: move, resize, relabel, retype, add, delete or regroup fields of an analyzed PDF (path) or a saved template (template_id). Edits go to a local working copy that fill_form, fill_template and preview_page use at once; nothing is sent until save_template, and then only the layout and the form's wording. Labels, descriptions, placeholders and options hold the FORM's own wording (its captions and instructions), never the user's answers: answers go only in fill values. Ids are the ones analyze_form / get_template / preview_page show (an option or table cell id addresses that box); any id may be shortened to an unambiguous prefix of 6+ characters, like the preview tags. Coordinates are fractions of the page (0–1), top-left origin, x right, y down; preview_page's legend shows every box. Returns applied, rejected [{op_index, reason}], diff_summary (ops: snapped, noop per op) and warnings ([] = none; placement checks touched boxes: oversized text, over printed text, past the ruled cell). Edits to an unsaved analysis stay local: to keep corrections, analyze_form with save_as_template: true and edit that template.

Inputs

Returns

applied, rejected ([{op_index, reason}]), diff_summary (each applied op, with snapped and noop) and warnings from the placement checks.

Example

{  "path": "~/Documents/blank-application.pdf",  "ops": [    {      "op": "move",      "id": "3f9a2c",      "dx": 0.01,      "dy": 0,      "snap": "underline"    },    {      "op": "relabel",      "id": "b71e04",      "label": "Date of birth"    }  ]}

Save local edits to a template. Save edit_template's local working copy of a saved template to fenfill (only the layout and the form's wording are sent; never fill values). Fails safely if the template changed in fenfill since the edits began (template_conflict: the local edits are kept; discard and re-apply them), and refuses wording that repeats an answer given to fill_form / fill_template / preview_page in this session (answers never go into a template): answer_in_template lists the matched ids and properties. An answer: fix it with edit_template. The form's own wording (a caption that shares a word with a test value): call again with confirm_wording: true. Wording edited in an earlier session can't be checked that way: save_template then answers confirm_wording_needed with the changed ids and properties; review that wording (preview_page shows labels) and call again with confirm_wording: true. An unsaved analysis can't be saved: analyze it again with save_as_template: true (no page scans on a native-field PDF; otherwise it costs scans again), then edit that template.

Inputs

Returns

The saved template's field_count (the whole template). With nothing to save: saved: false, nothing_to_save: true. Refuses with template_conflict, answer_in_template or confirm_wording_needed instead of sending.

Example

{  "template_id": "6c1d2e8a-4b7f-4e21-9a3c-5d0e7f8b9a12"}

Re-analyze pages of a saved template. Re-run fenfill's analysis on some pages of a SAVED template, using the blank PDF already stored with it (nothing is uploaded). Spot never-analyzed pages with get_template (unanalyzed_pages) or list_templates (analyzed_pages vs page_count). kind: "scratch" (default; only allowed when the pages have no fields) analyzes a never-analyzed page, or replaces a badly analyzed one's fields; "find" adds blanks the first pass missed and keeps everything else; "relabel" re-derives labels, types, groups and sections keeping the boxes (relabel may reset table column types/orientation; check get_template after); "label_missing" fills in only missing labels. Cost: 1 page scan per page; label_missing may use none (get_account shows what is left). Pass estimate: true first to price it (starts nothing). Unsaved local edits (edit_template) must be saved (save_template) or dropped (discard: true) first. Returns the pages' changes (added / removed / changed fields) and their new fields. If it returns status "running", call it again with the same arguments (no extra charge). A rate-limit or busy refusal is waited out automatically (up to about a minute).

Inputs

Returns

Per changed page, the fields added, removed and changed, then the new fields of those pages. With estimate: true it prices the run and starts nothing. status: "running" means call again with the same arguments.

Example

{  "template_id": "6c1d2e8a-4b7f-4e21-9a3c-5d0e7f8b9a12",  "pages": "2",  "kind": "find",  "estimate": true}