Kimai MCP server

What the model can do

Kimai time tracking (self-hosted or Kimai Cloud): timesheets by person, customer, project, activity and date with total hours, plus customers, projects, activities, tags, users, teams and invoices. Can record a finished timesheet, restart or stop one, change or delete a timesheet, create, change or delete customers, projects and activities, comment on a customer or project, set an invoice's status or delete it, add or remove a team member, and create or delete a tag.

Reads

• kimai_list_timesheetsKimai timesheets, newest first: begin and end (the user's local time with offset), hours, person, customer, project, activity, description, tags…
• kimai_list_customersKimai customers: id, name, number, whether visible and billable.
• kimai_list_projectsKimai projects: id, name, customer id, start and end dates, visible and billable.
• kimai_list_activitiesKimai activities (the kind of work: Development, Meeting…): id, name, project id (none means global), visible and billable.
• kimai_list_usersKimai users the token may list (needs view_user): id, display name (alias), username, whether enabled.
• kimai_list_tagsKimai tag names, optionally matching a term.
• kimai_list_invoicesKimai invoices, newest pages first as Kimai orders them: id, number, status (new, pending, paid, canceled), customer, created, payment date…
• kimai_list_teamsKimai teams the token may see (needs view_team): id and name.

Acts, when you ask

These change something in Kimai. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• kimai_create_timesheetRecords a finished Kimai timesheet for a named user: project, activity, begin and end as local date-times in that user's Kimai timezone (no offset)…
• kimai_stop_timesheetStops a running Kimai timesheet now, setting its end to the current time.
• kimai_update_timesheetOVERWRITES.
• kimai_delete_timesheetDESTRUCTIVE.
• kimai_create_tagCreates a Kimai tag by name (needs manage_tag or create_tag).
• kimai_create_customerCreates a Kimai customer with a name, and optionally a number, comment, country (ISO code), currency, timezone and whether visible and billable…
• kimai_create_projectCreates a Kimai project for a customer (by id), with a name and optionally a number, comment, order number, start and end dates (YYYY-MM-DD)…
• kimai_create_activityCreates a Kimai activity (a kind of work) with a name, for one project or, without a project, global to all; optionally a number, comment…
• kimai_restart_timesheetSTARTS A RUNNING TIMER.
• kimai_delete_tagDESTRUCTIVE.
• kimai_update_customerOVERWRITES.
• kimai_update_projectOVERWRITES.
• kimai_update_activityOVERWRITES.
• kimai_delete_customerDESTRUCTIVE.
• kimai_delete_projectDESTRUCTIVE.
• kimai_delete_activityDESTRUCTIVE.
• kimai_add_customer_commentAdds a comment (markdown) to a Kimai customer, optionally pinned to the top.
• kimai_add_project_commentAdds a comment (markdown) to a Kimai project, optionally pinned to the top.
• kimai_update_invoiceSets a Kimai invoice's status (new, pending, paid, canceled), its payment date (YYYY-MM-DD, for paid) or its comment.
• kimai_delete_invoiceDESTRUCTIVE.
• kimai_add_team_memberCHANGES ACCESS.
• kimai_remove_team_memberCHANGES ACCESS.

Connect it

First connect Kimai on Dashboard → Connections, then add Memtro to your client once. The Kimai tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Kimai connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › 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

Questions

Is this an official Kimai MCP server?

No. It is Memtro's MCP server with Memtro's Kimai connector behind it: the connector reads Kimai through its API with the credentials you connect on Dashboard → Connections, and Kimai publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Kimai?

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. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Work management

• Clio Manage MCP server
• Linear MCP server
• Jira MCP server
• Asana MCP server
• monday.com MCP server
• Airtable MCP server