JustFill PDF Forms
The JustFill PDF Forms server lets AI agents detect, review, fill, and manage fields in PDF forms (including scanned images) programmatically.
Open & detect PDF fields: Open a PDF or scanned image (JPG/PNG/TIFF) and automatically detect fillable fields using saved templates, embedded AcroForm fields, or ML detection — with confidence scores for each field.
Preview fields: Render page images with color-coded field box overlays to visually verify placement (blue = deterministic, green/orange/red = ML confidence levels).
Preview filled output: See how the filled PDF will look with your values drawn in place — without consuming a fill credit or generating the actual PDF.
List fields: List all detected fields, optionally filtered to a specific page.
Add/Update/Remove fields: Manually correct detection errors (false negatives/positives) by adding, updating, or removing fields individually or in batch, including position, size, name, type, and text alignment.
Prune fields: Bulk-delete detection noise using combined criteria (field type, confidence threshold, size thresholds, page, or exclusions).
Fill PDF: Populate the PDF with provided values (field ID → text) and save the output file, with warnings for values that will be shrunk or truncated.
Save templates: Persist a reviewed field layout as a named, reusable template for fully deterministic future fills (confidence 1.0, no ML needed).
List templates: View all saved templates, including name, field count, and file hash.
Enables n8n workflows to detect, review, and fill PDF form fields through justfill.app, allowing automated PDF form processing with ML detection and template reuse.
JustFill MCP Server
Let AI agents (Claude, ChatGPT, n8n — any MCP client) detect, review and fill PDF form fields through justfill.app.
Excel or CSV batch workflow
If the source data is already in a spreadsheet and you need one filled copy of the same existing PDF per row, an MCP client is optional. The guided browser workflow imports XLSX or CSV, maps columns to reviewed PDF fields, previews each record, and exports the approved PDFs in a ZIP.
Try the five-row PDF mail merge sample — no card or sales call.
Related MCP server: DocImprint
Why agents can trust it
Source | Confidence | What it means |
Saved template | 1.0 | This exact PDF was filled before; geometry is human/agent-verified. No ML runs at all. |
AcroForm | 1.0 | The PDF has embedded form fields — read from the file, filled natively. |
ML detection | 0.0–0.95 | An honest draft. Review it visually ( |
ML confidence is calibrated: the detector's raw scores are not
probabilities (its server-side filter accepts boxes from raw ~0.02 and
auto-accepts at raw 0.15), so they are mapped onto 0–1 to mean what you'd
expect — ≥0.75 "detector is sure", 0.4–0.75 "probably right, glance at the
preview", <0.4 "borderline accept, verify". The raw detector score is kept
on each field as raw_score.
The correction loop (render_preview → add/update/remove_field) exists
precisely because ML detection has false positives and negatives. A false
positive costs nothing (leave it unfilled or remove it); a false negative is
visible on the preview and fixable with one add_field call. Once reviewed,
save_template makes every future fill of that form deterministic.
Setup
uv tool install ./mcp-server # or: pip install ./mcp-serverAuthorize once (opens the browser, one click while logged in to justfill.app):
justfill-mcp loginThen the config needs no credentials at all:
{
"mcpServers": {
"justfill": { "command": "justfill-mcp" }
}
}Alternatives, in the order the server checks them:
JUSTFILL_API_KEYenv — create a key at justfill.app → Account → API Keys and put"env": {"JUSTFILL_API_KEY": "jf_live_…"}in the config.The key saved by
justfill-mcp login(~/.config/justfill/credentials.json).JUSTFILL_EMAIL+JUSTFILL_PASSWORD— legacy fallback; an API key is better (no password in config files, revocable per client, never expires mid-session).
Tools
open_pdf(path, min_confidence=0.0, max_pages=10, force_detect=False)— template → AcroForm → ML resolution order. Accepts scanned images too (jpg/png/tiff → converted to PDF, deterministically, so templates still match).force_detect=Trueignores a saved template and re-runs ML.render_preview(page_index)— page image with labeled field boxes (blue = deterministic, green/orange/red = ML confidence)render_filled_preview(values, page_index)— the same page with your values drawn in place (checkboxes get an X). Costs no fills — check before you fill.list_fields(page_index?)add_field(x, y, w, h, name, page_index, field_type, align?, vertical_align?)— coords in % of page, top-left originupdate_field(field_id, …)/remove_field(field_id)update_fields([{field_id, …}, …])/remove_fields([ids])— batch versionsprune_fields(field_type?, confidence_below?, width_below?, height_below?, page_index?, exclude_ids?)— bulk-delete detection noise in one call (criteria AND-ed, removed ids returned)fill_pdf(values, output_path, flatten=True)—values={field_id: text}; responds withwarningsfor values that will be shrunk/truncated to fitsave_template(name)— persist the reviewed layout for deterministic repeat fillslist_templates()
Text alignment: align = left|center|right, vertical_align =
top|middle|bottom — set per field (e.g. right for RTL forms, center for
boxed digits). Persisted in templates.
Example agent flow
open_pdf("~/forms/w-9.pdf") → acroform, 27 fields, confidence 1.0
fill_pdf({"f1": "Jane Doe", …}, "~/out/w-9-filled.pdf")open_pdf("~/forms/scan.jpg") → converted to PDF; ml, 34 fields
render_preview(0) → agent sees noise + one missed line
prune_fields(field_type="cell", width_below=3) → 16 removed in one call
add_field(x=18, y=62.5, w=40, h=3, name="Phone")
render_filled_preview({…}) → values sit right, no overflow
fill_pdf({…}, "~/out/filled.pdf")
save_template("Client intake form") → next time: deterministicNotes
Auth is a regular justfill.app account; tokens auto-refresh on expiry.
Usage and document-output rules are enforced by the same account service as the web app.
fill_pdfreports whether the output is clean or watermarked.One PDF open at a time per server session (by design — keeps ids stable).
This repository mirrors released versions of the MCP client (development happens in a private monorepo alongside the justfill.app backend). Bug reports and feature requests are very welcome in the issue tracker here.
Maintenance
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mrmaciej1/justfill-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server