MCP tools reference

The Everhour MCP server registers 28 tools, all prefixed everhour_. You don’t call them by name — your AI client picks the right tool from your request and fills in the details. This reference is handy when you’re debugging a connection or want to see exactly what an assistant can do. The example prompts below are just that — examples. Phrase requests however you like; the client maps them to the right tool. Durations are always in seconds, and dates use YYYY-MM-DD (more).

Behavior hints

Each tool is annotated so well-behaved clients know how to treat it. Most are marked read-only and never change data — clients can run them without asking you first. Seven tools carry the destructive hint, so Claude, Cursor, and ChatGPT prompt you to confirm before running them:

everhour_start_timer
everhour_start_timer_without_task
everhour_stop_timer
everhour_log_time
everhour_update_time_entry
everhour_delete_time_entry
everhour_favorite_task

The hint marks a tool that changes state you can notice, not just one that deletes. Starting a timer stops whichever timer was already running, so it earns the prompt too.

This page describes what each tool does, not its full call signature. Parameters appear below only where the behaviour is non-obvious — everything else is in the JSON Schema the server publishes. Call the MCP tools/list method for the authoritative, live set of names, schemas, and annotations; this page mirrors it rather than replacing it.

Timer

Tool	Description	Example
`everhour_get_current_timer`	Get the running timer and its elapsed time, or none if nothing is running.	”Is my timer running?”
`everhour_start_timer`	Start the timer on a task. Switches from any timer already running — that one stops and keeps its elapsed time. Starting on the task already running keeps the elapsed time but replaces the comment with the one sent now, so omitting `comment` clears the existing one rather than leaving it.	”Start a timer on the login bug.”
`everhour_start_timer_without_task`	Start a timer that isn’t tied to a task, identified by its comment alone. Teams can forbid tracking without a task, in which case the call is rejected with that reason.	”Start a timer for the standup.”
`everhour_stop_timer`	Stop the currently running timer.	”Stop my timer.”

Timer state lives on the server and changes outside the conversation — the web app, browser extension, and mobile apps all start and stop the same timer.

Time records

These tools carry time_entry in their names; the record they act on is what concepts.mdx calls a time record.

Tool	Description	Example
`everhour_log_time`	Log manual time on a task. When exactly one record already exists for the same task, date, and user, this adds to that record instead of creating a second one — logging 30m twice on one task and date leaves 1h.	”Log 2 hours to the API docs task.”
`everhour_update_time_entry`	Set an existing record to a new duration, date, or comment. Unlike `everhour_log_time`, this replaces the duration rather than adding to it.	”Change yesterday’s design entry to 90 minutes.”
`everhour_delete_time_entry`	Clear a time record: its duration becomes 0 and its comment is removed. The record itself is not deleted — it stays on the same task and date and still appears in timesheets with 0 time.	”Clear the time I logged to the wrong task.”
`everhour_get_user_time`	Raw time records for one user over a date range, set with `from` and `to`. `user_id` picks whose — it defaults to `me`, so pass a team member’s ID to read theirs. One row per record with its date, duration, comment, and task. No totals, no pagination — the range is capped at 31 days.	”How much did Alex track last week?”
`everhour_get_my_timesheet`	One week of a timesheet with server-computed daily totals and a per-task breakdown. `week` takes `YYYY-MM-DD` for any date inside your own week, `<userId>:YYYY-MM-DD` for another member’s, or a numeric week ID.	”Show my timesheet for this week.”

everhour_update_time_entry with time: 0 clears the record instead of updating it. The duration goes to 0, the comment is removed, and a date or task sent in the same call is silently ignored — the same outcome as everhour_delete_time_entry. To move a record to another date, send a non-zero time.

Pick by shape of the answer: everhour_get_my_timesheet for one week with totals, everhour_get_user_time for raw entries over any month, and everhour_get_dashboard with dashboard="months" for totals across a longer period.

Tasks

