RepairShopr for AI agents
RepairShopr manages repair shop operations, tracking tickets, estimates, invoices, and customer contacts for device repair and IT service businesses. 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 RepairShopr.
Add a comment to a ticket
Add a note to an open repair ticket so the customer sees an update on their device.
Convert an estimate to an invoice
Turn an approved estimate into an invoice once the customer signs off on the repair.
Confirm before creating a vendor
Check existing vendors first, then create a new one only after confirming it doesn't already exist.
147 RepairShopr actions, graded by risk.
Every RepairShopr action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
65Look things up. Allowed by default.
- repairshopr.get_meGet Current User
- repairshopr.get_leadGet Lead
- repairshopr.get_userGet User
- repairshopr.get_assetGet Asset
- repairshopr.get_leadsGet Leads
- repairshopr.get_usersGet Users
- repairshopr.get_assetsGet Assets
- repairshopr.get_ticketGet Ticket
- repairshopr.get_vendorGet Vendor
- repairshopr.list_itemsList Items
- repairshopr.search_allSearch All
- repairshopr.get_contactGet Contact
- repairshopr.get_invoiceGet Invoice
- repairshopr.get_paymentGet Payment
- repairshopr.get_productGet Product
- repairshopr.list_phonesList Phones
write
64Create and change things. Allow, or ask the user first.
- repairshopr.post_leadCreate Lead
- repairshopr.post_assetCreate Asset
- repairshopr.update_leadUpdate Lead
- repairshopr.create_phoneCreate Phone
- repairshopr.post_invoiceCreate Invoice
- repairshopr.post_paymentCreate Payment
- repairshopr.post_productCreate Product
- repairshopr.update_assetUpdate Asset
- repairshopr.update_phoneUpdate Phone
- repairshopr.create_ticketCreate Ticket
- repairshopr.create_vendorCreate Vendor
- repairshopr.post_customerCreate Customer
- repairshopr.post_estimateCreate Estimate
- repairshopr.update_ticketUpdate Ticket
- repairshopr.update_vendorUpdate Vendor
- repairshopr.create_contactCreate Contact
destructive
18Delete, cancel or archive. Ask first, or deny outright.
- repairshopr.delete_phoneDelete Phone
- repairshopr.delete_ticketDelete Ticket
- repairshopr.delete_contactDelete Contact
- repairshopr.delete_invoiceDelete Invoice
- repairshopr.delete_contractDelete Contract
- repairshopr.delete_customerDelete Customer
- repairshopr.delete_estimateDelete Estimate
- repairshopr.delete_scheduleDelete Schedule
- repairshopr.delete_rmm_alertDelete RMM Alert
- repairshopr.delete_wiki_pageDelete Wiki Page
- repairshopr.delete_appointmentDelete Appointment
- repairshopr.delete_portal_userDelete Portal User
- repairshopr.delete_ticket_timerDelete Ticket Timer
- repairshopr.delete_canned_responseDelete Canned Response
- repairshopr.delete_appointment_typeDelete Appointment Type
- repairshopr.remove_ticket_line_itemRemove Ticket Line Item
RepairShopr in three steps.
- 01Your users connect RepairShoprThey add their RepairShopr api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Phone” can wait for the user, and “delete Phone” can be denied outright.
- 03Any agent can actYour agent calls RepairShopr through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('repairshopr', { read: 'allow', write: 'ask', // create_phone destructive: 'deny', // delete_phone }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How RepairShopr connects.
Users add their RepairShopr 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 RepairShopr 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 RepairShopr from any agent.
RepairShopr and Arc0, answered.
Can I use RepairShopr with Claude, ChatGPT or Cursor?
Yes. Connect RepairShopr 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 RepairShopr actions you allow.
How do users connect RepairShopr?
Users add their RepairShopr 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 RepairShopr actions can my agent take?
147 in total: 65 read, 64 write and 18 destructive, such as “create Phone”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in RepairShopr?
Yes. Actions like “delete Phone” 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 RepairShopr too?
Yes. The same RepairShopr connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug RepairShopr into your agent.
Your users connect RepairShopr once, under your brand. Your agent gets 147 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan