Integration

Tick integration

Tick is a time tracking tool that tracks hours against project and task budgets. Log time entries on tasks, list entries by date range or by last change with billable, billed, project, task and user filters, mark an entry billed or correct its hours, read clients, projects, tasks and users, and create clients, projects, tasks and users (creating clients, projects, tasks and users is for administrators of the subscription). Left out: deleting records, updating clients, projects and tasks, the closed-projects, closed-tasks, all-clients and deleted-users lists, the per-user, per-project and per-task entry lists (list_entries filters the same way), and the roles call that returns API tokens. Users (names, emails) and time entries (who worked on what, when, with notes) are personal data. Authentication is the API token of your Tick role, sent as Authorization: Token token=<token>, with the subscription id (the number in the Tick API URL) and a User-Agent naming your application and a contact email, which Tick requires on every call.

Connect Tick How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Tick

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.

Entry, 4 operations

create_entryCreate entryPOSTLogs a time entry on a task. user_id is ignored unless the caller is an administrator.
get_entryGet entryGETReturns one time entry with the task it was logged on.
list_entriesList entriesGETLists time entries between start_date and end_date, or those created or changed after updated_at. Each entry identifies who logged it (user_id), with hours and notes: personal data.
update_entryUpdate entryPUTUpdates only the fields passed on a time entry (date, hours, notes, task, billed flag); fields left out keep their value. Answers the updated entry.

Task, 4 operations

create_taskCreate taskPOSTCreates a task in a project. Administrators only (403 otherwise).
get_taskGet taskGETReturns one task with its total hours entered, a summary of its entries and its project.
list_project_tasksList project tasksGETLists the open tasks of one project.
list_tasksList tasksGETLists the open tasks across all projects.

Client, 3 operations

create_clientCreate clientPOSTCreates a client. Administrators only (403 otherwise).
get_clientGet clientGETReturns one client with a summary of its projects (count and when they last changed).
list_clientsList clientsGETLists the clients that have open projects, up to 100 per page.

Project, 3 operations

create_projectCreate projectPOSTCreates a project, without tasks (time cannot be entered until a task exists). Administrators only.
get_projectGet projectGETReturns one project with its total hours entered, a summary of its tasks and its client.
list_projectsList projectsGETLists the open projects of the subscription, up to 100 per page.

User, 2 operations

create_userCreate userPOSTAdds a user to the subscription. Administrators only.
list_usersList usersGETLists the users of the subscription with their names, emails and time zones (personal data). Administrators see everyone; other users see only themselves.

Use Tick from Claude Code, Cursor or Codex

Connect Tick in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Tick 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 Tick

Create your workspace
Sign up free. Nothing to install.
Connect Tick once
Add your Tick 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.