Weekly hours review
On Monday the operations lead asks who logged time on Acme last week. Memtro reads the week's time records and answers with hours by person and by task, with their comments, beside what the project has spent of its budget.
Who logged what, on which project, and which timers are running now in Everhour.
Connect Everhour with your API key and Memtro reads the team's time records for a period with hours, person, task and comment, timers running now, projects with budget spent, clients, tasks and timesheets. Team-wide time needs an admin or manager role. 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 start and stop timers, set or change logged time, manage tasks, projects and clients, and submit, approve or reject timesheets, all as you. Deleting a task permanently removes all time logged on it.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Everhour tool, reads what it needs, and answers with the source cited.
These tools change something in Everhour. 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.
Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Everhour for you. Each event can start a job, with the event as its input. Everhour signs nothing, so the long random address is the only check: treat it as a password.
Events and webhooksOnce Everhour 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 logged time on Acme last week?
How many hours did Priya Sharma log in October?
Who has a timer running right now, and on what?
How much of the Northwind budget has been spent?
Log three hours on the Northwind design review task for yesterday
On Monday the operations lead asks who logged time on Acme last week. Memtro reads the week's time records and answers with hours by person and by task, with their comments, beside what the project has spent of its budget.
Priya Sharma tells Memtro she worked four hours, not two, on the BigCo audit task on Tuesday. Memtro sets her time for that day to four hours, replacing the two that were there, and says what it replaced.
The teams that lean on Everhour most, a question each of them asks, and what they connect beside it.
A record in Everhour 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 app.everhour.com open My Profile, scroll to the API key at the bottom of the page and copy it
The key acts as you, so anything Memtro changes is changed as you, and team-wide time needs an admin or manager role in Everhour
In Memtro open Connections → Everhour, paste the API key and connect
Ask who logged time on a project last week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Everhour tools are the same everywhere.
Only when you ask, and only what it has been granted: add a task to an Everhour project; add a client in Everhour; start an Everhour timer on a task as the connected user (stops any timer already running); stop the connected user's running Everhour timer; set the time a person logged on a task for a day in Everhour, replacing what was there; change an Everhour time record; delete an Everhour time record; rename, close, reopen or reschedule an Everhour task; set an Everhour task's estimate; permanently delete an Everhour task and all its time records; create an Everhour project; rename an Everhour project, change its client or colour; archive or unarchive an Everhour project; rename, archive or reactivate an Everhour client; submit an Everhour timesheet week for approval; approve or reject an Everhour timesheet. 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 app.everhour.com open My Profile, scroll to the API key at the bottom of the page and copy it.
Yes. Turn events on in the connection's Events tab on the Connections page, choose the kinds you want, and Memtro registers its address with Everhour for you. A job set to start "When an event arrives" then runs once for each matching event, with the event as its input. The run treats the event as outside data, never as instructions, and anything the run remembers is kept as unverified.
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