Reference
MCP tools reference
Login with the human account. Pass the short session token on later calls. Create jobs and proofs. Approve on the app to spend the meter. Ask the live MCP server for the tool list. Do not invent names.
What agents can do
This page is English capabilities, not a schema dump. The live list is on the MCP server after login. Names change. The jobs below do not.
Login
Account email and password from the environment. Returns a short-lived session token. Pass that token on later mail tools. On auth failure, log in again.
If login fails, check env, then retry login. Do not paste the password into chat to recover.
Create, upload, configure
Create a job. Upload documents and lists. Set First-Class, Certified, print options. Same production path as the portal.
Documents and postcards. Statement or invoice jobs are uploaded files and lists, not bills we generate inside a core. Certified is not for postcards. Add proof options before you approve. A list is recipient data. Handle it under your policies. Do not paste the file into a public prompt.
Mixed lists are valid: some rows have a person and a company; some have only a name (the name is the company). Empty company on those name-only rows is correct. After ingest, read the digested rows. Column maps alone are not proof the company values arrived.
Proof and status
Generate proof. List and get jobs. Read meter balance. Tracing on qualifying First-Class pieces is not tracking.
Proof is the review surface. If it looks wrong, fix the job before you approve. We do not rewrite the document you uploaded. Status is where the draft sits. Meter balance tells you whether approve on the app can cover the job. It is not a public price list.
Cancel draft
Cancel a draft before a human approves. After approve, production has started. Do not treat cancel as a recall of printed mail. If you need to stop a draft the agent assembled, cancel it on the tools the server lists, or discard it on the app before you confirm.
Approve (postage)
A human on the app approves. That debit starts production. Agents do not run card deposits. Agents do not approve production mail.
Submit does not print
If the server exposes a submit or persist step, it stores the job. It does not print. It does not debit the meter. A human still approves on the app. That debit starts production. We then print, insert, apply postage, and deliver the pieces to USPS.
Until that confirm, the job is a draft. You can still change options, replace a file, or cancel. After confirm, the factory has the job. Physical mail cannot be unsent.
Sequence
human: register + fund meter in the app env: account email + password (never in the prompt) MCP: login → session token MCP: create / upload / proof MCP: persist stores a draft app: human approves → meter debit → we produce
Live names come from the MCP server tool list. Do not invent hostnames or add commands.
Operator walkthrough: Getting started. Why the human gate exists: MCP overview.
Live names after login
Ask the connected MCP server for its tool list. Use those names. Do not copy names from a gist, a screenshot, or an old chat. Do not invent public aliases on www.
This site will not publish mill tool names. This site will not publish an eight-name alias set. English is the contract here: login, create job, upload, proof, status, cancel draft.
Connection details come with access on the app.
Not included
- Standalone API keys (planned later)
- Unauthenticated public MCP
- Agent card deposits
- Agent approve of production mail
- A hostname or add command on this page
- A public schema of mill tool names
Same production path as the portal. Cutoffs and tracing live on How it works. Certified options: Certified Mail.
FAQ
What are the MCP tool names?
Do not invent tool names. The live list is on the MCP server after login. This page describes capabilities in English: login, create job, upload, proof, status, cancel draft.
Does submit print the job?
No. If the server exposes a submit or persist step, it stores the job. It does not print. A human approves on the app. That debit starts production.
Are mixed Name and Company lists valid?
Yes. Mixed files are valid. Some rows have a person and a company. Some have only a name (the name is the company). Empty company on those name-only rows is correct. After ingest, read the digested rows. Column maps alone are not proof the company values arrived.
Can the agent approve production mail?
No. Agents do not approve production mail. A human must approve on the app. Agents do not run card deposits.
Get started
MCP is available now on the app. Account + prepaid meter.