Amcards for AI agents
AMCards lets businesses send personalized greeting cards and gifts through automated mailing campaigns, using templates and contact lists to keep customer relationships personal at scale. 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 Amcards.
Browse card templates by category
List public templates within a category before choosing a design for a campaign.
Look up a contact first
Find a contact record to confirm the mailing details are current before sending.
Check available gift options
List gifts that can be attached to a card before including one in an order.
10 Amcards actions, graded by risk.
Every Amcards action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
10Look things up. Allowed by default.
- amcards.get_giftGet Gift
- amcards.get_cardsGet Cards
- amcards.list_giftsList Gifts
- amcards.get_categoryGet Category
- amcards.get_contactsGet Contacts
- amcards.get_api_schemaGet API Schema
- amcards.list_categoriesList Categories
- amcards.get_category_schemaGet Category Schema
- amcards.get_public_templateGet Public Template
- amcards.list_public_templatesList Public Templates
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Amcards in three steps.
- 01Your users connect AmcardsThey add their Amcards api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Amcards through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('amcards', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Amcards connects.
Users add their Amcards 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 Amcards 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 Amcards from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Amcards and Arc0, answered.
Can I use Amcards with Claude, ChatGPT or Cursor?
Yes. Connect Amcards 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 Amcards actions you allow.
How do users connect Amcards?
Users add their Amcards 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 Amcards actions can my agent take?
10 in total: 10 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Amcards?
Yes. Allow read actions and deny writes in the Amcards policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Amcards too?
Yes. The same Amcards connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Amcards into your agent.
Your users connect Amcards once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan