Who logged what in Clockify this week, with totals by project and client.
Connect Clockify with an API key and Memtro reads workspaces, projects, clients, members, and a person's time entries for a period with hours, description and totals by project. Reading someone else's time needs admin rights in Clockify. 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 log, change or permanently delete time entries, start and stop timers, create and update projects, tasks, clients and tags, request time off, submit timesheets, and approve or reject time off and timesheets, all as you.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Clockify tool, reads what it needs, and answers with the source cited.
These tools change something in Clockify. 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 Clockify 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.
How many hours did I log on the Acme project this week?
What did Priya Nair log last week, by project?
Which projects belong to Brightwave Ltd, and are they billable?
Log two hours yesterday afternoon on the Northwind project for the data migration review
Start a timer on the BigCo onboarding project
Before invoicing, the account lead asks how many hours went into Brightwave Ltd last month. Memtro reads each member's time entries for the month, which the key's admin rights allow, and answers with totals by project and which entries are not billable.
On Monday the operations lead, Dan Fletcher, asks Memtro to approve Priya Nair's submitted timesheet for last week. Memtro finds the pending request, approves it with his note, and Clockify locks the period's entries and shows Priya the decision.
The teams that lean on Clockify most, a question each of them asks, and what they connect beside it.
A record in Clockify 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.
Clio Manage
YouTrack
Canny
Float
Productive
Smartsheet
Wrike
Financial Cents
Karbon
Scoro
Kanboard
Kimai
Leantime
Acuity Scheduling
Luma
Tito
Fellow
Samsara
ServiceM8
Cliniko
Fleetio
SavvyCal
Chili Piper
Humanitix
Circleback
Aha!
Tempo
Smoobu
Semble
Airmeet
Beds24
Bookeo
Commusoft
Fergus
Fixflo
Housecall Pro
Nookal
Paymo
ProductPlan
SimplyBook.me
TimeCamp
Workiz
Guesty
Buildium
Skilljar
Runn
ClockodoIn app.clockify.me open Profile settings → API, click Generate and copy the key, which acts as you, and for a workspace on its own subdomain generate it while signed in there
Leave API host blank for api.clockify.me, or enter your region's host name, such as euc1.clockify.me, and leave Workspace ID blank to use your first workspace
In Memtro open Connections → Clockify, paste the API key and connect, noting a FREE workspace allows only 30 API requests an hour
Ask how many hours you logged on a project this week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Clockify tools are the same everywhere.
Only when you ask, and only what it has been granted: log a completed time entry in a Clockify workspace; add a client to a Clockify workspace; add a task to a Clockify project; add a tag to a Clockify workspace; start a running Clockify timer as the connected user; stop a running Clockify timer; change a Clockify time entry; permanently delete a Clockify time entry; create a Clockify project; rename, archive or change a Clockify project; rename a Clockify task, mark it done, or change its estimate or assignees; rename, archive or change the note of a Clockify client; request time off under a Clockify time-off policy; approve or reject a Clockify time-off request; submit a Clockify timesheet for approval; approve, reject or withdraw a Clockify timesheet approval request. 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.clockify.me open Profile settings → API, click Generate and copy the key, which acts as you, and for a workspace on its own subdomain generate it while signed in there.
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