Breathe HR for AI agents
Breathe HR is cloud-based HR software that small and mid-sized businesses use to manage employee records, absences, leave requests, and performance reviews in one place. 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 Breathe HR.
Look up an employee's record
Read-only pull of an employee's profile, absences, and benefits before processing a request for them.
Approve a leave request
Approve a submitted leave request after the user confirms the dates and remaining allowance.
Require approval before deleting an expense
Treat deleting an employee expense or training course as destructive since it removes their record.
50 Breathe HR actions, graded by risk.
Every Breathe HR action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
38Look things up. Allowed by default.
- breathe_hr.get_accountGet Account
- breathe_hr.get_employeeGet Employee
- breathe_hr.list_bonusesList Employee Bonuses
- breathe_hr.list_absencesList Absences
- breathe_hr.list_benefitsList Employee Benefits
- breathe_hr.list_salariesList Salaries
- breathe_hr.list_divisionsList Divisions
- breathe_hr.list_employeesList Employees
- breathe_hr.list_locationsList Locations
- breathe_hr.list_sicknessesList Sicknesses
- breathe_hr.list_departmentsList Departments
- breathe_hr.get_leave_requestGet Leave Request
- breathe_hr.list_employee_jobsList Employee Jobs
- breathe_hr.list_leave_requestsList Leave Requests
- breathe_hr.get_employee_expenseGet Employee Expense
- breathe_hr.list_change_requestsList Change Requests
write
10Create and change things. Allow, or ask the user first.
- breathe_hr.create_employeeCreate Employee
- breathe_hr.update_sicknessUpdate Sickness
- breathe_hr.create_employee_expenseCreate Employee Expense
- breathe_hr.create_employee_sicknessCreate Employee Sickness
- breathe_hr.create_employee_expense_claimCreate Employee Expense Claim
- breathe_hr.update_employee_expense_claimUpdate Employee Expense Claim
- breathe_hr.create_employee_change_requestCreate Employee Change Request
- breathe_hr.update_employee_training_courseUpdate employee training course
- breathe_hr.reject_leave_requestReject Leave Request
- breathe_hr.approve_leave_requestApprove Leave Request
destructive
2Delete, cancel or archive. Ask first, or deny outright.
- breathe_hr.delete_employee_expenseDelete Employee Expense
- breathe_hr.delete_employee_training_courseDelete Employee Training Course
Breathe HR in three steps.
- 01Your users connect Breathe HRThey add their Breathe HR api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Employee” can wait for the user, and “delete Employee Expense” can be denied outright.
- 03Any agent can actYour agent calls Breathe HR through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('breathe_hr', { read: 'allow', write: 'ask', // create_employee destructive: 'deny', // delete_employee_expense }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Breathe HR connects.
Users add their Breathe HR 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 Breathe HR 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 Breathe HR from any agent.
Breathe HR and Arc0, answered.
Can I use Breathe HR with Claude, ChatGPT or Cursor?
Yes. Connect Breathe HR 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 Breathe HR actions you allow.
How do users connect Breathe HR?
Users add their Breathe HR 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 Breathe HR actions can my agent take?
50 in total: 38 read, 10 write and 2 destructive, such as “create Employee”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Breathe HR?
Yes. Actions like “delete Employee Expense” 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 Breathe HR too?
Yes. The same Breathe HR connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Breathe HR into your agent.
Your users connect Breathe HR once, under your brand. Your agent gets 50 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan