Skip to content
Clockodo logo

Clockodo MCP server

Time tracking made easy

Clockodo is not a separate install. One Activepieces MCP server exposes it alongside 760+ other apps, behind a single URL.

Tools
33
Works with
Any MCP client
Auth
Custom auth
License
MIT, open source
Updated
September 2026

About the Clockodo MCP server

Connect Clockodo once in Activepieces and every action it ships becomes a tool your assistant can call, behind the same server URL as the rest of your apps. Your agent reaches Clockodo and 760+ other apps over a single connection, on our cloud or a self-hosted install.

Tools

Clockodo tools your AI can run

Once connected, your assistant can call any of these Clockodo actions by asking in plain language.

  • Create Entry

    Creates an entry in clockodo

    8 fields

  • Get Entry

    Retrieves a single entry from clockodo

    1 field

  • Get Entries

    Fetches entries from clockodo

    10 fields

  • Update Entry

    Updates an entry in clockodo

    8 fields

  • Delete Entry

    Deletes an entry in clockodo

    1 field

  • Create Customer

    Creates a customer in clockodo

    6 fields

  • Get Customer

    Retrieves a single customer from clockodo

    1 field

  • Update Customer

    Updates a customer in clockodo

    7 fields

  • Get Customers

    Fetches customers from clockodo

    2 fields

  • Delete Customer

    Deletes a customer in clockodo

    1 field

  • Create Project

    Creates a project in clockodo

    9 fields

  • Get Project

    Retrieves a single project from clockodo

    1 field

  • Get Projects

    Fetches projects from clockodo

    3 fields

  • Update Project

    Updates a project in clockodo

    13 fields

  • Delete Project

    Deletes a project in clockodo

    1 field

  • Create Service

    Creates a service in clockodo

    4 fields

  • Get Service

    Retrieves a single service from clockodo

    1 field

  • Update Service

    Updates a service in clockodo

    5 fields

  • Get Services

    Fetches services from clockodo

  • Delete Service

    Deletes a service in clockodo

    1 field

  • Get Team

    Retrieves a single team from clockodo

    1 field

  • Get Teams

    Fetches teams from clockodo

  • Get User

    Retrieves a single user from clockodo

    1 field

  • Get Users

    Fetches users from clockodo

  • Create User

    Creates a user in clockodo

    10 fields

  • Update User

    Updates a user in clockodo

    12 fields

  • Delete User

    Deletes a user in clockodo

    1 field

  • Create Absence

    Creates a absence in clockodo

    8 fields

  • Get Absence

    Retrieves a single absence from clockodo

    1 field

  • Update Absence

    Updates an absence in clockodo

    8 fields

  • Get Absences

    Fetches absences from clockodo

    2 fields

  • Delete Absence

    Deletes an absence in clockodo

    1 field

  • Custom API Call

    Make a custom API call to a specific endpoint

    10 fields

Triggers

Clockodo events your agent can watch

These start a run the moment something happens in Clockodo, so work gets picked up on its own.

  • New Entry

    Triggers when a new time entry is created

  • New Absence Enquiry

    Triggers when a new absence enquiry is created

Give your assistant Clockodo

Connect Clockodo once and every tool above is callable from Claude, Cursor or any MCP client, behind the same server URL as 760+ other apps. Free to start.

Clockodo MCP, answered.

No. That is the point of it. One Activepieces server exposes Clockodo alongside every other piece you connect, so your client keeps a single connection.

Yes. Activepieces is open source and free to start, and the MCP server is included on every plan, from the free cloud tier to any self-hosted deployment.

Connect Clockodo in Activepieces, enable the server under Settings → MCP Server, then paste your server URL into your client config. It authenticates over OAuth on first use.

It can call 33 tools, including Create Entry, Get Entry, Get Entries, and chain them with steps in other apps inside the same run.

Connections use OAuth2 with limited scopes and are stored under 256-bit encryption, with no API to read them back, so an agent gets scoped access rather than your keys.