Backendless for AI agents
Backendless is a backend-as-a-service platform giving mobile and web apps user authentication, a data store, file storage, and messaging without teams standing up their own servers. 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 Backendless.
Look up a user record
Find a user by ID and check their account details before a support agent resets access.
Manage files in storage
Upload, move, or copy a file between directories in Backendless file storage as part of a content update.
Delete a stale user account
Delete a user account only after confirming it's inactive and the request is approved, since removal can't be undone.
30 Backendless actions, graded by risk.
Every Backendless action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
6Look things up. Allowed by default.
- backendless.get_timerGet Backendless Timer
- backendless.get_key_itemsGet Key Items
- backendless.get_all_valuesGet All Values
- backendless.get_file_countGet File Count
- backendless.get_counter_valueGet Counter Value
- backendless.validate_user_tokenValidate User Token
write
18Create and change things. Allow, or ask the user first.
- backendless.create_hiveCreate Backendless Hive
- backendless.create_timerCreate Backendless Timer
- backendless.update_timerUpdate Backendless Timer
- backendless.create_directoryCreate Directory
- backendless.map_putMap Put
- backendless.copy_fileCopy File
- backendless.move_fileMove File
- backendless.user_findFind User by ID
- backendless.user_loginUser Login
- backendless.user_logoutUser Logout
- backendless.user_updateUpdate User
- backendless.publish_messagePublish Message
- backendless.directory_listingDirectory Listing
- backendless.set_counter_valueSet Counter Value
- backendless.user_registrationUser Registration
- backendless.user_grant_permissionGrant Permission to User
destructive
6Delete, cancel or archive. Ask first, or deny outright.
- backendless.delete_fileDelete File
- backendless.delete_timerDelete Backendless Timer
- backendless.delete_directoryDelete Directory
- backendless.user_deleteDelete User
- backendless.reset_counterReset Counter
- backendless.user_revoke_permissionRevoke Permission from User
Backendless in three steps.
- 01Your users connect BackendlessThey add their Backendless api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Backendless Hive” can wait for the user, and “delete File” can be denied outright.
- 03Any agent can actYour agent calls Backendless through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('backendless', { read: 'allow', write: 'ask', // create_hive destructive: 'deny', // delete_file }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Backendless connects.
Users add their Backendless 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 Backendless 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 Backendless from any agent.
Backendless and Arc0, answered.
Can I use Backendless with Claude, ChatGPT or Cursor?
Yes. Connect Backendless 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 Backendless actions you allow.
How do users connect Backendless?
Users add their Backendless 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 Backendless actions can my agent take?
30 in total: 6 read, 18 write and 6 destructive, such as “create Backendless Hive”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Backendless?
Yes. Actions like “delete File” 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 Backendless too?
Yes. The same Backendless connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Backendless into your agent.
Your users connect Backendless once, under your brand. Your agent gets 30 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan