Fireberry for AI agents
Fireberry is a CRM platform that integrates with other business tools to manage contacts, opportunities, tickets, and orders, used by sales and operations teams in one system. 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 Fireberry.
Log a customer call
Create a phone call activity log once a rep finishes a call with a prospect.
Create a new opportunity
Create an opportunity record once a deal moves from lead to active pipeline.
Confirm before deleting an account
Require approval before deleting an account, since it removes its linked contacts and opportunities.
124 Fireberry actions, graded by risk.
Every Fireberry action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
53Look things up. Allowed by default.
- fireberry.get_taskGet Fireberry Task by ID
- fireberry.get_userGet a Fireberry user by ID
- fireberry.get_a_noteGet a Note
- fireberry.get_a_taskGet a Task
- fireberry.get_accountGet an Account
- fireberry.get_contactGet a Contact
- fireberry.get_an_assetGet an Asset
- fireberry.get_a_ticketGet a Ticket
- fireberry.get_campaignGet Campaign by ID
- fireberry.get_all_tasksGet All Tasks
- fireberry.get_all_usersGet All Users
- fireberry.get_a_meetingGet a Meeting
- fireberry.get_an_objectGet an Object
- fireberry.get_a_productGet a Product
- fireberry.get_a_projectGet a Project
- fireberry.query_recordsFireberry: Query Records
write
51Create and change things. Allow, or ask the user first.
- fireberry.create_fileUpload file to Fireberry record
- fireberry.update_task2Update a Task (V2)
- fireberry.create_a_noteCreate a note
- fireberry.create_a_taskCreate a Task
- fireberry.create_recordCreate a new Fireberry record
- fireberry.update_a_userUpdate a User
- fireberry.create_meetingCreate a Fireberry meeting
- fireberry.update_accountUpdate Fireberry Account
- fireberry.create_an_assetCreate a Fireberry asset
- fireberry.create_a_ticketCreate a Ticket
- fireberry.create_campaignCreate a Campaign
- fireberry.update_an_assetUpdate an Asset
- fireberry.update_a_ticketUpdate a Ticket
- fireberry.update_campaignUpdate a Fireberry Campaign
- fireberry.create_a_contactCreate a Fireberry contact
- fireberry.create_a_productCreate a Fireberry product
destructive
20Delete, cancel or archive. Ask first, or deny outright.
- fireberry.delete_a_noteDelete a Note
- fireberry.delete_a_taskDelete a task
- fireberry.delete_accountDelete an Account
- fireberry.delete_contactDelete a Contact
- fireberry.delete_meetingDelete a Meeting
- fireberry.delete_productDelete a product
- fireberry.delete_an_assetDelete a Fireberry asset
- fireberry.delete_a_ticketDelete a ticket
- fireberry.delete_campaignDelete a Fireberry campaign
- fireberry.delete_crm_userDelete a CRM User
- fireberry.delete_a_projectDelete a project
- fireberry.delete_a_contractDelete a contract
- fireberry.delete_an_articleDelete an Article
- fireberry.delete_a_competitorDelete a Competitor
- fireberry.delete_activity_logDelete an Activity Log
- fireberry.delete_a_phone_callDelete a Phone Call
Fireberry in three steps.
- 01Your users connect FireberryThey add their Fireberry api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “upload file to Fireberry record” can wait for the user, and “delete a Note” can be denied outright.
- 03Any agent can actYour agent calls Fireberry through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('fireberry', { read: 'allow', write: 'ask', // create_file destructive: 'deny', // delete_a_note }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Fireberry connects.
Users add their Fireberry 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 Fireberry 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 Fireberry from any agent.
Fireberry and Arc0, answered.
Can I use Fireberry with Claude, ChatGPT or Cursor?
Yes. Connect Fireberry 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 Fireberry actions you allow.
How do users connect Fireberry?
Users add their Fireberry 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 Fireberry actions can my agent take?
124 in total: 53 read, 51 write and 20 destructive, such as “upload file to Fireberry record”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Fireberry?
Yes. Actions like “delete a Note” 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 Fireberry too?
Yes. The same Fireberry connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Fireberry into your agent.
Your users connect Fireberry once, under your brand. Your agent gets 124 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan