FrankKiMCPOne endpoint gives your agent a printer, an envelope, and a postbox. It drafts the letter, gets an exact destination quote, waits for your approval unless you switch on autopilot, and tracks the dispatch. After approval, real paper is delivered worldwide where the destination policy and postal partner allow it.
OAuth sign-in for Claude and ChatGPT · Scoped API keys for scripts · No subscription
Claude, Claude Desktop and Claude Code sign in over OAuth: add the URL, choose "Sign in now", sign in or create your FrankKi account, and allow access. You only need a scoped API key for scripts and servers. Every physical dispatch needs your approval unless you switch on autopilot.
Choose your app. The setup prompt stays visible in case your browser blocks the handoff.
On a Team or Enterprise plan an owner adds it once under Organization settings > Connectors ("Add", then Custom > Web). Everyone else clicks "Connect" on it under Customize > Connectors.
Claude opens with the setup prompt filled in. Add the connector first, then press Send.
Setup promptConnect FrankKi at https://mcp.frankki.app so we can send letters by post. Ask me before you connect or grant permissions. Then run the FrankKi connection check mcp_health to see what my account still needs, and walk me through the setup step by step. Take our sender details and brand from our website and ask me once before you save them. Copy 1 to 3 templates that fit my business and show me one preview. For steps only I can do, such as a top-up, give me the link. Without my approval you send nothing and pay for nothing. Never switch on autopilot yourself.claude mcp add --transport http frankki https://mcp.frankki.app
# headless, with an API key
claude mcp add --transport http frankki https://mcp.frankki.app \
--header "Authorization: Bearer ${FRANKKI_API_KEY}"Draft, quote, submit for approval. A human reviews the rendered letter, exact price and service before dispatch. The agent never touches a printer, never guesses a price, and cannot spend past the cap you set on the call.
Composition is text-first. You hand over content and a recipient; FrankKi renders a correctly laid-out DIN 5008 document. After your approval, or after a 10-minute cancel window on autopilot, it prints, franks it, and hands it to the postal network.
Plain text plus a recipient. Back comes a rendered preview, letterhead and signature applied.
The exact, live cost for that destination and service level, before anything is committed.
Creates the final preview, reserves the quoted cost and queues the letter for explicit human approval. Nothing is printed yet.
After approval: printed, posted, delivered where supported. A verified posting record is available where the selected service provides one.
Read tools return state and never cost money. Action tools are explicit about what they change. Your agent can gate on the annotation.
Beyond the core flow: attachments, letterheads and signatures, sender profiles, send presets, scheduled sends, cancellation, posting receipts, client lookups, and GoBD or DATEV archive exports. The authoritative list is always what the server returns from tools/list.
Every submitted send has a status your agent can poll. After approval it is printed, franked, posted, and delivered where the destination supports it. A verified order_einlieferungsbeleg can provide an archived proof-of-posting record. That records postal acceptance, not the legal effectiveness of the letter.
Sending paper is irreversible and it costs money, so the platform is cautious by default. Four independent limits, each of which alone stops a runaway loop.
There are no post-paid invoices. Every paid send draws from a balance you topped up, so the absolute worst case is bounded by what is in the account.
Pass a ceiling with order_send. If the live server price exceeds it, nothing is printed and nothing is charged.
Every physical letter enters the approval queue. A human reviews the preview, exact price and service, then explicitly approves it through approval_decide before dispatch. If you switch on autopilot in the dashboard, letters from your released templates to known recipients go out after a 10-minute cancel window instead, within the daily and monthly limits you set. Rejection leaves the letter unprinted, and every decision is logged.
Each API key carries an allowed-tools scope and its own spending limit, so the reach of a leaked key is decided in advance.
Drafts, previews, quotes and a dryRun rehearsal cost nothing. A dryRun runs the same checks and pricing as a real send and returns page 1 as an image, with nothing printed and nothing charged. It needs the signed data processing agreement first. Money only moves when you approve a real letter.
Create an accountIf you send a few letters a month, a German standard letter in black and white is EUR 1.99. From 20 letters a month every letter that month is EUR 1.89, from 100 it is EUR 1.79, from 500 EUR 1.69, and from 1,000 letters EUR 1.59. The rung your volume reaches applies to every letter that month, including the first. Everything else is priced per destination and quoted live before the send. No subscription: top up from EUR 10 to EUR 500 per top-up through Stripe, and the balance does not expire. No company needed, freelancers and sole traders sign up too.
Prices are authoritative from the server. Call shipping_quote for the live figure, always, before order_send.
Measured on a trailing 30 days. The rung your volume reaches applies to every letter that month, including the first. Colour and registered products step down at the same five thresholds: EUR 2.09, EUR 5.99 and EUR 6.39 under 20 letters a month, EUR 1.69, EUR 5.59 and EUR 5.99 from 1,000.
Most automations stop at "now a human prints this and walks to a postbox". These are the ones that no longer have to.
Queue a printed reminder from an email event, with the amount and due date merged per debtor.
Cancellations, terminations and objections where physical mail is appropriate, sent as registered mail where the destination supports it.
Welcome letters, contract confirmations and account notifications, triggered by your own backend events.
Authority correspondence and regulated notices, archived with retrievable posting records where the selected service provides them.
Letter data is processed in the EU. FrankKi helps you draft, format and send physical letters, but it does not determine whether a letter is legally sufficient or effective. DIN 5008 describes layout, not legal effect. Posting records and delivery evidence are separate, and you remain responsible for content, recipient, authority, form, signature and deadlines. FrankKi provides no legal advice or individual legal assessment.
Connect Claude and create your account in the sign-in window, or sign up first. Nothing to self-host, drafts and dryRun rehearsals are free, and every real dispatch needs your approval unless you switch on autopilot.