Tave for AI agents
Tave is studio management software for photographers, tracking clients, jobs, invoices, and events from booking through delivery. 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 Tave.
Create a new job for a client
Set up a job record with its event type and contact details after a client books a shoot.
Log a note on a client file
Add a note to a client's address book entry to record a call or preference.
Confirm before applying a payment
Check the amount and order before applying a payment to a job, since it changes the client's balance on record.
129 Tave actions, graded by risk.
Every Tave action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
58Look things up. Allowed by default.
- tave.get_brandGet Brand
- tave.get_eventGet Event
- tave.list_filesList Files
- tave.get_galleryGet Gallery
- tave.list_brandsList Brands
- tave.list_eventsList Studio Events
- tave.get_event_typeGet Event Type
- tave.get_resource_jobGet Job
- tave.list_event_typesList Event Types
- tave.get_resource_noteGet Note
- tave.get_resource_userGet User by ID
- tave.list_address_bookList Address Book Contacts
- tave.list_resource_jobList Resource Job
- tave.get_resource_orderGet Order
- tave.list_resource_noteList Resource Note
- tave.list_resource_userList Resource User
write
47Create and change things. Allow, or ask the user first.
- tave.create_userCreate User
- tave.create_brandCreate Brand
- tave.update_brandUpdate Brand
- tave.create_galleryCreate Gallery
- tave.update_event_typeUpdate Event Type
- tave.create_custom_fieldCreate Custom Field
- tave.create_resource_jobCreate Job
- tave.update_address_bookUpdate Address Book Entry
- tave.update_resource_jobUpdate Job
- tave.create_discount_typeCreate Discount Type
- tave.create_resource_fileCreate File
- tave.create_resource_noteCreate Note
- tave.update_resource_noteUpdate Note
- tave.update_resource_userUpdate User
- tave.create_resource_eventCreate Event
- tave.update_resource_eventUpdate Event
destructive
24Delete, cancel or archive. Ask first, or deny outright.
- tave.delete_brandDelete Brand
- tave.delete_galleryDelete Gallery
- tave.delete_event_typeDelete Event Type
- tave.delete_custom_fieldDelete Custom Field
- tave.delete_resource_jobDelete Job
- tave.delete_resource_noteDelete Note
- tave.delete_resource_userDelete User
- tave.delete_resource_eventDelete Event
- tave.delete_resource_productDelete Product
- tave.delete_resource_discountDelete Discount
- tave.delete_resource_job_roleDelete Job Role
- tave.delete_resource_job_typeDelete Job Type
- tave.delete_resource_paymentsDelete Payment
- tave.delete_resource_tax_rateDelete Tax Rate
- tave.delete_address_book_entryDelete Address Book Entry
- tave.delete_resource_rest_hookDelete RestHook
Tave in three steps.
- 01Your users connect TaveThey add their Tave api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create User” can wait for the user, and “delete Brand” can be denied outright.
- 03Any agent can actYour agent calls Tave through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('tave', { read: 'allow', write: 'ask', // create_user destructive: 'deny', // delete_brand }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Tave connects.
Users add their Tave 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 Tave 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 Tave from any agent.
Tave and Arc0, answered.
Can I use Tave with Claude, ChatGPT or Cursor?
Yes. Connect Tave 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 Tave actions you allow.
How do users connect Tave?
Users add their Tave 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 Tave actions can my agent take?
129 in total: 58 read, 47 write and 24 destructive, such as “create User”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Tave?
Yes. Actions like “delete Brand” 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 Tave too?
Yes. The same Tave connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Tave into your agent.
Your users connect Tave once, under your brand. Your agent gets 129 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan