Covering the weekend
The store manager asks who is working at the Northwind café on Saturday. Memtro reads the rostered shifts for that location: four people across the day, one open shift from 16:00 to 22:00, and one person on approved leave.
Ask who is rostered on Saturday in Deputy, or how many hours someone worked this week.
Connect Deputy with your install name, region and a permanent access token, and Memtro reads employees, timesheets with hours and approval, rostered shifts including open and draft ones, leave and its status, and locations and areas. Pay, cost, contact details and leave comments are never returned. It reads on demand and there is no hourly sync. When you ask, and once an administrator has granted the action by name, it can raise, approve or decline leave, clock people in and out, approve timesheets for payroll, post memos to staff and add journal notes. Discarding a timesheet is permanent.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Deputy tool, reads what it needs, and answers with the source cited.
These tools change something in Deputy. 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 Deputy 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 rostered on Saturday at the Manchester store?
How many hours did Dan Fletcher work this week?
Which timesheets from last week are not yet approved?
Approve Priya Sharma's leave request for 12 to 14 December
Post a memo to the Leeds staff that the store opens at 10 on Boxing Day
The store manager asks who is working at the Northwind café on Saturday. Memtro reads the rostered shifts for that location: four people across the day, one open shift from 16:00 to 22:00, and one person on approved leave.
Before payroll, operations lead Sam Okafor asks Memtro to approve last week's timesheets at the Acme Leeds store. Memtro approves the twelve completed ones so they go into the next payroll export, and lists Friday's that was still in progress for him to check.
The teams that lean on Deputy most, a question each of them asks, and what they connect beside it.
A record in Deputy 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.
Sign in to your Deputy install as an administrator who can see the whole roster and open /exec/devapp/oauth_clients on your Deputy address. The token reaches what its maker can see and do
Add a Client ID with any name, open it, press Get an Access Token and copy the token at once: Deputy shows it only once
In Memtro open Connections → Deputy and paste the Permanent access token with the Install name and Region from your address (acme and au for acme.au.deputy.com), and connect
Ask who is rostered on at the Leeds location on Saturday
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Deputy tools are the same everywhere.
Only when you ask, and only what it has been granted: raise a leave request in Deputy for an employee, awaiting manager approval; approve, decline or cancel a Deputy leave request; clock a Deputy employee in (start a timesheet); clock a Deputy employee out (end a timesheet), with an optional meal break; approve a Deputy timesheet for payroll; discard a Deputy timesheet, permanently; post a memo in Deputy to a location's staff or named users; add a journal note to a Deputy employee's record. 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.
Install name, Region and Permanent access token. Sign in to your Deputy install as an administrator who can see the whole roster and open /exec/devapp/oauth_clients on your Deputy address. The token reaches what its maker can see and do.
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