Integration

timeBuzzer integration

timeBuzzer is a time-tracking app. Record, edit, search and delete activities (time entries) tagged with up to three tiles (for example customer, project, task), mark activities as billed in bulk, and pull grouped report data; manage tiles and which users and groups may track time on them, user groups, and webhooks fired when an activity is created, edited or deleted; read the account, its users, the layers and the available permissions. Updating your own user profile, the deprecated chart views, the desktop client compatibility check and the bare activity count and API version reads are not exposed. Authentication is the API key from your timeBuzzer settings (Settings, API), sent in the Authorization header as APIKey followed by the key.

Connect timeBuzzer How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in timeBuzzer.Built from the 41 timeBuzzer tools below, on the connection you add once.

What you can do with timeBuzzer

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Tile, 6 operations

create_tileCreate tilePOSTCreates a tile (a customer, project, task or other item of a layer) and returns it with its new ID. name and layer are required; parents and children link it to tiles of the adjacent layers.
delete_tileDelete tileDELETEDeletes a tile. A tile that still has activities cannot be deleted (409): move or delete them first, check_tiles_have_activities tells.
get_tileGet tileGETReturns one tile with its name, layer, type, color, description, parent and child tile IDs, archived and favorite flags, external references and assigned users and groups.
list_tilesList tilesGETLists the tiles (customers, projects, tasks and so on) the key's user can see, with name, layer, type, color, parent and child tiles, archived and favorite flags and assigned users and groups.
set_group_tilesSet group tilesPUTReplaces the tiles assigned to a user group with the given list (an empty list removes them all) and returns the group.
update_tileUpdate tilePUTEdits a tile and returns it. name and layer are required (the layer cannot change); users and groups are given as assignedUsers and assignedGroups.

Webhook, 6 operations

create_webhookCreate webhookPOSTCreates a webhook: timeBuzzer will POST the activity to your URL on NewActivity, EditedActivity or DeletedActivity. The target must answer 202, or the activity change is cancelled. The vendor documents no response body.
delete_webhookDelete webhookDELETEDeletes one webhook configuration.
delete_webhooks_by_urlDelete webhooks by urlDELETEDeletes every webhook configuration that targets the given URL.
get_webhookGet webhookGETReturns one webhook configuration: target URL, event, active flag and the names of the headers sent (their values are not returned).
list_webhooksList webhooksGETLists the webhook configurations: ID, target URL, event (NewActivity, EditedActivity or DeletedActivity), active flag and the names of the headers sent (their values are not returned).
update_webhookUpdate webhookPUTUpdates a webhook configuration (url, event, active and requestHeaders are all required). The target must answer 202, or the activity change is cancelled. The vendor documents no response body.

Activity, 5 operations

create_activityCreate activityPOSTCreates an activity (time entry) and returns it with its new ID. userId is required: your own ID (from get_my_user) or a team member's, which needs the ACTIVITY_CREATE_TEAM permission. Fires the NewActivity webhooks.
delete_activityDelete activityDELETEDeletes an activity (time entry) permanently and fires the DeletedActivity webhooks.
get_activityGet activityGETReturns one activity: start and end dates in UTC with their offsets, note, billed flag, owner, tile IDs and lock state (whether it can still be edited).
list_activitiesList activitiesGETLists activities (time entries) with start and end dates, UTC offsets, note, billed flag, owner and tile IDs: your own, or every user's when your key has the ACTIVITY_READ_TEAM permission. Also returns the total count and total duration.
update_activityUpdate activityPUTEdits an activity and fires the EditedActivity webhooks. timeBuzzer expects the whole activity (tiles, dates, offsets, note, userId): read it with get_activity first and resend the values you keep. No response body is documented.

Group, 5 operations

