Supportbee for AI agents
SupportBee is email-based helpdesk software that helps small teams organize, assign, and reply to customer support tickets from a shared inbox. 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 Supportbee.
List open tickets by team
Pull the list of tickets assigned to a team so an agent knows what needs a response today.
Reply to a support ticket
Draft and send a reply to a customer's ticket after the support agent reviews the wording.
Delete a ticket only if confirmed
Delete a ticket only after the user confirms it was created by mistake or is pure spam.
41 Supportbee actions, graded by risk.
Every Supportbee action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
15Look things up. Allowed by default.
- supportbee.get_ticketGet Ticket
- supportbee.list_usersList SupportBee Users
- supportbee.list_ticketsList Tickets
- supportbee.search_ticketsSearch SupportBee Tickets
- supportbee.list_ticket_repliesList Ticket Replies
- supportbee.list_ticket_commentsList Ticket Comments
- supportbee.get_replies_count_reportGet Replies Count Report
- supportbee.get_tickets_count_reportGet Tickets Count Report
- supportbee.get_avg_first_response_time_reportGet Avg First Response Time Report
- supportbee.fetch_teamsFetch SupportBee Teams
- supportbee.fetch_emailsFetch Forwarding Emails
- supportbee.fetch_labelsFetch SupportBee Labels
- supportbee.fetch_snippetsFetch Snippets
- supportbee.show_ticket_replyShow Ticket Reply
- supportbee.show_user_or_customer_groupShow SupportBee User or Customer Group
write
19Create and change things. Allow, or ask the user first.
- supportbee.create_ruleCreate Rule
- supportbee.update_userUpdate SupportBee User
- supportbee.create_emailCreate Forwarding Email
- supportbee.create_filterCreate Filter
- supportbee.create_ticketCreate SupportBee Ticket
- supportbee.create_commentCreate Ticket Comment
- supportbee.create_snippetCreate Snippet
- supportbee.update_snippetUpdate Snippet
- supportbee.create_consequenceCreate Consequence
- supportbee.add_label_to_ticketAdd Label to Ticket
- supportbee.create_ticket_replyCreate Ticket Reply
- supportbee.create_user_or_customer_groupCreate SupportBee User
- supportbee.untrash_ticketUntrash SupportBee Ticket
- supportbee.unarchive_ticketUnarchive SupportBee Ticket
- supportbee.mark_ticket_as_spamMark SupportBee Ticket as Spam
- supportbee.assign_ticket_to_teamAssign Ticket to Team
destructive
7Delete, cancel or archive. Ask first, or deny outright.
- supportbee.delete_ticketDelete SupportBee Ticket
- supportbee.archive_ticketArchive SupportBee Ticket
- supportbee.delete_snippetDelete Snippet
- supportbee.remove_label_from_ticketRemove Label From Ticket
- supportbee.trash_ticketTrash SupportBee Ticket
- supportbee.unassign_ticket_from_teamUnassign Ticket from Team
- supportbee.unassign_ticket_from_userUnassign User From Ticket
Supportbee in three steps.
- 01Your users connect SupportbeeThey add their Supportbee api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Rule” can wait for the user, and “delete SupportBee Ticket” can be denied outright.
- 03Any agent can actYour agent calls Supportbee through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('supportbee', { read: 'allow', write: 'ask', // create_rule destructive: 'deny', // delete_ticket }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Supportbee connects.
Users add their Supportbee 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 Supportbee 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 Supportbee from any agent.
Supportbee and Arc0, answered.
Can I use Supportbee with Claude, ChatGPT or Cursor?
Yes. Connect Supportbee 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 Supportbee actions you allow.
How do users connect Supportbee?
Users add their Supportbee 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 Supportbee actions can my agent take?
41 in total: 15 read, 19 write and 7 destructive, such as “create Rule”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Supportbee?
Yes. Actions like “delete SupportBee Ticket” 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 Supportbee too?
Yes. The same Supportbee connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Supportbee into your agent.
Your users connect Supportbee once, under your brand. Your agent gets 41 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan