Article
Timero for Developers: API and MCP for AI Assistants

Most people who track time do it in the middle of something else. You just finished a meeting, delivered a change, or tidied up a project – and then you need to log the hours in a system before you forget them.
We have long received questions about whether Timero can communicate with other systems. Now it can. Timero has its own API for developers and integrations, as well as an MCP server that allows AI assistants to log and retrieve hours for you – with your own permissions and login.
An API Built on the Same Foundation as the App
With the Timero API, you can connect Timero to your own systems: an internal dashboard, a payroll system, a CRM, or a script that syncs projects from another tool.
Through the API, you can:
- retrieve, create, and modify clients and projects
- log, change, and delete hours
- retrieve timesheets and time reports for a period
- get users in the company
However, the most important things happen under the hood. The API uses exactly the same rules as the app: hourly rates, rounding, project status, and invoice locks. An hour that has been invoiced is locked via the API as well. You will not get a separate set of rules that can drift apart over time.
API Keys That Are Safe to Share
Owners and administrators create keys under Settings → Integrations → API and MCP. Each key has:
- Access (scopes) – for example, read-only access to hours, or permission to create projects
- Optional expiration date – 30, 90, 180, or 365 days
- Usage overview – when the key was last used
The key is only displayed once, when it is created. We do not store it in plain text, so we cannot see it afterwards either. If you lose it, you can rotate the key and get a new one. The old one will stop working immediately.
Each key has a responsible user and can never do more than that user is allowed to do in the company. If the user leaves, the key will stop working.
If you prefer OAuth, you can instead create an OAuth client and retrieve short-lived tokens with client credentials.
MCP: Let the AI Assistant Log the Hours
MCP (Model Context Protocol) is an open standard that allows AI assistants to use tools in other services. Timero now has its own MCP server.
You connect by logging in with your Timero account, just like in the app. You do not need to paste in passwords or API keys into the assistant, and the company login with Microsoft applies as usual.
Once the assistant is connected, you can say things like:
- “Log three hours on the client project today, description: new login page.”
- “How much have I logged this week, broken down by project?”
- “What hours have I logged on this project in October?”
Nothing is Stored Without Your Approval First
It’s easy to be skeptical when an AI assistant is going to write in a system used for invoicing. That’s why we have built in a strict control in Timero, not just a recommendation to the assistant.
When the assistant is about to log or change hours, it first receives a preview from Timero: project and client, date, description, and number of hours after rounding – exactly as they will be stored. If you have already logged hours on the same project and date, you will be notified of possible double logging. Timero has also checked permissions, project status, and invoice locks. The assistant will show you the preview and wait for your response.
Only when the preview is confirmed are the hours stored. The confirmation only applies to exactly what was shown. If anything changes along the way, it must be previewed again.
The assistant also never has more permissions than you. If you are an employee, it can only log and change your own hours, and projects you do not have access to do not exist for it.
The Right Project, Even When You’re in the Code
For developers, it’s often the repo or folder that is the starting point, not the project name in Timero. Therefore, the assistant can send the name of the repo or folder you are working in and ask Timero to find the right project.
The first time, you confirm which project it pertains to, and you can save the link. The next time, it hits directly. The links are shared within the company, so the whole team benefits from them.
Timero never reads your code, Git, or files. The only thing sent is the name the assistant provides.
Who Gets Access?
The API and MCP are included in Timero Pro and Timero Team, also during the trial period. You can find documentation for the API and MCP setup under Developers, and a simpler overview on the API and MCP pages.
If you have ideas about what you want to connect Timero to, or what tools the assistant should have, we would love to hear from you.



