Read Tick clients, projects, tasks, users and time entries; log and edit time entries. Hosted by usefulapi — connect from Claude, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"tick": {
"url": "https://tick.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"tick": {
"type": "http",
"url": "https://tick.usefulapi.io/mcp"
}
}
}Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
The login page asks for your Tick subscription id and Tick API token.
Both values are in Tick under My Profile (the subscription id is also the number in your Tick address, https://www.tickspot.com/12345/...). The token belongs to one user and one subscription and acts with that user's rights. Your token is used only to call the Tick API on your behalf; it is never shown to anyone.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Tick subscription id and Tick API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
| Tool | Type | What it does |
|---|---|---|
tick_list_clients | read | 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 | read | Get client One client by id, with a summary of its projects (count and URL). GET /clients/{id}.json. |
tick_list_projects | read | 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 | read | 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 | read | 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, /projects/{id}/tasks.json or /projects/{id}/tasks/closed.json. |
tick_get_task | read | 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 | read | 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 | read | List time 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 page. GET /entries.json. |
tick_get_entry | read | Get time entry One time entry by id, with its task. GET /entries/{id}.json. |
tick_create_entry | write | Log time 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 | Update time 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 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 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 task WRITE: create a new task on a project (POST /tasks.json). Tick administrators only. Creates a new task every call. |
tick_usage_status | Usage status (free-tier meter) Report the caller's current free-tier usage this month: calls used, monthly limit, remaining, and whether the cap is reached. Read-only; does not count against the meter. | |
tick_request_feature | Request a missing feature Tell usefulapi that the user needs something the Tick tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
tick_upgrade | Upgrade to Pro (unlimited) Subscribe to the Pro plan for UNLIMITED Tick tool calls (the free tier caps monthly usage). Choose monthly ($9/month) or yearly ($90/year — 2 months free) billing. Returns a Stripe Checkout link to open in your browser; after payment your account upgrades automatically. Does not count against the meter. | |
tick_cancel_subscription | Cancel the Pro subscription Cancel the caller's Tick Pro subscription at the end of the paid period (no refund for the current period; unlimited calls continue until then, then the free tier applies). Requires confirm: true. Run tick_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 100 tool calls / month |
| Proper account | $9/mo · $90/yr | Unlimited |
Pro covers this Tick server only. Subscribe with tick_upgrade (it returns a Stripe Checkout link). Cancel any time with tick_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running tick_upgrade before then undoes the cancel. Or write to [email protected].
No. usefulapi is an independent service. It is not affiliated with or endorsed by Tick. The server calls the Tick API with your own Tick access, so it sees only the data that your account can see.
The login page asks for your Tick subscription id and Tick API token. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your Tick subscription id and Tick API token. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the Tick API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in Tick.
Yes, if you approve it. 5 of the 14 Tick tools can create or change data. The other 9 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 100 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls, for this Tick server only. Run tick_usage_status to see how many calls you used.
Ask the AI to run tick_upgrade: it returns a Stripe Checkout link. To cancel, run tick_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with tick_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.