MCP server for terminal commands, file operations, and process management
Mail Merge PDF is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Mail Merge PDF: the site's own MCP server — checker, enquiry (enquiry = a human handoff, not a...
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http mail-merge-pdf-mcp https://mailmergepdf.com/mcp
# 2 — ask your agent for something these tools do
# checker_start, checker_answer, checker_tree and 3 more
Mail Merge PDF costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http mail-merge-pdf-mcp https://mailmergepdf.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
6 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
The first question of the Which mail merge to PDF route? decision guide.
No parameter schema on file.
Given a question id and the chosen option (its choice index), return the next question or the final verdict.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| question | string | yes | — |
| choice | integer | yes | — |
Every question, option and verdict of the Which mail merge to PDF route? guide, for reasoning end to end.
No parameter schema on file.
Read first. States plainly what submit_enquiry does on Mail Merge PDF: it starts an enquiry with human providers who quote directly. Nothing is bought, ordered or paid; no quote is guaranteed; it is free. Also returns who receives the details, the consent wording, and how the person confirms.
No parameter schema on file.
Every field of the Mail Merge PDF enquiry: key, label, type, whether required, help text and the allowed options where there are any. Pass answers to submit_enquiry keyed by field key.
No parameter schema on file.
Submits an enquiry to Mail Merge PDF — NOT a purchase, NOT a guaranteed quote. Step 1: call with the answers (keyed by field key from enquiry_fields) and consent=true; it validates and returns a summary, the consent line and a confirmation token — show the person the summary and the consent line. Step 2: only if the person agrees, call again with the same answers, consent=true and the confirmation
| Parameter | Type | Required | Notes |
|---|---|---|---|
| answers | object | yes | the person's answers, keyed by field key |
| consent | boolean | yes | true only when the person has agreed to: Send my contact details to up to three document and data extraction software suppliers, chosen by Mail Merge PDF, who'll contact me directly. I'll be emailed e |
| confirmation | string | no | the confirmation token from step 1, after the person has approved the summary |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Mail Merge PDF or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Mail Merge PDF can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.