Tool	Description	Example
`everhour_search_tasks`	Search tasks by keyword across all projects or within one project. Use to find a task before logging time.	”Find tasks about onboarding.”
`everhour_recent_tasks`	Tasks you tracked most recently, newest record first. When there isn’t enough history to fill the limit, the tail is padded — first your favorites, then your timesheet tasks, then the newest tasks of your projects. A task listed here wasn’t necessarily tracked at all. Default `limit` 15, max 30. With `project_id`, padding stays inside that project and only the last month of tracking counts.	”What have I worked on recently?”
`everhour_get_task`	Get a single task by ID including time tracked and estimate data.	”Show details for the checkout task.”
`everhour_list_tasks`	Every task of one project, filtered by name when `query` is given. There’s no sort order and no sorting parameter, so a `limit` smaller than the project returns an arbitrary subset — not the newest tasks — and stable paging isn’t guaranteed. Default `limit` is 50.	”List the tasks in the Website project.”
`everhour_resolve_platform_ids`	Convert platform-specific task IDs (Asana, Jira, GitHub, and others) to Everhour IDs. Use when someone provides a task URL or ID from an integration.	”Track time on this pasted Asana link.”

Call everhour_list_platforms to validate a platform code before everhour_resolve_platform_ids. This pair turns a pasted Asana or Jira URL into the right Everhour task to log against.

Favorites

Tool	Description	Example
`everhour_list_favorite_tasks`	Your personal shortlist of pinned tasks. Rows come back in storage order rather than sorted by `position`, so sort on it when the pinned order matters. Rows are typed: `task` carries the task, `comment` is a saved timer comment for tracking without a task, and `section` is a folder header.	”What are my starred tasks?”
`everhour_favorite_task`	Pin a task to your favorites, or unpin it when `favorite` is false. Passing the state it already has leaves it unchanged.	”Pin the checkout task to my favorites.”

Projects & clients

Tool	Description	Example
`everhour_list_projects`	Projects you have access to, one page at a time. Teams run to thousands of projects, so narrow with `query` or page through rather than expecting the whole list. Default `limit` is 50.	”What projects do I have?”
`everhour_get_project`	Get a single project by ID including client association and billing info.	”Show the Website Redesign project.”
`everhour_list_clients`	List clients, optionally filtered by name.	”List my clients.”
`everhour_get_client`	Get a single client by ID. Requires admin access — `everhour_list_clients` is open to every member, but a single client isn’t.	”Show details for the Acme account.”

Team

Tool	Description	Example
`everhour_get_me`	Get the current authenticated user’s profile, role, and team info.	”What’s my role and team?”
`everhour_list_team_users`	List all team members with their roles and capacity.	”List everyone on my team.”

Reporting

Tool	Description	Example
`everhour_get_dashboard`	Aggregated team report for a date range — one row per member, project, client, team group, week, or month. Money columns appear only for roles allowed to see them.	”How many hours did the team log by project last month?”
`everhour_get_project_budgets`	Budget report — budget, spent, remaining, and progress per project. Current status, so no date range. Filter by `project_id`, `client_id`, `billing`, `budget_type`, or `budget_period`. `project_status` defaults to `open`, so pass `archived` to see closed projects. Requires billing/budgets access.	”Which projects are over budget?”
`everhour_get_time_off`	Team time-off assignments that overlap a date range. Only approved assignments are returned — pending and declined requests aren’t visible. Requires supervisor access.	”Who’s out on time off next week?”
`everhour_get_users_capacity`	Weekly capacity per team member: capacity against logged, billable, and remaining time. Requires admin access.	”What’s each teammate’s capacity this week?”

Dashboard views

everhour_get_dashboard is one tool with a dashboard selector, so it covers reports the Everhour app splits across several screens. Every view shares the same date range, the optional member_id / project_id / client_id filters, and columns to request a subset of fields.

