> ## Documentation Index
> Fetch the complete documentation index at: https://developers.everhour.com/llms.txt
> Use this file to discover all available pages before exploring further.
# MCP tools reference
> The 24 tools the Everhour MCP server exposes, grouped by area, with example prompts.
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](/dates-and-timezones)).
### 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
| Tool | Description | Example |
| ---------------------------- | ------------------------------------------------------------------------------------------- | ----------------------------------- |
| `everhour_get_current_timer` | Get the currently running timer for the authenticated user, or null if no timer is running. | *"Is my timer running?"* |
| `everhour_start_timer` | Start a timer on a task. Search for the task first to get its ID. | *"Start a timer on the login bug."* |
| `everhour_stop_timer` | Stop the currently running timer. | *"Stop my timer."* |
## Time entries
| Tool | Description | Example |
| ---------------------------- | ------------------------------------------------------------------------------- | -------------------------------------------------- |
| `everhour_log_time` | Log a manual time entry for a task. Time is in seconds. Date defaults to today. | *"Log 2 hours to the API docs task."* |
| `everhour_update_time_entry` | Update an existing time entry (duration, date, or comment). | *"Change yesterday's design entry to 90 minutes."* |
| `everhour_delete_time_entry` | Delete a time entry. | *"Delete the time I logged to the wrong task."* |
| `everhour_get_user_time` | Get time entries for a user within a date range. Max 31 days per request. | *"How much did Alex track last week?"* |
| `everhour_get_my_timesheet` | Get the current user's weekly timesheet with daily totals and task breakdown. | *"Show my timesheet for this week."* |
## Tasks
| Tool | Description | Example |
| ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------ | ------------------------------------------ |
| `everhour_search_tasks` | Search tasks by keyword across all projects or within a specific project. Use to find tasks before logging time. | *"Find tasks about onboarding."* |
| `everhour_recent_tasks` | Get recently tracked tasks. Shows tasks you worked on recently — use before searching by keyword. | *"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` | List tasks within a specific project. Requires project\_id. | *"List the tasks in the Website project."* |
| `everhour_resolve_platform_ids` | Convert platform-specific task IDs (Asana, Jira, GitHub, etc.) to Everhour IDs. Use when the user 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.
## Projects & clients
| Tool | Description | Example |
| ------------------------ | ---------------------------------------------------------------------------------- | -------------------------------------- |
| `everhour_list_projects` | List projects accessible to the user. Use to find project IDs before logging time. | *"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. | *"Show details for the Acme account."* |
## Team
| Tool | Description | Example |
| -------------------------- | ------------------------------------------------------------ | ----------------------------- |
| `everhour_get_me` | Get current authenticated user 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. Requires budget access. | *"Which projects are over budget?"* |
| `everhour_get_time_off` | Team time-off assignments that overlap a date range. Requires admin access. | *"Who's out on time off next week?"* |
| `everhour_get_users_capacity` | Weekly capacity per team member. 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 and optional `member_id` / `project_id` / `client_id` filters.
| `dashboard` | Shows | Example |
| ------------- | --------------------------------------------------------------- | --------------------------------------------------------------- |
| `users` | Time, billing, and cost 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. 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
| 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?"* |