Covering a Saturday
Maya Okafor, operations manager at Northwind, asked who is working at Soho on Saturday. Memtro listed each shift with role, start and end, and flagged one open shift with nobody assigned.
Who is working at Soho on Saturday, and who has leave booked?
RotaCloud connects Memtro to your staff rotas. It reads shifts in a date window with who, where, which role and when, then booked leave, pending leave requests, employees, locations, roles and day notes. Pay, rates, payroll ids and dates of birth are never returned. When asked, and once an administrator has granted them by name, it can create, publish or permanently delete shifts, approve or deny leave and unavailability, book leave, message staff by email, and add or delete employees. Published shifts, decisions and messages reach employees, and messages cannot be unsent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right RotaCloud tool, reads what it needs, and answers with the source cited.
These tools change something in RotaCloud. 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 RotaCloud 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 working at Soho on Saturday?
Which shifts next week are still open?
Which leave requests are waiting for a decision?
Approve Jo Bell's holiday request for the first week of June.
Create an open bar shift at Soho on Friday from 6pm to midnight and publish it.
Maya Okafor, operations manager at Northwind, asked who is working at Soho on Saturday. Memtro listed each shift with role, start and end, and flagged one open shift with nobody assigned.
Tom Reilly, area manager at Acme Ltd, asked Memtro to give Saturday's open Soho shift to Jo Bell and publish it. Memtro assigned the shift to Jo and published it, so it appeared on her rota and RotaCloud could notify her.
The teams that lean on RotaCloud most, a question each of them asks, and what they connect beside it.
A record in RotaCloud 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 RotaCloud, open Settings (the cog, top right) → API and Webhooks → API Keys.
Press + next to API Keys, name it Memtro and copy the key. It has full access with no scopes, so keep it for Memtro alone so you can revoke it on its own.
In Memtro, open Connections → RotaCloud and paste the API key.
Ask: who is working at Soho on Saturday?
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The RotaCloud tools are the same everywhere.
Only when you ask, and only what it has been granted: add a day note for managers to a rota day; edit or delete a day note; create, change or delete a shift; publish or unpublish named shifts (staff see published shifts); approve or deny a leave request; book leave for named employees, or delete a leave record; approve or deny an unavailability request; send a message to named employees; add an employee, optionally sending the invite; delete an employee. 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 RotaCloud, open Settings (the cog, top right) → API and Webhooks → API Keys.
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