Skip to main content
The Everhour MCP server registers 24 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. Read-only tools (most get_/list_/search_ tools) never change data. Write tools are marked accordingly, and everhour_delete_time_entry carries the destructive hint — Claude, Cursor, and ChatGPT prompt you to confirm before running it.
The tool set can change over time. For the authoritative, live list, use the MCP tools/list method — this page mirrors the current set.

Timer

Time entries

Tasks

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.

Projects & clients

Team

Reporting

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 and optional member_id / project_id / client_id filters. Omit member_id for the whole team, or name a person to scope to one member. Money views (payroll and cost columns elsewhere) and the clients and timecards views need the matching cost, admin, or supervisor role — without it, those columns or views are left out.

Platforms