# mcp-server MCP server

TrackingTime MCP server for profile, events, users, projects, tasks, customers, and services.

## Links
- Registry page: https://www.getdrio.com/mcp/io-github-trackingtime-mcp-server
- Repository: https://github.com/TrackingTime/mcp-server
- Website: https://trackingtime.co

## Install
- Endpoint: https://mcp.trackingtime.co/mcp
- Auth: Auth required by registry metadata

## Setup notes
- Remote header: X-API-Key (required; secret)
- Remote header: X-API-Key (required; secret)
- The upstream registry signals required auth or secrets.
- Remote endpoint: https://mcp.trackingtime.co/mcp
- Header: X-API-Key
- Remote endpoint: https://mcp.trackingtime.co/sse
- Header: X-API-Key

## Tools
- 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 app_password/api_token or X-API-Key; does not return full account-wide analytics. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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 global account-level events, set filter=COMPANY (or use list_company_events). Limitations: from and to are required; results are paginated; only returns data accessible to the authenticated account. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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 admin/project manager for full account listing). Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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, ARCHIVED, TRACKING). If filter is not provided, it is not sent to the API. Limitations: read-only; visibility depends on account permissions. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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 must belong to the authenticated account context. Endpoint: https://mcp.trackingtime.co/mcp
- 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, and permissions depend on role. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- track_task - Starts tracking time using /tasks/track. Supports tracking an existing task or creating/tracking by task and project names. Limitations: write operation; task/project resolution depends on the provided identifiers. Endpoint: https://mcp.trackingtime.co/mcp
- stop_task - Stops tracking a running task using /tasks/stop/:task_id. Supports optional stop date and returning the updated task. Limitations: write operation; the task must be currently trackable in the target account. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp
- 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. Endpoint: https://mcp.trackingtime.co/mcp

## Resources
Not captured

## Prompts
Not captured

## Metadata
- Owner: io.github.TrackingTime
- Version: 1.0.2
- Runtime: Sse, Streamable Http
- Transports: HTTP
- License: Not captured
- Language: Not captured
- Stars: Not captured
- Updated: Mar 6, 2026
- Source: https://registry.modelcontextprotocol.io