Everhour
A workspace-scoped time tracking platform. Reads follow a strict project hierarchy; writes cover resource CRUD plus live timers and time entries.
Resource hierarchy (top down)
- Client → Project → Section → Task → Time record
- Project → Time record (project-scoped feed)
- User (member) → Time record, Timecard
- Project → Expense (categorized via Expense Category)
- Webhook (workspace-wide, optionally project-scoped)
A project can belong to at most one client; reassigning an already-attached project to a different client errors with HTTP 400. Tasks and sections are created under a parent project but updated and deleted by their own resource id. There is no workspace-wide task list — list tasks one project at a time.
ID formats (this catches people out)
- Native Everhour resources (project, task) use string ids prefixed ev: — e.g. ev:195526947697395. Imported integration projects use as: (Asana), jira:, trello:. Only native ev: projects accept create, update, and delete.
- Numeric ids for clients, sections, tags, users, expenses, expense categories, webhooks, and time records.
- Composite key for timecards: (user_id, date). Both are always required on read-single, upsert, and delete.
Time records
Read with one tool that branches on scope: no scope for the team feed, project_id for one project, task_id for one task (aggregate plus per-history detail), user_id for one user. from_date and to_date (YYYY-MM-DD, inclusive) only narrow the team and user feeds.
Add time against a task id (minimum 60 seconds, maximum 36000 per call). Delete by the numeric record id on the time entry — not an ev:… task id and not a row inside .history[]. Individual records are not updated in place; the service appends history rows, so correcting an entry means delete then re-add.
Timers
There is exactly one current timer per user. Starting a new timer auto-stops any running one for the same user and saves the accrued seconds as a TIMER history entry on the previous task. Stop is a no-op when no timer is running.
Everhour admins can cap weekly hours per user. When the cap is hit, start-timer and time-entry writes return HTTP 400 with a weekly-limit message — contact the workspace admin; MCPBundles credentials are not the issue.
Money units
Currency amounts (project budget, hourly rate, expense amount, line item totals) are integers in the lowest currency unit (cents). Hours / durations are integers in seconds.
Permissions
The connected credential is scoped to a single user in a single workspace. Mutations run as that user. Admin-only operations (creating users, editing tag definitions, sending invoices) remain in the Everhour admin UI.
