Justfill Pdf Forms

MCP开发工具

提供方 mrmaciej1

开发工具 未标注 OAuth 授权 社区 / 第三方 ClaudeCursorCodexZed

Fill any PDF form with AI agents — ML field detection on scans, visual review loop, reusable templates, and native AcroForm fill via justfill.app.

一句话选型结论

按资料字段整理

Justfill Pdf Forms 属于开发工具类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Claude、Cursor、Codex 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类开发工具 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

开发工具
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

pdfformsautomation

安装与配置

未标注 OAuth 授权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
代码与仓库操作

在对话里直接查代码、提 issue、走 PR,省掉来回切工具。

本地命令与脚本

把构建、测试、格式化这类重复命令交给模型执行。

接口联调与测试

让模型调你的接口、跑一遍用例,快速定位问题。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude、Cursor、Codex,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在开发工具场景里让模型直接调用外部能力的人。
  • 已经在用 Claude、Cursor 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Justfill Pdf Forms当前 未标注 未标注 未标注 无 未标注
Git 838e2ec1 12 stdio · 本地进程 本地部署 有 2026-05-17
Markitdown MCP 2c653a5f 1 stdio · 本地进程 本地部署 有 2026-05-17
JavaGuide 未标注 stdio · 本地进程 本地部署 有 2026-04-11
awesome-claude-skills 未标注 stdio · 本地进程 本地部署 有 2026-04-26
Context7 831acf40 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

开发工具
字段来自项目仓库与公开索引,中文说明由本站标注
提供方mrmaciej1上游标注的维护方 mrmaciej1
分类开发工具本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · python本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

8.7 KB
来自项目仓库与上游目录的原文,未做删改

JustFill MCP Server

Let AI agents (Claude, ChatGPT, n8n — any MCP client) detect, review and fill
PDF form fields through justfill.app.

Fill PDF forms in ChatGPT

Install the published JustFill PDF Forms plugin
from the ChatGPT plugin directory, then connect your JustFill account. This
hosted path does not require installing the Python client or configuring an
MCP server manually.

Try this prompt with the one-page, six-field sample:```text
Use JustFill to open https://justfill.app/examples/chatgpt/project-intake.pdf.
List its fields and show a preview. Do not fill anything yet.


Ask for a filled preview with fictional values and approve it before generating
the PDF. Save the reviewed layout, then open the same original blank PDF for
the next client or project. Your saved template is available in the same
JustFill account; generated files follow that account's plan.

Try the two-project example and download the real editable results.
The example includes prompts for two fictional clients, the blank PDF, and
two generated PDFs with their free-output watermark.

## Hosted server — no local installation

If your MCP client supports remote servers with OAuth, use this server URL:```text
https://justfill.app/api/mcp

Connect from your client, sign in to JustFill, and review the access request.
You do not need to install the Python package or copy an API key for this path.
Access can be revoked in JustFill under Account → API Keys.

Connection guide.
The client is MIT-licensed; PDF processing uses your JustFill account's allowance.
For a first check, use a blank form and fictional values, and review the filled
preview before exporting. Save the reviewed layout to reuse it with new data
when the same form comes up again.

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.

Import-ready n8n workflows

Start with the
deterministic workflow JSON in this repository.
It collects a PDF and JSON payload, reuses the reviewed field names saved for
that exact form, fills the original layout and returns a temporary download
link.

The workflow is listed in the
n8n template library.
For new runs, import the current strict-mapping JSON from this repository,
which includes the synthetic fixture and validation evidence alongside it.
The workflow is free to download; running it uses a JustFill account and its
PDF-processing allowance. It uses built-in nodes, not the separate JustFill
community node.

The repository also includes the exact deterministic workflow JSON, synthetic
test PDF, production evidence and a separate two-pass vision workflow for an
unfamiliar form. Both call the hosted MCP endpoint with standard HTTP Request
nodes and can be inspected before adding credentials.

Inspect the source workflows and evidence, or follow the
step-by-step n8n setup.

Business example: recurring supplier intake

An operations team can keep the supplier's required intake PDF unchanged,
save its reviewed field layout once, and let n8n map approved vendor data from
a webhook or CRM record into that exact form. The workflow returns a temporary
filled-PDF link that can be reviewed before it is uploaded to Drive, attached
to a draft email, or written back to the vendor record. The repository's
synthetic supplier-intake PDF exercises this exact path without customer data.

Gemini CLI extension

Install the same reviewed MCP tools plus the included PDF workflow guidance:```bash
gemini extensions install https://github.com/mrmaciej1/justfill-mcp


The extension manifest lives at the repository root and uses the published
`justfill-mcp` package. Gemini CLI asks for normal third-party extension consent
before enabling it.

## 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 (`render_preview`), fix it, then `save_template` to lock it in. |

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.

## Local client setup```bash
uv tool install justfill-mcp

Authorize once (opens the browser, one click while logged in to justfill.app):```bash
justfill-mcp login


Then the config needs no credentials at all:```json
{
  "mcpServers": {
    "justfill": { "command": "justfill-mcp" }
  }
}

For a zero-install configuration, use uvx directly:```json
{
"mcpServers": {
"justfill": {
"command": "uvx",
"args": ["justfill-mcp"]
}
}
}


Alternatives, in the order the server checks them:

1. `JUSTFILL_API_KEY` env — create a key at justfill.app → Account → API Keys
   and put `"env": {"JUSTFILL_API_KEY": "jf_live_…"}` in the config.
2. The key saved by `justfill-mcp login` (`~/.config/justfill/credentials.json`).
3. `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=True` ignores 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 origin
- `update_field(field_id, …)` / `remove_field(field_id)`
- `update_fields([{field_id, …}, …])` / `remove_fields([ids])` — batch versions
- `prune_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 with `warnings` for values that will be shrunk/truncated to fit
- `save_template(name)` — persist the reviewed layout for deterministic repeat fills
- `list_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: deterministic

Notes

  • 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_pdf reports 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.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Justfill Pdf Forms 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Justfill Pdf Forms 怎么在 Claude、Cursor、Codex 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Justfill Pdf Forms 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Justfill Pdf Forms 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Justfill Pdf Forms 支持哪些客户端?

资料标注支持 Claude、Cursor、Codex、Zed;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Justfill Pdf Forms 能提供哪些能力?

资料显示能力标签包括 pdf、forms、automation、ocr、ai agents。具体工具清单以官方文档为准。

Justfill Pdf Forms 需要什么运行环境?

运行时为 python。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。