Skip to content

Integration · Productivity

clockodo.com

Connect Claude & ChatGPT to Clockodo

Ask your AI to start the clock on a customer, show what you logged last week or check how much overtime and holiday someone has in Clockodo. It can start and stop the stopwatch, correct time entries, create customers and projects, and record and approve absences. Time questions get answered without opening reports by hand.

Connect Clockodo free

Free plan, no credit card. Takes about a minute.

Try asking

  • “Start the clock on Acme, service Consulting, project Website.”

    The AI finds the customer, service and project IDs and starts the stopwatch with them.

  • “Stop my running clock.”

    It reads your running stopwatch and stops it, which saves the time entry.

  • “What did I log for Acme last week?”

    It lists time entries in that date range filtered by customer, with project, service, text and duration.

What your AI can do

Time tracking

Start and stop the stopwatch, list, read and correct time entries, and see a user's work times.

Customers and projects

List, create and update customers, projects and subprojects, with budgets, deadlines and services.

Absences and reports

Create, update and approve absences, and read user reports and project reports with hours and revenue.

  • “How much overtime and holiday does Maria have this year?”

    It reads the user reports for the year with target hours, worked hours, overtime and holidays.

  • “Book a holiday for me from 14 to 18 July.”

    It finds your user ID and creates a holiday absence for those dates.

  • “Which projects are near their budget?”

    It lists project reports with hours and revenue per project so you can compare them with each project's budget.

143 tools for Clockodo