`dashboard`	Shows	Example
`users`	Time, billing, cost, and profit per member	”How much did each teammate track in May?”
`team-hours`	Tracked time vs. time off, overtime, and capacity per member	”Show tracked hours against capacity this month.”
`payroll`	Payroll, overtime, and gross pay per member (needs cost access)	“Show payroll for May — overtime and gross pay.”
`projects`	Time and cost per project	”How many hours went to each project in April?”
`clients`	Time and cost per client (needs admin)	“Break down the team’s time by client for Q2.”
`team-groups`	Totals per team group	”Compare tracked hours across team groups this quarter.”
`months`	Totals per calendar month	”Show tracked time month by month this year.”
`weeks`	Totals per calendar week	”How did weekly tracked time trend over the last two months?”
`timecards`	Clock-in/out summary per member (needs supervisor)	“Summarize the team’s clock-in and clock-out last week.”

Omit member_id for the whole team, or name a person to scope to one member. Limited members are narrowed to themselves in every view except team-hours.

A money column you can’t see comes back as 0, not missing. Costs, billable amount, profit, expenses, and their sub-columns are zeroed for callers without the matching role. A 0 there means “not visible to this caller”, never “no money” — don’t report it as an amount. Columns gated by role alone (billable amount, costs, and profit for non-admins; payroll without cost access) are absent from the response entirely, which is the case you can safely detect.

Platforms

Tool	Description	Example
`everhour_list_platforms`	List supported integration platforms and their 2-letter codes. Use to validate platform codes before calling `everhour_resolve_platform_ids`.	”Which integrations can I resolve task IDs from?”

Guide

Tool	Description	Example
`everhour_get_instructions`	The Everhour usage guide, written for the assistant rather than for you: units and date rules, which timesheet tool answers which question, how permissions shape a report, how to format the result. Pass `section` for one part of it, or omit `section` for the whole guide.	—

This is the one tool nobody asks for by name. The server sends a short set of instructions when your client connects, and hosts truncate that at 2 KB — so the rest of the guide lives here, and a client fetches the part it needs while working. section takes one of six values:

`section`	Covers
`basics`	Domain model, units, date and week rules
`workflows`	Timers, logging time, finding tasks, favorites, platform IDs
`timesheet`	Reading a timesheet and raw entries without wrong totals
`reporting`	Team dashboards, money columns, permissions
`formatting`	Output format, chart choice, brand palette
`troubleshooting`	Best practices and what error answers mean

The same guide is also published as an MCP resource, for hosts that read resources instead of calling tools. everhour://instructions returns the whole guide, and the everhour://instructions/{section} template returns one section — the same six names as above.

Interactive cards

Thirteen of the 28 tools return an interactive card alongside their text result, so the answer is something you can act on rather than read. The server publishes four card templates as MCP resources under ui://everhour/:

Card	Shows	Returned by
`timer`	Running task, elapsed time, and a Stop button	`everhour_get_current_timer`, `everhour_start_timer`, `everhour_start_timer_without_task`, `everhour_stop_timer`
`tasks`	Task list where every row starts a timer	`everhour_search_tasks`, `everhour_recent_tasks`, `everhour_list_tasks`, `everhour_list_favorite_tasks`
`task`	One task with project, assignees, estimate, status, tags, and your time on it	`everhour_get_task`, `everhour_log_time`, `everhour_favorite_task`
`timesheet`	Month grid or week list, switchable, with daily and weekly totals	`everhour_get_my_timesheet`, `everhour_get_user_time`

Cards are served with the text/html;profile=mcp-app MIME type and render in clients that support MCP Apps. Everywhere else the same answer arrives as text, with nothing missing. Actions inside a card call Everhour directly, so a timer you stop in a card is stopped everywhere — the web app, the browser extension, and the mobile apps. See Everhour in Claude for what the cards look like in use, and Data, privacy, and permissions for the links a card is allowed to open.

Get started

API basics

OAuth 2.1

MCP server

MCP tools reference

Behavior hints

Timer

Time records

Tasks

Favorites

Projects & clients

Team

Reporting

Dashboard views

Platforms

Guide

Interactive cards

​Behavior hints

​Timer

​Time records

​Tasks

​Favorites

​Projects & clients

​Team

​Reporting

​Dashboard views

​Platforms

​Guide

​Interactive cards

Behavior hints

Timer

Time records

Tasks

Favorites

Projects & clients

Team

Reporting

Dashboard views

Platforms

Guide

Interactive cards