TrackingTime MCP Server のリモート MCP サーバーとは何ですか?
TrackingTime MCP Server のリモート MCP サーバーは、https://mcp.trackingtime.co/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。
@TrackingTime
基本情報
Official MCP server for TrackingTime (trackingtime.co). Query time entries, projects, tasks, customers, and team productivity data from Claude, Cursor, or any MCP-compatible AI client. Read-only. Works with HTTP transports.
https://mcp.trackingtime.co/mcpclaude mcp add trackingtime-mcp-server --transport http https://mcp.trackingtime.co/mcpReturns 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.
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.
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.
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.
Lists report-filtered WORK and SCHEDULE events from /events/filtered using one JSON query_data payload. Use this when you need precise event searches by project, task, user, customer, notes, billing fields, numeric report fields, or custom fields without first discovering legacy filter/id combinations. Required: date_range.period, date_range.start and date_range.end. Use date_range.period=custom_range with YYYY-MM-DD dates; all/all_time are not supported. The API excludes events from DELETED projects and returns results ordered by event start date descending.
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.
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).
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.
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.
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.
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.
Gets account/workspace settings from /account. Use for account-level configuration and metadata. Limitations: read-only; visibility depends on account role.
Updates account/workspace settings using /account/update. Limitations: write operation; requires admin-level permissions.
Updates a user profile/settings using /users/update/:user_id. Limitations: write operation; requires permission to manage users.
Invites one or more users to the account using /users/invite. Limitations: write operation; requires permission to invite users.
Assigns projects to a user using /users/:user_id/projects/assign. Limitations: write operation; project/user visibility depends on role.
Archives/closes a user using /users/close/:user_id. Limitations: destructive write operation; requires user-management permissions.
Restores/reopens an archived user using /users/open/:user_id. Limitations: write operation; requires user-management permissions.
Lists user groups/teams from /user_groups. Limitations: read-only; visibility depends on account role.
Gets a user group/team by id from /user_groups/:user_group_id. Limitations: read-only.
Creates a user group/team using /user_groups/add. Limitations: write operation; requires permission to manage groups.
Updates a user group/team using /user_groups/update/:user_group_id. Limitations: write operation; changing membership may affect access.
Deletes a user group/team using /user_groups/delete/:user_group_id. Limitations: destructive write operation.
Lists projects from /projects with optional status filter (ALL, ACTIVE, ARCHIVED, FOLLOWING). Use for project discovery before task/event queries. Limitations: read-only listing.
Gets a specific project from /projects/:project_id/min. Supports detail flags for tasks, task lists, closed tasks and custom fields. Limitations: read-only; project must belong to the authenticated account context.
Lists users assigned to a project from /projects/:project_id/users. Limitations: read-only.
Gets project time totals from /projects/times. Use for project-level accumulated time lookups. Limitations: read-only; pass project IDs or filters supported by the API.
Archives/closes a project using /projects/close/:project_id. Limitations: write operation; affects project visibility.
Restores/reopens an archived project using /projects/open/:project_id. Limitations: write operation.
Deletes a project using /projects/delete/:project_id. Limitations: destructive write operation.
Duplicates a project using /projects/duplicate/:project_id. Limitations: write operation; supports extra API parameters via passthrough.
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.
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.
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.
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.
Archives/closes a task using /tasks/close/:task_id. Limitations: destructive write operation; task must exist in the target account.
Restores/reopens an archived task using /tasks/open/:task_id. Limitations: write operation; task must exist in the target account.
Deletes a task using /tasks/delete/:task_id. Limitations: destructive write operation.
Lists comments for a task using /tasks/:task_id/comments. Limitations: read-only; visibility depends on task access.
Adds a comment to a task using /tasks/:task_id/comments/add. Limitations: write operation.
Deletes a task comment using /comments/delete/:comment_id. Limitations: destructive write operation.
Lists task history/log entries using /tasks/:task_id/logs. Limitations: read-only.
Updates tasks in batch using /tasks/batch/update. Limitations: destructive write operation; payload replaces/updates fields according to API behavior.
Creates a new customer using POST /customers/add. Supports adding custom field values during creation. Limitations: write operation; requires permissions in the target account.
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.
Gets a specific customer from /customers/:customer_id. Supports include_custom_fields. Limitations: read-only; customer must belong to the authenticated account context.
Archives/closes a customer using /customers/close/:customer_id. Limitations: write operation.
Restores/reopens an archived customer using /customers/open/:customer_id. Limitations: write operation.
Deletes a customer using /customers/delete/:customer_id. Limitations: destructive write operation.
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.
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.
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.
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.
Deletes a time entry using /events/delete/:event_id. Limitations: destructive write operation.
Restores a deleted/archived time entry using /events/restore/:event_id when supported by the API. Limitations: write operation.
Creates time entries in batch using /events/batch/add. Limitations: write operation; accepts API-supported batch payloads.
Updates time entries in batch using /events/batch/update. Limitations: destructive write operation; accepts API-supported batch payloads.
Deletes time entries in batch using /events/batch/delete. Limitations: destructive write operation.
Gets aggregated event/hour summary from /events/summary. Use for totals over date ranges without fetching every event. Limitations: read-only; from/to are required by most summary queries.
Gets aggregate event statistics from /events/stats. Use for metrics over date ranges. Limitations: read-only; from/to are required by most stats queries.
Lists time off requests using GET /timeoffs. Limitations: read-only; accepts API-supported query filters.
Gets one time off request using GET /timeoffs/:timeoff_id. Limitations: read-only.
Creates a time off request using GET /timeoffs/add. Limitations: sensitive write operation; requires confirm=true.
Updates a time off request using GET /timeoffs/:timeoff_id/update. Limitations: sensitive write operation; requires confirm=true.
Deletes a time off request using GET /timeoffs/:timeoff_id/delete. Limitations: destructive write operation; requires confirm=true.
Approves or rejects a time off request using GET /timeoffs/approve/:timeoff_id?token=:token. This endpoint is global and does not prefix account_id. Limitations: sensitive write operation; requires confirm=true.
Lists time off balances using GET /timeoffs/balances. Limitations: read-only.
Gets a user's balance status for a policy using GET /timeoffs/balances/status/:user_id/:policy_id. Limitations: read-only.
Calculates time off amount using GET /timeoffs/calculate_amount. Limitations: read-only calculation.
Lists time off types using GET /timeoffs/types. Limitations: read-only.
Lists time off policies using GET /timeoffs/policies. Limitations: read-only.
Gets one time off policy using GET /timeoffs/policies/:policy_id. Limitations: read-only.
Creates a time off policy using POST /timeoffs/policies/add. Limitations: sensitive write operation; requires confirm=true.
Updates a time off policy using POST /timeoffs/policies/:policy_id/update. Limitations: sensitive write operation; requires confirm=true.
Lists holidays using GET /holidays. Limitations: read-only.
Creates a holiday using GET /holidays/add. Limitations: write operation; confirm is not required by the Excel.
Updates a holiday using POST /holidays/update/:holiday_id. Limitations: write operation; confirm is not required by the Excel.
Deletes a holiday using GET /holidays/delete/:holiday_id. Limitations: destructive write operation; requires confirm=true.
Lists user timecards using POST /timecards/users. Limitations: write-style POST endpoint used for listing; accepts API-supported body fields.
Gets a user's timecard using GET /timecards. Limitations: read-only; typically requires user_id, from and to.
Gets timecards count using GET /timecards/count. Limitations: read-only.
Lists timecard logs using GET /timecards/logs. Limitations: read-only.
Saves or modifies a timecard day using POST /timecards/days/save. Limitations: write operation; accepts API-supported body fields.
Generates a user timecard using GET /timecards/generate. Limitations: write operation; can save generated days when save_days=true.
Exports timecards using GET /timecards/export. Limitations: read-only export; pass data in the API-supported format.
Lists schedules using GET /schedules/. Limitations: read-only.
Gets one schedule using GET /schedules/:schedule_id. Limitations: read-only.
Gets the current schedule for a user using GET /schedules/users/:user_id/current. Limitations: read-only.
Creates a schedule using GET /schedules/add. Limitations: sensitive write operation; requires confirm=true.
Updates a schedule using GET /schedules/update/:schedule_id. Limitations: sensitive write operation; requires confirm=true.
Deletes a schedule using GET /schedules/delete/:schedule_id. Limitations: destructive write operation; requires confirm=true.
Assigns users to a schedule using GET /schedules/:schedule_id/users/assign. Limitations: sensitive write operation; requires confirm=true.
Removes a schedule assignment using GET /schedules/:schedule_id/assignments/delete/:assignment_id. Limitations: sensitive write operation; requires confirm=true.
Lists invoices using GET /invoices. Limitations: read-only.
Gets one invoice using GET /:account_id/invoices/:invoice_id. Limitations: read-only.
Gets the next invoice number using GET /invoices/next_number. Limitations: read-only.
Creates an invoice using POST /:account_id/invoices/add. Limitations: sensitive write operation; requires confirm=true.
Updates an invoice using POST /:account_id/invoices/:invoice_id/update. Limitations: sensitive write operation; requires confirm=true.
Deletes an invoice using POST /invoicing/:account_id/invoices/:invoice_id/delete. Limitations: destructive write operation; requires confirm=true.
Sends an invoice using POST /:account_id/invoices/:invoice_id/send. Limitations: sensitive write operation; requires confirm=true.
Marks an invoice as paid using POST /:account_id/invoices/:invoice_id/pay. Limitations: sensitive write operation; requires confirm=true.
Marks an invoice as void using POST /:account_id/invoices/:invoice_id/void. Limitations: sensitive write operation; requires confirm=true.
Exports an invoice using GET /:account_id/invoices/:invoice_id/export. Limitations: read-only export.
Lists expenses using GET /expenses/. Limitations: read-only.
Gets one expense using GET /expenses/:expense_id. Limitations: read-only.
Creates an expense using GET /expenses/add. Limitations: sensitive write operation; requires confirm=true.
Updates an expense using GET /expenses/:expense_id/update. Limitations: sensitive write operation; requires confirm=true.
Deletes an expense using GET /expenses/:expense_id/delete. Limitations: destructive write operation; requires confirm=true.
Lists expense categories using GET /expenses/categories. Limitations: read-only.
Lists saved/shared reports using GET /docs/. Limitations: read-only; reports are represented by docs in the API.
Gets a saved/shared report using GET /docs/:report_id. Limitations: read-only; report_id maps to doc id.
Creates a saved/shared report using POST /docs/add. Limitations: write operation; confirm is not required by the Excel.
Updates a saved/shared report using POST /docs/:report_id/update. Limitations: write operation; confirm is not required by the Excel.
Deletes one or more saved/shared reports using POST /docs/delete. Limitations: destructive write operation; requires confirm=true.
Refreshes a report share token using GET /docs/:report_id/refresh_token. Limitations: sensitive write operation; requires confirm=true.
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 trackable task/project/service reference.
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 from the user's computer/settings before calling this tool. Limitations: write operation; the task must be currently trackable in the target account.
Lists custom field definitions from /custom_fields. Use this to inspect available custom fields before setting values on tasks, projects, events, users, or customers. Supports pagination and optional object-class/type filters when supported by the TrackingTime API. Limitations: read-only; visibility depends on account permissions.
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.
Gets a custom field definition from /custom_fields/:custom_field_id. Limitations: read-only.
Updates a custom field definition using /custom_fields/update/:custom_field_id. Limitations: destructive write operation; field changes can affect existing records.
Deletes a custom field definition using /custom_fields/delete/:custom_field_id. Limitations: destructive write operation.
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.
Lists enum options for custom fields from /enum_options. Limitations: read-only; optionally filter by custom field when supported by the API.
Updates an enum option using /enum_options/update/:enum_option_id. Limitations: destructive write operation; can affect existing custom-field values.
Deletes an enum option using /enum_options/delete/:enum_option_id. Limitations: destructive write operation.
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.
The official Model Context Protocol (MCP) server for TrackingTime, the time tracking software built for agencies, consultancies, and professional services teams.
Connect Claude, ChatGPT, Cursor, VS Code, Windsurf or any MCP-compatible client to your TrackingTime workspace. Ask about your hours, start and stop timers, log time, and manage projects, tasks and customers in natural language.
https://mcp.trackingtime.co/mcpX-API-Key header is also supported for clients without OAuth.Every action runs with the permissions of the signed-in TrackingTime user.
Add a custom connector with this URL and sign in with TrackingTime when prompted:
https://mcp.trackingtime.co/mcp
{
"mcpServers": {
"trackingtime": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.trackingtime.co/mcp"]
}
}
}
{
"mcpServers": {
"trackingtime": {
"command": "npx",
"args": [
"-y", "mcp-remote", "https://mcp.trackingtime.co/mcp",
"--header", "X-API-Key:${TRACKINGTIME_APP_PASSWORD}"
],
"env": { "TRACKINGTIME_APP_PASSWORD": "<your app password>" }
}
}
}
POST /mcp: MCP over Streamable HTTPGET /health: health check/.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource/mcp: OAuth discoveryThe legacy SSE endpoint (/sse) has been retired.
io.github.TrackingTime/mcp-serverMaintained by the TrackingTime team.
TrackingTime MCP Server のリモート MCP サーバーは、https://mcp.trackingtime.co/mcp にホストされた Model Context Protocol エンドポイントです。AI アシスタントはローカルに何もインストール・実行することなく接続できます。
エンドポイント https://mcp.trackingtime.co/mcp を Claude Code、Cursor、VS Code など任意の MCP 対応クライアントに追加してください。このページのセットアップ手順で各クライアントを一度に設定できます。
はい。TrackingTime MCP Server は OAuth を使用します。初回接続時に MCP クライアントがブラウザを開いてサインイン・認可を行い、以降はその認証情報を再利用します。
TrackingTime MCP Server は stdio エンドポイントを公開しており、これはリモート MCP サーバーで広く使われ、主要な MCP クライアントがサポートするトランスポートです。
One MCP connection for all your Gmail, Google Calendar, Drive and Contacts accounts, Slack workspaces and Notion — free.
Aard connects Macroeconomic and other official data from 170+ publishers including World Bank, IMF, BIS, ECB, Eurostat, and National Statistical Offices. Aard is powered by a large graph of the metadata universe and an
Search and read public data from X/Twitter, Reddit, YouTube, Instagram, TikTok, Facebook, Threads, Bluesky, Trustpilot, Amazon, Google Maps, news, forums and the web. 90+ read-only tools plus ready-made research playbook
Research competitors' winning ads, clone them for your brand and launch paused campaigns on Meta, Google and TikTok from chat.
Remote MCP server that turns Claude, ChatGPT, or Cursor into a full ad workflow: research any brand's live Facebook and TikTok ads, clone the proven winners for your own brand, and launch real campaigns on Google, TikTok
コメント