These tools are switched on when you connect. You can switch any of them off, or require your approval before it runs.

  • approve_change_requestVisible to othersApprove a change request (change request id). Has effects visible outside this system.
  • create_absenceChanges dataCreate an absence of a `type` (1 holiday, 4 sick day and so on) from `date_since`, optionally to `date_until`, for a user (`users_id`), half day or with a note.
  • create_access_groupChanges dataCreate a new access group. Required: name.
  • create_change_requestChanges dataCreate a new change request. Required: date, users id or changes.
  • create_customerChanges dataCreate a customer with a `name`, optionally number, note, color, active and billable default.
  • create_favoriteChanges dataCreate a new favorite. Required: name, customers id, services id, color or position.
  • create_favorite_startChanges dataCreate a new start for a favorite.
  • create_holidays_carryChanges dataCreate a new holidays carry. Required: year, users id or count.
  • create_holidays_quotumChanges dataCreate a new holidays quotum. Required: users id, year since or count. Search holidays quota first to avoid duplicates.
  • create_individual_user_access_clearChanges dataCreate a new clear for a individual user access.
  • create_lump_sum_serviceChanges dataCreate a new lump sum service. Required: name or price. Search lump sum services first to avoid duplicates.
  • create_nonbusiness_dayChanges dataCreate a new nonbusiness day. Required: nonbusiness group id, type or name.
  • create_nonbusiness_groupChanges dataCreate a new nonbusiness group. Required: name.
  • create_overtime_carryChanges dataCreate a new overtime carry. Required: year, users id or hours.
  • create_overtime_reductionChanges dataCreate a new overtime reduction. Required: users id, date or hours.
  • create_pageChanges dataCreate a new page. Required: body. Search pages first to avoid duplicates.
  • create_projectChanges dataCreate a project with a `name` under a customer (`customers_id`), optionally budget, deadline, start date and number.
  • create_project_next_intervalChanges dataCreate a new project. Search projects first to avoid duplicates.
  • create_rateChanges dataCreate a new rate. Required: parent rate id or hourly rate.
  • create_registerChanges dataCreate a new register. Required: companies name, name or email.
  • create_service_v4Changes dataCreate a new service v4. Required: name.
  • create_subprojectChanges dataCreate a new subproject. Required: projects id or name. Search subprojects first to avoid duplicates.
  • create_targethourChanges dataCreate a new targethour. Required: users id, type, date since, date until or compensation monthly.
  • create_teamChanges dataCreate a new team. Required: name. Search teams first to avoid duplicates.
  • create_userChanges dataCreate a new user. Required: email, name or role. Search users first to avoid duplicates.
  • create_users_nonbusiness_groupChanges dataCreate a new users nonbusiness group. Required: users id, nonbusiness groups id or date since. Search users nonbusiness groups first to avoid duplicates.
  • delete_absenceDeletesPermanently delete a absence by absence id. Destructive action; may require approval.
  • delete_access_groupDeletesPermanently delete a access group by access group id. Destructive action; may require approval.
  • delete_change_requestDeletesPermanently delete a change request by change request id. Destructive action; may require approval.
  • delete_customerDeletesPermanently delete a customer by customer id. Destructive action; may require approval.
  • delete_entryDeletesDelete one time entry by `page_id` (the entry ID). This cannot be undone.
  • delete_entrygroupsMoves moneyPermanently delete a entrygroup. Financial or irreversible action; may require approval.
  • delete_favoriteDeletesPermanently delete a favorite by favorite id. Destructive action; may require approval.
  • delete_holidays_carryDeletesPermanently delete a holidays carry by holidays carry id. Destructive action; may require approval.
  • delete_holidays_quotumDeletesPermanently delete a holidays quotum by holidays quotum id. Destructive action; may require approval.
  • delete_lump_sum_serviceDeletesPermanently delete a lump sum service by lump sum service id. Destructive action; may require approval.
  • delete_nonbusiness_dayDeletesPermanently delete a nonbusiness day by nonbusiness day id. Destructive action; may require approval.
  • delete_nonbusiness_groupDeletesPermanently delete a nonbusiness group by nonbusiness group id. Destructive action; may require approval.
  • delete_overtime_carryDeletesPermanently delete a overtime carry by overtime carry id. Destructive action; may require approval.
  • delete_overtime_reductionDeletesPermanently delete a overtime reduction by overtime reduction id. Destructive action; may require approval.
  • delete_projectDeletesPermanently delete a project by project id. Destructive action; may require approval.
  • delete_rateDeletesPermanently delete a rate by rate id. Destructive action; may require approval.
  • delete_serviceDeletesPermanently delete a service by service id. Destructive action; may require approval.
  • delete_subprojectDeletesPermanently delete a subproject by subproject id. Destructive action; may require approval.
  • delete_targethourDeletesPermanently delete a targethour by targethour id. Destructive action; may require approval.
  • delete_teamDeletesPermanently delete a team by team id. Destructive action; may require approval.
  • delete_userDeletesPermanently delete a user by user id. Destructive action; may require approval.
  • delete_users_nonbusiness_groupDeletesPermanently delete a users nonbusiness group by users nonbusiness group id. Destructive action; may require approval.
  • get_absenceGet one absence by absence id.
  • get_access_groupGet one access group by access group id.
  • get_current_userGet the Clockodo user the API key belongs to, including their user ID.
  • get_customerGet one customer by `customer_id`.
  • get_customer_projectsGet one customer.
  • get_entryGet one time entry by `page_id` (the entry ID).
  • get_favoriteGet one favorite by favorite id.
  • get_holidays_carryGet one holidays carry by holidays carry id.
  • get_holidays_quotumGet one holidays quotum by holidays quotum id.
  • get_lump_sum_serviceGet one lump sum service by lump sum service id.
  • get_nonbusiness_dayGet one nonbusiness day by nonbusiness day id.
  • get_nonbusiness_groupGet one nonbusiness group by nonbusiness group id.
  • get_overtime_carryGet one overtime carry by overtime carry id.
  • get_overtime_reductionGet one overtime reduction by overtime reduction id.
  • get_projectGet one project by `project_id`, including budget and deadline.
  • get_rateGet one rate by rate id.
  • get_running_clockGet the currently running stopwatch (clock), optionally for another user by `users_id`.
  • get_serviceGet one service by service id.
  • get_subprojectGet one subproject by subproject id.
  • get_targethourGet one targethour by targethour id.
  • get_teamGet one team by team id.
  • get_userGet one user by `user_id`.
  • get_userreportGet one userreport by userreport id.
  • get_users_nonbusiness_groupGet one users nonbusiness group by users nonbusiness group id.
  • list_absencesList absences (holidays, sick days and more), filtered in `filter` by user, year or status.
  • list_access_group_projectsList projects for a access group.
  • list_access_group_servicesList services for a access group.
  • list_access_groupsList access groups.
  • list_change_requestsList change requests. Optional filters: date since, date until, items per page, scope, sort or status. Results are paginated.
  • list_customersList customers, with `filter.fulltext` to search by name and `filter.active`, plus paging and sort.
  • list_entriesList time entries between `time_since` and `time_until` (ISO date-times), filtered in `filter` by user, customer, project, service, text or billable.
  • list_favoritesList favorites.
  • list_holidays_carriesList holidays carries. Optional filters: users id or year.
  • list_individual_user_access_projectsList projects for a individual user access.
  • list_individual_user_access_servicesList services for a individual user access.
  • list_nonbusiness_daysList nonbusiness days. Optional filters: nonbusiness group id or year.
  • list_nonbusiness_groupsList nonbusiness groups.
  • list_overtime_carriesList overtime carries. Optional filters: users id or year.
  • list_overtime_reductionsList overtime reductions. Optional filters: users id.
  • list_project_reportsList project reports with hours and revenue per project, filtered and paged.
  • list_projectsList projects, filtered in `filter` (for example by customer, active or full text), with paging and sort.
  • list_projects_2List projects.
  • list_ratesList rates.
  • list_servicesList services (activity types) used on time entries, with filter and paging.
  • list_services_2List services.
  • list_subprojectsList subprojects, filtered in `filter` (for example by project), with paging.
  • list_subscriptionsList subscriptions.
  • list_targethoursList targethours. Optional filters: users id.
  • list_user_reportsList user reports (target hours, worked hours, overtime, holidays) for a `year`; `type` sets month/week/day detail.
  • list_usersList co-workers (users) in the Clockodo account, with filter and paging.
  • list_work_timesList a user's work times (clock-in/out periods) for `users_id` between `date_since` and `date_until`.
  • search_entries_textsSearch entries texts by filter, items, mode or term. Use this to find existing entries texts before creating a new entries text.
  • search_entrygroupsSearch entrygroups by calc also revenues for projects with hard budget, filter, grouping, prepend customer to project name, round to minutes or time since. Use this to find existing entrygroups before creating a new entrygroup.
  • search_holidays_quotaSearch holidays quota by filter, users id or year. Use this to find existing holidays quota before creating a new holidays quotum.
  • search_lump_sum_servicesSearch lump sum services by filter, items per page or sort. Use this to find existing lump sum services before creating a new lump sum service. Results are paginated.
  • search_reportsSearch reports by filter, items per page or sort. Use this to find existing reports before creating a new report. Results are paginated.
  • search_teamsSearch teams by filter, items per page, scope or sort. Use this to find existing teams before creating a new team. Results are paginated.
  • search_users_nonbusiness_daysSearch users nonbusiness days by filter, items per page or year. Use this to find existing users nonbusiness days before creating a new users nonbusiness day. Results are paginated.
  • search_users_nonbusiness_groupsSearch users nonbusiness groups by filter or items per page. Use this to find existing users nonbusiness groups before creating a new users nonbusiness group. Results are paginated.
  • start_clockChanges dataStart the stopwatch for time tracking: `customers_id` and `services_id` required, optionally `projects_id`, `subprojects_id`, `text` and `billable`.
  • stop_clockDeletesStop the running stopwatch by `clock_id`, which saves the time entry. Optionally set `time_until`.
  • submit_projectVisible to othersComplete a project (project id). Has effects visible outside this system.
  • submit_subprojectVisible to othersComplete a subproject (subproject id). Has effects visible outside this system.
  • update_absenceChanges dataUpdate an absence by `absence_id`: dates, type, status (approve or decline), half day or notes.
  • update_access_groupChanges dataUpdate an existing access group identified by access group id.
  • update_access_group_customersVisible to othersUpdate an existing customer identified by access groups id. Has effects visible outside this system.
  • update_access_group_projectsVisible to othersUpdate an existing project identified by access groups id. Has effects visible outside this system.
  • update_access_group_servicesVisible to othersUpdate an existing service identified by access groups id. Has effects visible outside this system.
  • update_clockChanges dataUpdate an existing clock identified by clock id.
  • update_customerChanges dataUpdate a customer by `customer_id`: name, number, note, active flag or billable default.
  • update_customersVisible to othersUpdate an existing customer identified by access groups id. Has effects visible outside this system.
  • update_defaultsVisible to othersUpdate an existing default. Has effects visible outside this system.
  • update_entryChanges dataUpdate a time entry by `page_id` (the entry ID): change times, duration, text, billable, customer, project or service.
  • update_entrygroupsVisible to othersUpdate an existing entrygroup. Has effects visible outside this system.
  • update_favoriteChanges dataUpdate an existing favorite identified by favorite id.
  • update_holidays_carryChanges dataUpdate an existing holidays carry identified by holidays carry id.
  • update_holidays_quotumChanges dataUpdate an existing holidays quotum identified by holidays quotum id.
  • update_individual_user_access_customersVisible to othersUpdate an existing customer identified by users id. Has effects visible outside this system.
  • update_individual_user_access_projectsVisible to othersUpdate an existing project identified by users id. Has effects visible outside this system.
  • update_individual_user_access_servicesVisible to othersUpdate an existing service identified by users id. Has effects visible outside this system.
  • update_lump_sum_serviceChanges dataUpdate an existing lump sum service identified by lump sum service id.
  • update_nonbusiness_dayChanges dataUpdate an existing nonbusiness day identified by nonbusiness day id.
  • update_nonbusiness_groupChanges dataUpdate an existing nonbusiness group identified by nonbusiness group id.
  • update_overtime_carryChanges dataUpdate an existing overtime carry identified by overtime carry id.
  • update_overtime_reductionChanges dataUpdate an existing overtime reduction identified by overtime reduction id.
  • update_projectChanges dataUpdate a project by `project_id`: name, budget, deadline, active flag, note or customer.
  • update_project_billedChanges dataUpdate an existing project identified by project id.
  • update_rateChanges dataUpdate an existing rate identified by rate id.
  • update_rate_sortsVisible to othersUpdate an existing sort identified by rate id. Has effects visible outside this system.
  • update_serviceChanges dataUpdate an existing service identified by service id.
  • update_subprojectChanges dataUpdate an existing subproject identified by subproject id.
  • update_targethourChanges dataUpdate an existing targethour identified by targethour id.
  • update_teamChanges dataUpdate an existing team identified by team id.
  • update_userChanges dataUpdate an existing user identified by user id.
  • update_users_nonbusiness_groupChanges dataUpdate an existing users nonbusiness group identified by users nonbusiness group id.

