Tick MCP by usefulapi

Last 30 days

Uptime

100%

Response time

287 ms typical, 287 ms slowest 5%

Last check

3 h ago

Next check

in 4 h

How to call it

Add it to any MCP client that supports remote servers.

{
  "mcpServers": {
    "tick-mcp-by-usefulapi": {
      "type": "http",
      "url": "https://tick.usefulapi.io/mcp"
    }
  }
}

14 tools

• tick_list_clients

  List Tick clients. By default only clients that have open projects; set include_all=true for every client (also archived or without projects). 100 per page. GET /clients.json or /clients/all.json.

• tick_get_client

  One client by id, with a summary of its projects (count and URL). GET /clients/{id}.json.

• tick_list_projects

  List Tick projects with budget (hours or money), billable flag, client_id and owner_id. Open projects by default; status=closed for closed ones. 100 per page. GET /projects.json or /projects/closed.json.

• tick_get_project

  One project by id, with total_hours entered, a summary of its tasks (count and URL) and its client. GET /projects/{id}.json.

• tick_list_tasks

  List Tick tasks (the budget lines that time entries are logged against). Across all projects, or for one project when project_id is given. Open tasks by default; status=closed for closed ones. You need a task id to log time. 100 per page. GET /tasks.json, /tasks/closed.json, /pro

• tick_get_task

  One task by id, with total_hours entered, a summary of its entries (count and URL) and its project. GET /tasks/{id}.json.

• tick_list_users

  List the users of the Tick subscription (id, name, e-mail, timezone). A non-administrator sees only themself. Use deleted=true for removed users who still have time entries (administrators only). GET /users.json or /users/deleted.json.

• tick_list_entries

  List time entries. Tick requires EITHER start_date AND end_date (entries dated in that range) OR updated_at (entries created or changed after that time). Optional filters: project_id, task_id, user_id, billable, billed. Each entry has date, hours, notes, task_id, user_id. 100 per

• tick_get_entry

  One time entry by id, with its task. GET /entries/{id}.json.

• tick_create_entry

  WRITE: log a new time entry on a task (POST /entries.json). Needs the task id (see tick_list_tasks). hours is a decimal (1.5 = 1h30m). user_id is only honored for administrators (otherwise the entry is yours). Creates a new entry every call; nothing is sent to anyone.

• tick_update_entry

  WRITE: change an existing time entry (PUT /entries/{id}.json): hours, notes, date, task, or mark it billed. Only the fields you pass change; the previous values are overwritten.

• tick_create_client

  WRITE: create a new client (POST /clients.json). Tick administrators only (403 otherwise). Creates a new client every call.

• tick_create_project

  WRITE: create a new project (POST /projects.json). Tick administrators only. The project has no tasks: create at least one with tick_create_task before time can be logged. Creates a new project every call.

• tick_create_task

  WRITE: create a new task on a project (POST /tasks.json). Tick administrators only. Creates a new task every call.

Security scan

• No findings. We scan names, descriptions and tool definitions for hidden instructions and other prompt-injection patterns.

Recent checks