Cover for the week
Monday morning, the operations lead asks who is off this week. Memtro lists the approved holiday and sickness from Breathe by person and dates, and the line manager for each, so cover can be arranged.
Who works here, who they report to and who is off this week.
Connect Breathe with your account's API key and Memtro reads the directory: each employee's job title, department, line manager, working pattern and start date, plus absences, sickness, training courses, locations and holiday allowances. Salary, bank details, date of birth and personal contact details are not read, and there is no sync. When you ask, and once an administrator has granted each action by name, it can approve, reject, book or cancel leave, record sickness and training, add a new starter and decide expense claims. Deleting a record is permanent, and approving a claim commits the company to pay it.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Breathe HR tool, reads what it needs, and answers with the source cited.
These tools change something in Breathe HR. The model is told to use them only when you ask for exactly that, and an administrator grants each one by name to the teams that may use it; a personal connection acts only after its owner allows it.
Once Breathe HR is connected, these are the kinds of things people ask. Plain questions, no syntax. If the answer lives partly in another system you have connected, Memtro looks there too.
Who is off next week in the Finance team?
Who does Hannah Reid report to, and what is her working pattern?
Which sickness absences in the last 90 days still need a fit note?
Whose first-aid training expires before March?
Approve Tom Gallagher's holiday request for 2 to 6 December
Monday morning, the operations lead asks who is off this week. Memtro lists the approved holiday and sickness from Breathe by person and dates, and the line manager for each, so cover can be arranged.
Priya Shah, the office manager, asks Memtro to approve Tom Gallagher's pending holiday request for the first week of December. Memtro finds the request in Breathe and approves it, so the days are booked and taken from his allowance, recorded in Breathe as done by its API Employee.
The teams that lean on Breathe HR most, a question each of them asks, and what they connect beside it.
A record in Breathe HR is rarely the whole story. Connect the systems that hold the rest and Memtro checks them together, then remembers what it learned so the next question starts further along.
Using something else for the same job, or both? Each connector has its own tools; connect as many as you like.
In Breathe open Configure → Settings → Integrations → API Setup. An account admin has to enable the API first, and the production key starts prod-
In Memtro open Connections → Breathe HR, paste the API key and connect. For the Breathe sandbox enter https://api.sandbox.breathehr.info/v1 as the Base URL with the sandbox- key
Memtro only reads until an administrator grants an action by name, such as approving leave or recording sickness
Ask who is off next week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Breathe HR tools are the same everywhere.
Only when you ask, and only what it has been granted: approve a pending leave request; reject a pending leave request with a reason; book leave for an employee as a leave request; cancel an absence (booked leave), returning the days; record a sickness absence for an employee; change a sickness record (end date, status, type, reason); delete a sickness record, permanently; add an employee with directory details only; record a training course for an employee; change a training record; delete a training record, permanently; approve or reject an expense claim (approving commits the company to pay it). Every other tool reads, searches or lists. The Connections page labels the tools that act, an administrator grants each one by name to the teams that may use it, and a personal connection acts only after its owner allows it.
A personal connection serves only your own requests. A shared connection serves the organisation: everyone, or only the teams an admin chooses. Admins can always add shared connections; other members need the permission.
Credentials are encrypted at rest. Tool results are cached briefly so agent loops do not repeat identical calls, and the facts the model extracts are saved to your organisation's memory with provenance (system, record and link) so they can be checked and superseded.
API key. In Breathe open Configure → Settings → Integrations → API Setup. An account admin has to enable the API first, and the production key starts prod-.
Seven-day free trial, then one monthly price per organisation. Connectors, jobs and memory are never metered.
Sign in, add a provider key, create an API key and point your tools at Memtro. It takes about five minutes.
7-day free trial · card on file, nothing charged until it ends · cancel any time