Set up in three steps

  1. 1

    Pick the app

    Create a free HeyMyApps account and choose Clockodo from the app list.

  2. 2

    Paste your key

    Paste three values: your Clockodo login email, your API key and an application identification. You find the API key in Clockodo under the menu item Personal data (Persönliche Daten). Changing your Clockodo password makes the API key invalid, so you would need to paste a new one.

  3. 3

    Add the link to your AI

    You get a personal MCP link. Add it to Claude, ChatGPT or Cursor:

    1. Click your name, then Settings › Connectors › Add custom connector.
    2. Paste your link as the Remote MCP server URL.
    3. Switch it on from the + menu in a chat.

Questions

What can the AI do in Clockodo?

The AI can read customers, projects, subprojects, services, users, time entries, work times, the running stopwatch, absences, user reports and project reports. It can start and stop the stopwatch, update and delete time entries, create and update customers and projects, and create and update absences, including approving or declining them.

Does the AI see my Clockodo credentials?

No. Your Clockodo login email, API key and application identification are encrypted at rest and never shown to the AI. After you save them, they are not shown again, not even to you. The AI only sees the results of the tools it calls.

Can I control what the AI is allowed to do?

Yes. You choose which tools are switched on, so you can start read-only. Stopping the clock saves a time entry, and deleting a time entry cannot be undone, so those tools can require your approval before they run. Every tool call is logged.

Does it work with ChatGPT?

Yes. In ChatGPT, open Settings › Apps & Connectors › Advanced, turn on Developer mode and add your HeyMyApps link. Developer mode needs a paid ChatGPT plan: Plus, Pro, Business or Enterprise. The same link also works in Claude (Settings › Connectors › Add custom connector), Cursor and other MCP clients.

What does it cost?

HeyMyApps has a free plan with no credit card required. Paid plans bill per completed task. You also need your own Clockodo account.

Why did my Clockodo connection stop working?

Clockodo invalidates the API key when you change your Clockodo password. Copy the new API key from Personal data (Persönliche Daten) in Clockodo and paste it into HeyMyApps again. Your MCP link stays the same.

Let your AI work in Clockodo today.

Start free. Your key stays encrypted, and you decide what the AI may do.

Connect Clockodo free

HeyMyApps is not affiliated with Clockodo. Product names are trademarks of their owners.