Gelato for AI agents
Gelato is a print-on-demand platform for creating and fulfilling orders, browsing products, and checking stock and shipping options, used by ecommerce sellers who don't hold inventory. 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 Gelato.
Check stock availability
Check stock availability for a product before confirming an order can be fulfilled.
Create a draft order
Create a draft order for a customer's design so it can be reviewed before it prints.
Confirm before submitting an order
Require approval before submitting a draft order, since it commits to production and billing.
13 Gelato actions, graded by risk.
Every Gelato action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- gelato.get_orderGet Order
- gelato.get_productGet Product
- gelato.get_catalogsGet Catalogs
- gelato.search_ordersSearch Orders
- gelato.search_productsSearch Products
- gelato.get_product_pricesGet Product Prices
- gelato.check_stock_availabilityCheck Stock Availability
write
4Create and change things. Allow, or ask the user first.
- gelato.create_orderCreate Order
- gelato.create_draft_orderCreate Draft Order
- gelato.quote_orderQuote Order
- gelato.submit_draft_orderSubmit Draft Order
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- gelato.cancel_orderCancel Order
- gelato.delete_draft_orderDelete Draft Order
Gelato in three steps.
- 01Your users connect GelatoThey add their Gelato api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Order” can wait for the user, and “delete Draft Order” can be denied outright.
- 03Any agent can actYour agent calls Gelato through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('gelato', { read: 'allow', write: 'ask', // create_order destructive: 'deny', // delete_draft_order }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Gelato connects.
Users add their Gelato 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 Gelato 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 Gelato from any agent.
Gelato and Arc0, answered.
Can I use Gelato with Claude, ChatGPT or Cursor?
Yes. Connect Gelato 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 Gelato actions you allow.
How do users connect Gelato?
Users add their Gelato 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 Gelato actions can my agent take?
13 in total: 7 read, 4 write and 2 destructive, such as “create Order”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Gelato?
Yes. Actions like “delete Draft Order” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Gelato too?
Yes. The same Gelato connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Gelato into your agent.
Your users connect Gelato once, under your brand. Your agent gets 13 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan