How to connect Stannp to OpenClaw
Connect Stannp to OpenClaw with ClawLink: paste your Stannp key once and 32 tools work from chat. No MCP server to run, nothing stored on your machine.
StannpAPI KEYMCPStannp provides a direct mail API enabling users to send postcards and letters programmatically.. Once connected, OpenClaw can read and act on Stannp from chat — pairing, token refresh, and tool wiring handled for you.
The usual route to Stannp access for OpenClaw is an MCP server you configure and keep running, plus your own OAuth app or API keys. ClawLink gives OpenClaw a more practical Stannp setup: install one ClawHub skill, connect Stannp in the browser, and OpenClaw can call real Stannp actions from any chat surface with no auth, token refresh, or tool wiring to build yourself.
Setup
It takes three steps to connect OpenClaw to Stannp.
1Install the plugin
Paste the setup prompt into OpenClaw, or install from the terminal and ask OpenClaw to pair:
openclaw plugins install clawhub:clawlink-plugin- 2
Connect Stannp
Paste your API key in the dashboard.
- 3
Use it from chat
Ask OpenClaw: "What can you do with Stannp?"
Install by command
The setup prompt above does all of this in one paste. By hand, it is one install command plus a browser approval:
openclaw plugins install clawhub:clawlink-pluginThen ask OpenClaw to set up ClawLink. It starts browser pairing and prints an approval link — open it, approve the device, return to the chat, and say done. Finally, connect Stannp in the ClawLink dashboard — paste your Stannp API key once.
Verify the connection by asking OpenClaw:
Create it in Stannp for me, then confirm the important fields before you finish.
Using a different agent?
The OpenClaw plugin is one client of ClawLink's MCP server. Claude Code, Cursor, Codex, or any agent that can run a shell command pairs with the same ClawLink account through the CLI:
npx -y @useclawlink/cli loginlogin opens the same browser approval and stores a credential locally. Once Stannp is connected in the dashboard, that agent calls the same 32 Stannp tools over MCP. Full setup for MCP clients and shell agents: connect apps to any AI agent.
Stannp MCP for OpenClaw
Looking for a Stannp MCP server for OpenClaw? ClawLink connects Stannp to OpenClaw and exposes 32 Stannp tools your agent can call over MCP, with hosted auth and nothing to run or maintain yourself. Using Hermes instead? The Hermes Stannp integration works the same way.
What the OpenClaw Stannp integration can do
32 Stannp tools are ready for OpenClaw once the account is connected. The 29 below are the ones people reach for most; your agent can call all 32.
29 of 32 Stannp tools for OpenClaw
| Tool | What it does |
|---|---|
Create campaign sample stannp_create_campaign_sample | Produce a PDF sample of your campaign |
Get account balance stannp_get_account_balance | Retrieve the current account balance |
Get campaign stannp_get_campaign | Retrieve details of a specific campaign |
Get campaign available dates stannp_get_campaign_available_dates | Get available dates for scheduling a campaign (up to 30 days) |
Get campaign cost stannp_get_campaign_cost | Get the estimated cost of booking a campaign |
Get contact stannp_get_contact | Retrieve details of a specific contact |
Get current user stannp_get_current_user | Get information about the currently authenticated user including rate limit status |
Get reporting summary stannp_get_reporting_summary | Get a status summary on individual items within a date range |
List campaigns stannp_list_campaigns | Get a list of all campaigns |
List contacts stannp_list_contacts | List all contacts |
List folders stannp_list_folders | Get a list of folders in your secure file transfer area |
List groups stannp_list_groups | Get a list of mailing groups on your account |
List mailpieces stannp_list_mailpieces | Retrieve mailpiece objects sent within a date range |
List templates stannp_list_templates | List all templates associated with the account |
Validate address stannp_validate_address | Validate a postal address |
Add recipient to group stannp_add_recipient_to_group | Add a recipient to a recipient group |
Add recipients to group stannp_add_recipients_to_group | Add existing recipients to a mailing list group |
Create campaign stannp_create_campaign | Create a new direct mail campaign on the platform |
Create folder stannp_create_folder | Create a folder in your secure file transfer area |
Create group stannp_create_group | Create a new recipient group in Stannp |
Create letter stannp_create_letter | Create a letter with mail merge to insert address and variable data |
Create postcard stannp_create_postcard | Create a postcard |
Create selection stannp_create_selection | Create a new recipient selection for targeting in Stannp |
Import recipients stannp_import_recipients | Import recipients from a CSV or XLS file into a Stannp recipient group |
Merge pdfs stannp_merge_pdfs | Merge multiple PDF files into a single file |
Recalculate group stannp_recalculate_group | Recalculate a group to ensure stats are up to date |
Upload file stannp_upload_file | Upload a file to your secure file transfer area |
Cancel postcard stannp_cancel_postcard | Cancel a postcard if processing has not started yet |
Remove recipients from group stannp_remove_recipients_from_group | Remove recipients from a group without deleting them |
Try it: find the Stannp tool you need
Browse the 29 Stannp tools
Click any tool to see exactly what OpenClaw can do and copy a ready-to-use prompt.
Example prompts
Create it in Stannp for me, then confirm the important fields before you finish.
Pull the relevant data from Stannp, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Stannp, summarize it in plain English, and point out anything that needs attention.
Pull the relevant data from Stannp, summarize it in plain English, and point out anything that needs attention.
ClawLink vs. building it yourself
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Stannp working from chat.
| Manual | ClawLink | |
|---|---|---|
| Credential handling | Collect, validate, store, and rotate the Stannp API key yourself, then make sure every tool call uses the right account. | Users complete the hosted ClawLink setup once and the connected Stannp account becomes available to the agent without you building credential management. |
| Ongoing maintenance | You own refresh logic, permission debugging, environment config, and every provider-specific edge case for Stannp. | ClawLink handles the repetitive integration plumbing so your team can focus on the workflow instead of the infrastructure. |
| Agent usability | You still need to expose the right Stannp actions to the runtime in a format your agent can reliably use. | 32 tools for Stannp are already exposed through ClawLink, so the agent can read and act from chat immediately. |
ClawLink vs. Composio
Composio also exposes Stannp to AI agents. It is developer infrastructure: Python and TypeScript SDKs, an MCP server, and a catalog past 1,000 apps, aimed at teams shipping agent products. ClawLink is built for OpenClaw users instead. You install the plugin once, connect Stannp in the browser, and the 32 tools above work from chat. There is no SDK and no config file, and the Stannp key you paste at setup is stored server-side rather than kept in your environment. Choosing between them? Read the full Composio alternatives comparison.
Troubleshooting
OpenClaw installed the Stannp skill but can't call the tools
The ClawHub skill teaches OpenClaw about Stannp, but the calls run through the ClawLink plugin and your connected account. Make sure Stannp is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
Connection succeeds but no tools appear
Reconnect Stannp from the dashboard, then start a fresh chat if the runtime still has the old tool catalog loaded.
"Tool schema not loaded yet" error when calling Stannp tools
Stannp tool schemas load on demand the first time a tool runs and are cached after that, so this error usually clears on its own: wait a few seconds and retry the same request. If every Stannp call keeps failing with it in a fresh chat, reconnect from the dashboard, and contact support if it still persists — that pattern points to a configuration problem on our side, not something you can fix by reconnecting again.
Stannp returns 403 or "permission denied" on one action while others work
Two usual causes. The connected account may not have access to the specific workspace, inbox, store, or project in the request — check that first. If access looks right, the agent may have sent a placeholder value (like "YOUR_ID" or an example id from documentation) instead of a real one: ask it to run a list or search tool first, then retry the action with a real id from those results. Most failures at this stage are one of these two, not ClawLink bugs.
API key setup works but results look incomplete
Double-check that the API key for Stannp has the right scopes or account access. A valid key can still be too limited for some reads or writes.
FAQ
Is there a OpenClaw Stannp integration?
Yes. ClawLink is the fastest way to connect OpenClaw to Stannp: link your Stannp account once in the browser and OpenClaw can call the Stannp API through 32 ready-made tools — no custom code or token handling.
How do I add Stannp to OpenClaw with ClawLink?
Paste the setup prompt from this page into OpenClaw. It installs the ClawLink Stannp skill from ClawHub, then you click Connect in the dashboard to authorize Stannp. OpenClaw calls the tools from the next message — no config files, and the Stannp key you paste is stored server-side instead of in your environment.
How long does it take to connect Stannp to OpenClaw?
About two minutes. Sign in, click Connect next to Stannp in the dashboard, authenticate, and OpenClaw can use it from the next chat message.
Why use ClawLink instead of wiring Stannp up myself?
The alternative to ClawLink is usually manual API key setup plus your own token handling, permission troubleshooting, and tool plumbing for OpenClaw. That is fine if you want to build and maintain the integration yourself. Most teams just want Stannp working from chat.
OpenClaw installed the Stannp skill but can't call the tools
The ClawHub skill teaches OpenClaw about Stannp, but the calls run through the ClawLink plugin and your connected account. Make sure Stannp is connected in the dashboard, then start a fresh chat so OpenClaw reloads the tool catalog. If OpenClaw runs as a persistent gateway, restart it so the new tools register.
