Supersaas for AI agents
SuperSaaS is appointment and resource scheduling software used by businesses to manage bookings, schedules, forms, and user groups for services and facilities. 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 Supersaas.
List schedules before booking
Pull the list of available schedules as a read-only check before an agent books a new appointment.
Create a new user record
Add a new user to a schedule's group after confirming their details with the person requesting it.
Delete a user only with approval
Remove a user record only after the user explicitly confirms, since bookings tied to it may be affected.
10 Supersaas actions, graded by risk.
Every Supersaas 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.
- supersaas.get_userGet User
- supersaas.list_usersList Users
- supersaas.list_groupsList User Groups
- supersaas.list_schedulesList Schedules
- supersaas.list_field_listList Field List
- supersaas.list_promotionsList Promotions
- supersaas.list_super_formsList Form Definitions
write
2Create and change things. Allow, or ask the user first.
- supersaas.create_userCreate User
- supersaas.update_userUpdate User
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- supersaas.delete_userDelete User
Supersaas in three steps.
- 01Your users connect SupersaasThey add their Supersaas 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 User” can be denied outright.
- 03Any agent can actYour agent calls Supersaas through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('supersaas', { read: 'allow', write: 'ask', // create_user destructive: 'deny', // delete_user }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Supersaas connects.
Users add their Supersaas 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 Supersaas 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 · Username and password
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Supersaas from any agent.
Supersaas and Arc0, answered.
Can I use Supersaas with Claude, ChatGPT or Cursor?
Yes. Connect Supersaas 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 Supersaas actions you allow.
How do users connect Supersaas?
Users add their Supersaas 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 Supersaas actions can my agent take?
10 in total: 7 read, 2 write and 1 destructive, such as “create User”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Supersaas?
Yes. Actions like “delete User” 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 Supersaas too?
Yes. The same Supersaas connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Supersaas into your agent.
Your users connect Supersaas 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