Billing the month
On the first of the month the operations lead asks how many billable hours went to Northwind in October. Memtro reads the timesheets: 64.5 hours across three people, most of them Dan Fletcher's development work.
Ask Kimai how many hours went into a project, and by whom.
Connect Kimai with your host and an API token and Memtro reads timesheets by person, customer, project, activity and date with total hours, plus customers, projects and activities. Rates are never read. The token acts with its user's whole role, and there is no hourly sync. When you ask, and once an administrator has granted them by name, it can record, stop, restart or change timesheets, create, change and comment on customers, projects and activities, set an invoice's status, and add or remove team members. Deleting a customer, project or activity permanently deletes every timesheet recorded on it.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right Kimai tool, reads what it needs, and answers with the source cited.
These tools change something in Kimai. 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 Kimai 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 we log on the Acme project last month?
Who worked on Brightwave Ltd this week, and for how long?
Is anyone's timer still running?
Log two hours of meetings on the Northwind project for yesterday
Mark the October Northwind invoice as paid on 3 November
On the first of the month the operations lead asks how many billable hours went to Northwind in October. Memtro reads the timesheets: 64.5 hours across three people, most of them Dan Fletcher's development work.
Priya Sharma forgot to stop her timer overnight. She asks Memtro to stop it and set the end to 18:00. With the actions granted, Memtro stops the timesheet and replaces its end time, returning the old one, and nobody is notified.
The teams that lean on Kimai most, a question each of them asks, and what they connect beside it.
A record in Kimai 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 Kimai open your profile → API access (the label varies by version) and create an API token. It is not your login password
The token acts with its user's whole role and no scopes. A normal user sees only their own timesheets, so consider a dedicated user with view_other_timesheet and just the role it needs for the actions you grant
In Connections → Kimai in Memtro type the Host name only, or your Kimai Cloud host, public over https with a trusted certificate, plus Install path and Port if needed, and paste the API token
Ask how many hours went into each project last week
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The Kimai tools are the same everywhere.
Only when you ask, and only what it has been granted: record a finished timesheet for a named user; stop a running timesheet; overwrite a timesheet's times, project, activity or description; delete a timesheet; create a tag; delete a tag; create a customer; create a project for a customer; create an activity, global or for a project; restart a timesheet as a new running timer for the token's user; change a customer's name, number, comment, visibility, billable flag or locale; change a project's name, number, order number, dates, visibility or billable flag; change an activity's name, number, comment, visibility or billable flag; delete a customer with all its projects, activities and timesheets; delete a project with all its activities and timesheets; delete an activity with all its timesheets; comment on a customer; comment on a project; set an invoice's status, payment date or comment; delete an invoice and its document; add a user to a team (grants the team's access); remove a user from a team. 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.
Host and API token. In Kimai open your profile → API access (the label varies by version) and create an API token. It is not your login password.
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