Send physical letters with OpenClaw and FrankKi MCP

Add physical mail to an OpenClaw workflow

An OpenClaw task may end with a document that needs to reach a postal address. FrankKi provides tools to turn that document into a printed letter, with a preview, a current shipping quote and an approval step. This guide covers the authenticated MCP connection for that workflow.

The setup follows official documentation checked on September 13, 2026. It has not yet been tested as a complete OpenClaw-to-FrankKi journey. Verify the connection and available tools before using it for correspondence.

Use the outbound MCP connection

Current OpenClaw documentation describes a native registry for external MCP servers. That is the route used here. openclaw mcp serve exposes OpenClaw to another client; it does not connect your agent to FrankKi. Older mcporter configurations belong to a separate registry. See OpenClaw MCP paths.

You need an OpenClaw installation with the documented MCP commands and a FrankKi account ready for MCP access. Start with the FrankKi MCP overview and developer documentation if the account is new.

Save, authenticate and probe the server

Use a new server name, or inspect your existing entry before changing it. Run these commands in the environment that runs OpenClaw. Complete the browser sign-in before the final command.

openclaw mcp set frankki '{"url":"https://mcp.frankki.app","transport":"streamable-http","auth":"oauth"}'
openclaw mcp login frankki
openclaw mcp doctor frankki --probe

Set transport explicitly to streamable-http. OpenClaw documents SSE as the default when that field is omitted. OAuth handles the sign-in; this example contains no API key. The command syntax and authentication flow are in OpenClaw transports and OAuth.

The probe tests a live connection and lists capabilities. It does not mail a letter. If the probe succeeds but your agent cannot see the tools, check its tool profile and policy. The documented minimal profile hides MCP tools. See OpenClaw server management before changing access.

Prepare one letter before automating a queue

Start with a single business letter whose content you can check easily. For example, a customer has asked for a printed confirmation of a service appointment. Supply the agreed date, reference and verified postal addresses. Ask the agent to use only those facts.

Prepare a printed confirmation for the appointment described below. Use FrankKi to create the draft, show the page preview and fetch the available delivery methods and prices for the recipient country. Ask me to review the letter. Wait for my approval before sending, then report the order status.

Check the address block, appointment details and every attachment in the preview. Choose from the delivery methods returned by the current quote. Registered mail is an option only where the destination-specific quote offers it. A tracked method is not automatically registered mail.

This is a proposed workflow, not a report of a customer send. Its completion condition is clear: the approved letter has an order status you can inspect. A generated draft or a successful connection probe is an earlier step.

Give recurring work a review point

If you later use the workflow for a queue of confirmations, keep each letter identifiable. Record the source request, the recipient, the approved document and the returned order reference in your own process. That gives you something concrete to check when a task resumes or a network call fails.

For this workflow, the human reviews and approves each letter in FrankKi. A timer or an instruction to process the queue is not that approval. After a timeout during a send-related action, check the existing order before asking for a new one.

The authenticated FrankKi account uses a prepaid wallet. Read business pricing for the account model, then fetch a current quote for each letter. The postal quote does not include any separate OpenClaw hosting or model charges.

Choose the first task carefully

A short confirmation is easier to review than a large batch or a letter with a disputed deadline. Prove the connection, inspect one document and follow its status. Once those steps work in your installation, you have a concrete basis for deciding which correspondence should use the same process.

Using Hermes Agent? Read the physical-mail setup guide.

Photo: Kampus Production / Pexels.