A Model Context Protocol (MCP) server for interacting with Microsoft 365 and Office services through the Graph API
Tick MCP by usefulapi is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Read Tick clients, projects, tasks, users and time entries; log and edit time entries.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http tick-mcp-by-usefulapi https://tick.usefulapi.io/mcp
# 2 — ask your agent for something these tools do
# tick_list_clients, tick_get_client, tick_list_projects and 11 more
Tick MCP by usefulapi costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http tick-mcp-by-usefulapi https://tick.usefulapi.io/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| include_all | boolean | no | true = all clients, false/omitted = only clients with open projects. |
| page | integer | no | Page number, from 1 (default 1; 100 records per page). Pass the previous reply's next_page. |
One client by id, with a summary of its projects (count and URL). GET /clients/{id}.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| client_id | integer | yes | Tick client id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | open (default) or closed. |
| page | integer | no | Page number, from 1 (default 1; 100 records per page). Pass the previous reply's next_page. |
One project by id, with total_hours entered, a summary of its tasks (count and URL) and its client. GET /projects/{id}.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | Tick project id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | no | Only the tasks of this project. |
| status | string | no | open (default) or closed. |
| page | integer | no | Page number, from 1 (default 1; 100 records per page). Pass the previous reply's next_page. |
One task by id, with total_hours entered, a summary of its entries (count and URL) and its project. GET /tasks/{id}.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | integer | yes | Tick task id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| deleted | boolean | no | true = deleted users that have time entries. |
| page | integer | no | Page number, from 1 (default 1; 100 records per page). Pass the previous reply's next_page. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| start_date | string | no | First day of the range (with end_date). |
| end_date | string | no | Last day of the range (with start_date). |
| updated_at | string | no | Only entries created or modified after this time (instead of a date range). |
| project_id | integer | no | Only entries of this project. |
| task_id | integer | no | Only entries of this task. |
| user_id | integer | no | Only entries of this user. |
| billable | boolean | no | Only billable (true) or non-billable (false) entries. |
| billed | boolean | no | Only billed (true) or not yet billed (false) entries. |
| page | integer | no | Page number, from 1 (default 1; 100 records per page). Pass the previous reply's next_page. |
One time entry by id, with its task. GET /entries/{id}.json.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entry_id | integer | yes | Tick entry id. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| task_id | integer | yes | Task to log the time on. |
| date | string | yes | Day the work was done, yyyy-mm-dd. |
| hours | number | yes | Hours worked, decimal (1.5 = one and a half hours). |
| notes | string | no | What was done. |
| user_id | integer | no | Administrators only: log the time for this user. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| entry_id | integer | yes | Entry to change. |
| hours | number | no | New hours (decimal). |
| notes | string | no | New notes (replaces the old notes). |
| date | string | no | New date, yyyy-mm-dd. |
| task_id | integer | no | Move the entry to this task. |
| billed | boolean | no | Mark the entry as billed / not billed. |
WRITE: create a new client (POST /clients.json). Tick administrators only (403 otherwise). Creates a new client every call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Client name. |
| archive | boolean | no | Create the client archived (default false). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| name | string | yes | Project name. |
| client_id | integer | yes | Client the project belongs to (see tick_list_clients). |
| budget | number | no | Project budget (hours, or money for a money-based subscription). |
| billable | boolean | no | Whether the project is billable. |
| notifications | boolean | no | Send budget notifications. |
| recurring | boolean | no | Recurring budget. |
| owner_id | integer | no | User id of the project owner. |
WRITE: create a new task on a project (POST /tasks.json). Tick administrators only. Creates a new task every call.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_id | integer | yes | Project the task belongs to. |
| name | string | yes | Task name. |
| budget | number | no | Task budget (hours). |
| billable | boolean | no | Whether the task is billable. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Tick MCP by usefulapi or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Tick MCP by usefulapi can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.