How many hours did the team log on each project this week in TimeCamp?
TimeCamp connects Memtro to your time tracking. It reads time entries in a date range of up to 31 days, with hours, task, tags and billable status, and totals by task and by person. It reads tasks and projects with their budgets, searches the project tree, and shows running timers and your own. When asked and granted, it can log, edit or delete a time entry, start, stop or discard your timer, and create, rename, move or archive a task. People appear by user id, not name, and entry descriptions are not returned. The token sees only what you see.
Ask in plain English from chat, your editor, a scheduled job or your own agent. The model picks the right TimeCamp tool, reads what it needs, and answers with the source cited.
These tools change something in TimeCamp. 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 TimeCamp 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.
TimeCamp + MemtroHow many hours were logged on each project this week?
Which entries from the last two weeks are billable but not invoiced?
Who has a timer running right now?
What budget does the Website rebuild project have?
Start my timer on the Client onboarding task.
Dan Fletcher, project manager at BigCo, asked how many hours the Website rebuild had used this month. Memtro read the time entries for the month, gave the total on that project's tasks and the hours by user id, and set them beside the project's budget.
Maya Okafor, consultant at Northwind, asked Memtro to log two billable hours on Tuesday against the Acme audit task. With the action granted, Memtro logged the entry for her. It showed in her TimeCamp timesheet and now counts towards the billable hours that feed invoices.
The teams that lean on TimeCamp most, a question each of them asks, and what they connect beside it.
A record in TimeCamp 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
Workiz
Guesty
Buildium
Skilljar
Runn
ClockodoIn TimeCamp, open Settings, then Users, then your profile, and find Get your API token here. An admin's token sees everyone's time, so a dedicated user with only the access Memtro needs is safer.
In Memtro, open Connections → TimeCamp and paste the API token.
An administrator grants the time entry, timer and task actions by name to the teams that may use them. Logging time for someone else needs admin rights in TimeCamp.
Ask how many hours were logged on each project this week.
Chat in the dashboard, the OpenAI-compatible API, scheduled jobs, and any MCP client: Claude Code, OpenCode, Cursor, Claude Desktop. The TimeCamp tools are the same everywhere.
Only when you ask, and only what it has been granted: log a time entry; edit a time entry; delete a time entry; start your timer on a task; stop your running timer and save the time; discard your running timer; create a task or project; rename, move or archive a task. 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 token. In TimeCamp, open Settings, then Users, then your profile, and find Get your API token here. An admin's token sees everyone's time, so a dedicated user with only the access Memtro needs is safer.
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