# Tick Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Tick

Log and manage time entries, projects, tasks and clients in Tick time tracking.

- Record: https://musedirectory.ai/connector/tick
- Category: Productivity
- Developer: usefulapi (https://usefulapi.io/tick/)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 26ms, checked 2026-10-29T10:45:49Z
- Endpoint: https://tick.usefulapi.io/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-10-29T12:51:26Z)
- Source: Found in the official MCP Registry (io.usefulapi/tick) https://registry.modelcontextprotocol.io/v0/servers?search=io.usefulapi%2Ftick

Connect to Tick time tracking to read and log time entries, manage projects and tasks, view clients and users, and track billable hours and budgets. Requires a Tick account and administrator access for creating clients and projects.

Example request: "Log 2.5 hours of work on the website redesign task for today with notes about what was completed."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Tick to help me. It is a free service with an MCP server at https://tick.usefulapi.io/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

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.

Screening checks:
- MCP handshake: pass (Answered in 3ms)
- Domain against threat feeds (Cloudflare security DNS): pass (tick.usefulapi.io, usefulapi.io not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (14 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (No concerns)