Who is on the schedule this weekend, and who has asked for time off?
7shifts puts your restaurant schedule within reach of a question. You see the published and draft schedule by location, person and date, time punches with hours worked, time-off requests, employees, locations, departments and roles. When asked and granted, Memtro can create, change and delete shifts and time punches, approve, decline or delete time off, add an employee and deactivate one. Worth knowing: the token cannot be scoped and acts as an admin on the whole company. Pay rates, contact details, birth dates and addresses are never read, and wages and tips are not returned.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right 7shifts tool, reads what it needs, and answers with the source cited.
These tools change something in 7shifts. 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 7shifts 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.
7shifts + MemtroWho is on the schedule at the downtown location this weekend?
How many hours did the kitchen team clock last week?
Which time-off requests end after next Monday?
Are there any open shifts on Saturday?
Approve Tom Reilly's time-off request for next Friday.
Maya Okafor, general manager of Northwind's riverside restaurant, asked who was working Saturday night. Memtro listed the published shifts at that location with each person, role, start and end time, and the open shifts still unfilled.
Dan Fletcher, assistant manager at Acme Ltd's city centre site, asked Memtro to fix Tom Reilly's punch, which had no clock-out. Memtro corrected the clock-out time, and Tom's hours and payroll in 7shifts changed with it.
The teams that lean on 7shifts most, a question each of them asks, and what they connect beside it.
A record in 7shifts 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.
BambooHR
Ashby
Breathe HR
Lever
Workable
Deel
Factorial HR
Pinpoint
Recruitee
CharlieHR
Deputy
Humaans
JazzHR
SmartRecruiters
Lattice
15Five
Homerun
Jibble
Leapsome
LearnUpon
Planday
Timetastic
Recruit CRMIn 7shifts, a company admin goes to Company Settings, then Developer Tools, then Access Tokens, creates a token named Memtro and copies it.
In Memtro, open Connections → 7shifts and paste it into Access token. A token unused for six months is deleted by 7shifts.
An administrator grants the actions by name, such as Approve time off or Delete shift, to the managers who may use them.
Ask who is on the schedule at the downtown location this weekend.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The 7shifts tools are the same everywhere.
Only when you ask, and only what it has been granted: create a shift, as a draft or on the published schedule; change a shift; delete a shift (permanent); add a time punch for an employee; correct a time punch; delete a time punch (permanent); approve a time-off request; decline a time-off request; delete a time-off request (permanent); add an employee, and invite them if you ask; deactivate 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.
Access token. In 7shifts, a company admin goes to Company Settings, then Developer Tools, then Access Tokens, creates a token named Memtro and copies it.
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
