io.github.TrackingTime/mcp-server
io.github.TrackingTime/mcp-server · v1.0.2 · MCP 2025-11-25
TrackingTime MCP server for profile, events, users, projects, tasks, customers, and services.
Reachability
reachable
checked 2026-07-14 03:57 UTC
Registry status active
Tools pinned 26
d6df990a37d0
Tools last changed
unchanged since first capture 2026-07-14
Provenance
Registry namespace io.github.TrackingTime
(GitHub-account verified by the official registry)
Repository
github.com/trackingtime/mcp-server
Website
https://trackingtime.co
Remote endpoints
https://mcp.trackingtime.co/mcp (streamable-http)
https://mcp.trackingtime.co/sse (sse)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-07-14 03:57 | first capture | 26 tools pinned |
Pinned tool definitions (26)
| Tool | Description |
|---|---|
| get_me | Returns the authenticated user's profile from /me (user_id, account_id and identity fields). Use this first to discover account context before calling list/get tools. Limitations: read-only; requires valid credentials via... |
| list_workspaces | Lists available workspaces/accounts for the authenticated user, including account_id and selected workspace flag. Use this when multiple workspaces exist and you need to choose account_id before other tools. |
| list_events | Lists time events from /events for a date range. Supports filters by USER, PROJECT, CUSTOMER, TASK, or COMPANY, plus pagination and sort order. If filter/id are missing, it defaults to USER and auto-resolves the caller user_id. For... |
| list_company_events | Lists company-level events from /events using filter=COMPANY. Use this for global metrics (for example, total hours by user in a period) without iterating user-by-user. Requires from/to and does not require id. |
| get_event | Fetches one time event by event_id from /events/{id}. Use when you already have an event identifier and need full event detail. Limitations: requires a valid event_id in the same accessible account context; read-only. |
| list_users | Lists account users from /users. Supports filters and optional billing/team/employee expansion. Use this to discover users before calling user-specific tools. Limitations: read-only; visibility depends on role permissions (typically... |
| get_user | Gets a single user from /users/:id. Use when you already have a user id and need detailed profile data. Limitations: read-only; access to other users depends on role permissions. |
| list_user_tasks | Lists tasks assigned to a user from /users/:id/assigned_tasks, grouped by project. By default (without filter) this endpoint returns the user's active assigned tasks. Use filter only when you explicitly need another subset (ALL,... |
| list_user_projects | Lists projects assigned to a user from /users/:user_id/projects. Use to scope project context for a specific person. Limitations: read-only; returns only projects visible in the authenticated account context. |
| list_user_trackables | Lists user trackables from /users/:id/trackables (projects and tasks grouped by project). Supports favorite-only mode and project/task filtering options. Limitations: read-only; payload size can grow on large accounts. |
| list_projects | Lists projects from /projects with optional status filter (ALL, ACTIVE, ARCHIVED). Use for project discovery before task/event queries. Limitations: read-only listing; filter values are restricted to ALL/ACTIVE/ARCHIVED. |
| list_tasks | Lists tasks from /tasks, optionally scoped by project_id and status filter (ALL, ACTIVE, ARCHIVED). Use after selecting a project to narrow task context. Limitations: read-only; project_id must exist in the same account context when provided. |
| create_task | Creates a new task using POST /tasks/add. Supports assigning users, linking to a project, custom fields and billable flag. Limitations: write operation; requires permissions to create tasks in the target account/project. |
| get_task | Gets a specific task from /tasks/:task_id. By default this tool requests include_custom_fields=true so task custom fields are returned unless explicitly disabled. Use when you need full task details by id. Limitations: read-only; task... |
| update_task | Updates an existing task using /tasks/update/:task_id. Supports changing description, due date, project/service linkage, assignees, billing fields and custom fields. Limitations: write operation; task must exist in the target account,... |
| create_customer | Creates a new customer using POST /customers/add. Supports adding custom field values during creation. Limitations: write operation; requires permissions in the target account. |
| update_customer | Updates an existing customer using /customers/update/:customer_id. Supports renaming the customer and updating custom field values. Limitations: write operation; customer must exist in the target account. |
| create_project | Creates a new project using POST /projects/add. Supports linking a customer, custom fields, public visibility and estimated time. Limitations: write operation; requires permissions to create projects in the target account. |
| update_project | Updates an existing project using /projects/update/:project_id. Supports core project fields, billing fields, customer/service linkage, notes and custom fields. Limitations: write operation; project must exist in the target account. |
| create_event | Creates a new time event using POST /events/add. Supports linking to a task or project, optional notes, repeating configuration and custom fields. Limitations: write operation; start, end and timezone are required. |
| update_event | Updates an existing time event using /events/update/:event_id. Supports changing task/project linkage, start/end timestamps, notes, user and custom fields. Limitations: write operation; event must exist in the target account. |
| track_task | Starts tracking time. With task_id, calls POST /tasks/track/:task_id. Without task_id, calls /tasks/track/ with query fields such as task_name and project_name/project_id. Limitations: write operation; provide either task_id or a... |
| stop_task | Stops tracking a running task using /tasks/stop/:task_id. Requires date in YYYY-MM-DD HH:MM:SS format and timezone as an IANA timezone (for example Europe/Stockholm). Agents should derive the current local date/time and IANA timezone... |
| create_custom_field | Creates a new custom field using POST /custom_fields/add. Supports task, project, event, user and customer custom fields. Limitations: write operation; value_type and filter_object_class are required. |
| create_enum_option | Creates a new enum option for an existing custom field using POST /enum_options/add. Limitations: write operation; requires an existing enum custom field id. |
| list_customers | Lists customers from /customers with optional status filter (ALL, ACTIVE, ARCHIVED). Use to map customer entities before querying related projects/events. Limitations: read-only listing; filter values are restricted to ALL/ACTIVE/ARCHIVED. |
Status badge
[](https://toolpin.dev/servers/io.github.TrackingTime/mcp-server)
Maintain this server? Add the badge to your README — it links your users to this live status page.