create_groupCreate groupPOSTCreates a user group, optionally with its members and assigned tiles, and returns it.
delete_groupDelete groupDELETEDeletes a user group; its members and tiles are no longer associated with it. Returns a confirmation message.
list_groupsList groupsGETLists the account's user groups, each with its members (ID, name, email) and the tiles assigned to it. Personal data about the members.
set_tile_groupsSet tile groupsPUTReplaces the user groups assigned to a tile with the given list and returns the updated groups.
set_user_groupsSet user groupsPUTAssigns one user to several user groups and returns those groups with their members and tiles.

Bulk, 3 operations

delete_activitiesDelete activitiesDELETEDeletes up to 50 activities permanently and returns how many were deleted. Fires the DeletedActivity webhook for each one, one per second.
delete_tilesDelete tilesDELETEDeletes several tiles (up to 10,000) and returns the counts, the deleted tile IDs and an error per tile that could not be deleted.
set_activities_billedSet activities billedPOSTSets the billed flag of up to 50 activities at once and returns how many were processed. Fires the EditedActivity webhook for each activity, one per second.

User, 3 operations

list_tile_usersList tile usersGETLists the users assigned to a tile, with ID, first and last name and email. Personal data.
set_group_usersSet group usersPUTReplaces the members of a user group with the given users and returns the group.
set_tile_usersSet tile usersPUTReplaces the users assigned to a tile with the given list and returns the tile.

Filter, 2 operations

search_activitiesSearch activitiesPOSTSearches activities by period, users, groups, tiles, note text, billed flag or custom data, sorted and paged; covers every user of the account when your permission allows. Returns the activities, total count and total duration.
search_tilesSearch tilesPOSTSearches tiles by name or custom data text, layers and archived flag and returns the matching tiles.

Layer, 2 operations

get_layerGet layerGETReturns one layer with its name, visibility, index (1 to 3) and parent and child layer IDs.
list_layersList layersGETLists the account's layers (the up to three levels tiles live in, for example Customers, Projects, Tasks) with name, visibility, index and parent and child layer IDs.

Account, 1 operation

get_accountGet accountGETReturns the timeBuzzer account: its ID, available and used licenses, trial start, company settings and every user (ID, name, email, permissions, state and display settings). Personal data about the account's users.

Activities check, 1 operation

check_tiles_have_activitiesCheck tiles have activitiesPOSTTells whether any of the given tiles (up to 10,000) has activities recorded on it, for example before deleting tiles.

All, 1 operation

list_my_assigned_tilesList my assigned tilesGETLists the tiles assigned to the key's user, directly or through a group, with their name, layer, type, parents, children and flags.

Me, 1 operation

get_my_userGet my userGETReturns the user the API key belongs to: ID (needed as userId to create activities), name, email, permissions, state, account ID, display settings, license (FREE, PRO or TRIAL) and account policies.

Meta, 1 operation

get_activity_search_totalsGet activity search totalsPOSTReturns totals for an activity search without the activities: total count, last page number and size for the given count, total and rounded duration, and the comma-separated list of matching activity IDs.

Name, 1 operation

rename_groupRename groupPATCHRenames a user group and returns its ID and new name.

Permission, 1 operation

list_permissionsList permissionsGETLists every permission name timeBuzzer knows (for example ACTIVITY_READ, ACTIVITY_EDIT, ACTIVITY_CREATE), as a list of strings.

Public, 1 operation

set_tile_available_to_allSet tile available to allPUTMakes a tile available to every user of the account for tracking time, or limits it to its assigned users and groups, and returns the tile.

Report, 1 operation

get_reportGet reportPOSTReturns report tables of tracked time: up to 4 reports, each filtered (period, users, tiles, groups, billed, note) and grouped by up to 4 of layer, note, user, group, day, week, month or year, with seconds per row and in total.

Use timeBuzzer from Claude Code, Cursor or Codex

Connect timeBuzzer in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its timeBuzzer operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect timeBuzzer

Create your workspace
Sign up free. Nothing to install.
Connect timeBuzzer once
Add your timeBuzzer connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.