DocuPost for AI agents
DocuPost is a print-and-mail service that turns digital files into physical letters and postcards sent through the U.S. Postal Service. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in DocuPost.
Send a letter to a customer
Send a letter built from a digital file to a customer's mailing address once content is approved.
Check account balance first
Read the account balance before sending a batch of mail to confirm there are enough funds.
Approve before a postcard mailing
Route a postcard send through approval, since a physical mailing cannot be recalled once it ships.
3 DocuPost actions, graded by risk.
Every DocuPost action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
1Look things up. Allowed by default.
- docupost.get_balanceGet Account Balance
write
2Create and change things. Allow, or ask the user first.
- docupost.send_letterSend Letter
- docupost.send_postcardSend Postcard
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
DocuPost in three steps.
- 01Your users connect DocuPostThey add their DocuPost api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “send Letter” can wait for the user to approve.
- 03Any agent can actYour agent calls DocuPost through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('docupost', { read: 'allow', write: 'ask', // send_letter destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How DocuPost connects.
Users add their DocuPost api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same DocuPost connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use DocuPost from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
DocuPost and Arc0, answered.
Can I use DocuPost with Claude, ChatGPT or Cursor?
Yes. Connect DocuPost to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the DocuPost actions you allow.
How do users connect DocuPost?
Users add their DocuPost api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which DocuPost actions can my agent take?
3 in total: 1 read, 2 write and 0 destructive, such as “send Letter”. Your policies decide which of them each agent may call.
Can I make my agent read-only in DocuPost?
Yes. Allow read actions and deny writes in the DocuPost policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call DocuPost too?
Yes. The same DocuPost connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug DocuPost into your agent.
Your users connect DocuPost once, under your brand. Your agent gets 3 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan