# Timix.AI (remote · api.timix.ai)

Time tracking, live project budgets, and billing exports for service firms.

- Trust score: 75/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `api.timix.ai`: 75/100 (this document), [markdown](https://verifymcp.io/servers/ai-timix-time-tracking/api-integration-v1-mcp.md), [page](https://verifymcp.io/servers/ai-timix-time-tracking/api-integration-v1-mcp)

## Channel facts

- Endpoint: `https://api.timix.ai/api/integration/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 89/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 63/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 16024 tokens (~140/item across 114 items; 114 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-timix-time-tracking https://api.timix.ai/api/integration/v1/mcp
```

### Codex

```toml
[mcp_servers.ai-timix-time-tracking]
url = "https://api.timix.ai/api/integration/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-timix-time-tracking": {
      "type": "remote",
      "url": "https://api.timix.ai/api/integration/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-timix-time-tracking --url https://api.timix.ai/api/integration/v1/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-timix-time-tracking:
    url: "https://api.timix.ai/api/integration/v1/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-timix-time-tracking": {
      "type": "http",
      "url": "https://api.timix.ai/api/integration/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-02 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 74, +5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 69)

First indexed and scored.

## MCP tools (114)

### `get_hours_summary` (~119 tokens)

Get a summary of hours logged for a user or team over a date range

Input parameters:

- `end_date` (string, required): End date for the summary period (ISO 8601 format, e.g. 2026-01-31)
- `scope` (string): Scope of the summary: 'user' for individual user hours, 'team' for organization-wide overview. Defaults to 'user'.
- `start_date` (string, required): Start date for the summary period (ISO 8601 format, e.g. 2026-01-01)

### `get_dashboard_metrics` (~55 tokens)

Get organization dashboard metrics including utilization, revenue, and active projects

Input parameters:

- `month` (string): Month to get metrics for in YYYY-MM format (e.g. 2026-01). Defaults to current month if not provided.

### `get_customer_info` (~39 tokens)

Get detailed information about a customer including health score and portfolio

Input parameters:

- `customer_id` (string, required): The unique identifier of the customer to retrieve information for

### `get_project_status` (~40 tokens)

Get detailed project status including budget, hours, and task breakdown

Input parameters:

- `project_id` (string, required): The unique identifier of the project to retrieve status for

### `get_billing_report` (~67 tokens)

Get billing summary for a customer over a date range

Input parameters:

- `customer_id` (string, required): The customer ID to get billing report for
- `end_date` (string, required): End date in YYYY-MM-DD format
- `start_date` (string, required): Start date in YYYY-MM-DD format

### `get_budget_alerts` (~26 tokens)

Get all budget alerts for the organization showing projects that are over or near budget

### `list_customers` (~16 tokens)

List all customers in the organization

### `list_projects` (~37 tokens)

List all projects in the organization with their status and budget information

Input parameters:

- `customer_id` (string): Optional customer ID to filter projects by customer

### `get_my_time_entries` (~105 tokens)

Get the current user's time entry analytics for a date range, including hours breakdown by project and customer, billable vs non-billable split, and target comparison

Input parameters:

- `end_date` (string, required): End date for the analytics period (ISO 8601 format, e.g. 2026-01-31)
- `start_date` (string, required): Start date for the analytics period (ISO 8601 format, e.g. 2026-01-01)

### `get_resource_utilization` (~95 tokens)

Get team resource utilization summary showing target hours, actual hours, billable hours, and utilization percentage for the organization

Input parameters:

- `end_date` (string, required): End date for the utilization period (ISO 8601 format, e.g. 2026-01-31)
- `start_date` (string, required): Start date for the utilization period (ISO 8601 format, e.g. 2026-01-01)

### `get_unbilled_time` (~38 tokens)

Get a summary of unbilled time across the organization, including total hours, total amount, number of entries, and aging information

### `get_budget_health` (~40 tokens)

Get overall budget health summary for the organization, including project counts by status (on-track, warning, critical), total remaining budget hours, and active alerts

### `get_employee_timesheet` (~99 tokens)

Get an employee's timesheet report showing target hours, actual hours logged, and variance. Can look up by employee name or default to the requesting user.

Input parameters:

- `employee_name` (string): Name of the employee to look up. Leave empty or say 'me' for your own timesheet.
- `end_date` (string, required): End date in YYYY-MM-DD format
- `start_date` (string, required): Start date in YYYY-MM-DD format

### `list_my_time_entries` (~152 tokens)

List the current user's own individual time entries for a date range, with project name, task/subtask ids, hours, description, billable flag and status. Use this to see exactly what was logged (the per-entry detail), as opposed to aggregated totals.

Input parameters:

- `end_date` (string, required): End date of the range (ISO 8601 format, e.g. 2026-01-31)
- `limit` (integer): Optional maximum number of entries to return (1-200, default 200). Entries are returned most-recent first.
- `start_date` (string, required): Start date of the range (ISO 8601 format, e.g. 2026-01-01)

### `find_billing_work` (~121 tokens)

Find the projects, tasks and subtasks in your organization where time can be tracked, optionally filtered by a name fragment. Use this to locate where to record work. Returns ids and names only.

Input parameters:

- `max_results` (integer): Optional maximum number of rows to return (1-50, default 50).
- `project_id` (string): Optional project id to drill into. When supplied, returns that project's tasks and subtasks.
- `query` (string): Optional case-insensitive name fragment to filter projects (or tasks when project_id is supplied).

### `get_project_team` (~121 tokens)

Get the people associated with a project: who is ASSIGNED to it (formally responsible / accountable) and the TOP CONTRIBUTORS by hours logged (who is actually doing the work and driving the budget/overrun). Use this to answer 'who is responsible for / working on a project', especially when a project is over budget. Budget-alert results include the project_id you can pass directly into this tool.

Input parameters:

- `project_id` (string, required): The unique identifier of the project. Resolve a project name to its ID with find_billing_work or list_projects first.

### `log_time` (~189 tokens)

Create a single time entry on a subtask for the current user. Requires permission to log time.

Input parameters:

- `date` (string, required): Date of the work (ISO 8601 format, e.g. 2026-01-15).
- `hours` (number, required): Number of hours worked (greater than 0 and at most 24).
- `start_time` (string): Optional start time of day in 24-hour HH:mm (e.g. "12:00"). Set this when the user gives a specific time or a time range (and put the range length in 'hours'); the entry then runs from this time for…
- `subtask_id` (string, required): Id of the subtask to log time against. All time entries are recorded at the subtask level.
- `text` (string): Optional description of the work performed.

### `suggest_holiday_profile` (~165 tokens)

Look up the official public/national holidays for a country (ISO-2 code, e.g. US, IL, GB) and year from an authoritative public source (Hebcal for Israel, Nager.Date for everywhere else). Returns a DRAFT list of holiday dates: each is either a full day off or a half/partial working day (with a start/end working window). Use this to PROPOSE a holiday profile — never invent holiday dates from memory. The dates returned are authoritative for that exact year.

Input parameters:

- `country` (string, required): ISO-2 country code (two letters), e.g. "US", "IL", "GB", "DE".
- `year` (integer, required): The calendar year to look up holidays for (e.g. 2026).

### `create_holiday_profile` (~411 tokens)

Create and SAVE a national-holiday profile for the organization for a specific year, AFTER the user has explicitly reviewed and confirmed the holiday list. Each holiday is either a full day off or a half/partial working day (with a start/end working window). Holiday dates MUST come from suggest_holiday_profile or the user — never invent dates. Only call this once the user has confirmed; do not call it to preview.

Input parameters:

- `default_for_countries` (string): Optional comma-separated ISO-2 country codes this profile is the country-default for (for its year), e.g. "US" or "US,CA".
- `holidays` (string, required): A JSON array (as a string) of the confirmed holidays, each an object: {"date":"YYYY-MM-DD","name":"...","full_day_off":true|false,"window_start":"HH:mm","window_end":"HH:mm"}. Dates must be within th…
- `name` (string, required): A descriptive profile name, e.g. "US Holidays 2026" or "Israel 2026".
- `notes` (string): Optional free-text notes about this profile.
- `set_as_default` (boolean): Optional. Set this profile as the organization's default holiday set for its year.
- `source` (string): Provenance of the dates: "hebcal", "nager", "manual", or "ai". Use the source returned by suggest_holiday_profile.
- `year` (integer, required): The calendar year this profile governs (e.g. 2026). It applies only to its year.

### `create_customer` (~135 tokens)

Create a new billing customer in your organization. The organization is fixed by your context - never pass an organization id.

Input parameters:

- `contact_email` (string): Optional primary contact email address.
- `country` (string): Optional country.
- `currency` (string): Optional ISO 4217 currency code (e.g. USD, EUR). Defaults to USD.
- `description` (string): Optional customer description (max 200 characters).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `name` (string, required): Customer name (required).

### `create_project` (~215 tokens)

Create a new billing project under one of your customers. The organization is fixed by your context; customer_id must be a customer in your organization. Discover ids with find_billing_work - never ask the user for an id.

Input parameters:

- `billing_type` (string, required): Billing type to allow on the project (required). One of: TM, Fix, OVH.
- `create_general_activity` (boolean): Optional. When true (the default for this tool), also create a default visible "General" task + activity so time can be logged on the project immediately. Set false to create an empty project with no…
- `customer_id` (string, required): Id of the customer this project belongs to (required). Must be a customer in your organization.
- `description` (string): Optional project description (max 500 characters).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `name` (string, required): Project name (required).

### `create_task` (~178 tokens)

Create a task under a project. Tasks group the subtasks that time is logged against. The task inherits its allowed billing types from the parent project. Discover ids with find_billing_work - never ask the user for an id.

Input parameters:

- `create_general_activity` (boolean): Optional. When true (the default for this tool), also create a default visible "General" activity under the task so time can be logged immediately. Set false to create a task with no activities yet.
- `description` (string): Optional task description.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `name` (string, required): Task name (required).
- `project_id` (string, required): Id of the parent project (required). Must be a project in your organization.

### `create_subtask` (~140 tokens)

Create a subtask under a task. All time entries are logged against subtasks, so every task needs at least one. The subtask inherits a valid billing type from the parent task. Discover ids with find_billing_work - never ask the user for an id.

Input parameters:

- `description` (string): Optional subtask description.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `name` (string, required): Subtask name (required).
- `task_id` (string, required): Id of the parent task (required). Must be a task in your organization.

### `invite_user` (~160 tokens)

Invite a person to join your organization by email at a chosen role. The organization is fixed by your context - never pass an organization id. Valid roles: Admin, Finance, Manager, Member, Viewer (you can only invite at a role no more privileged than your own). The invitee receives an email with an acceptance link.

Input parameters:

- `email` (string, required): Email address of the person to invite (required).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `role` (string, required): Role to grant on acceptance (required). One of: Admin, Finance, Manager, Member, Viewer. You cannot invite at a role more privileged than your own.

### `assign_user_to_project` (~175 tokens)

Assign a member to a project so they can see it and log time against its tasks. Identify the member by email (preferred) or by org_user_id, and the project by project_id (discover ids with find_billing_work - never ask the user for an id). The organization is fixed by your context.

Input parameters:

- `email` (string): Email of the member to assign (preferred). Provide this OR org_user_id.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `org_user_id` (string): Organization-user id of the member to assign. Provide this OR email.
- `project_id` (string, required): Id of the project to assign the member to (required). Must be a project in your organization.

### `update_org_settings` (~293 tokens)

Update core settings for your organization: name, country, default_time_zone, base_currency, first_day_of_month (1-28), auto_close_month_after_days, and the budget alert thresholds (budget_warning_threshold_percent must be less than budget_critical_threshold_percent). The organization is fixed by your context - never pass an organization id. Only the fields you provide are changed; everything else is left as-is.

Input parameters:

- `auto_close_month_after_days` (integer): Auto-close a month this many days after it ends (0 = never).
- `base_currency` (string): Base ISO 4217 currency code (e.g. USD, EUR).
- `budget_critical_threshold_percent` (integer): Utilization % at which a project is flagged Over-Budget (must be greater than the warning threshold).
- `budget_warning_threshold_percent` (integer): Utilization % at which a project is flagged At-Risk (must be less than the critical threshold).
- `country` (string): Organization country.
- `default_time_zone` (string): Default IANA/Windows time zone id (e.g. America/New_York).
- `first_day_of_month` (integer): Day the billing month starts (1-28).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `name` (string): Organization display name.

### `update_customer` (~217 tokens)

Update an existing billing customer in your organization. Only the fields you provide are changed; everything else is left as-is (PATCH semantics). Discover ids with find_billing_work - never ask the user for an id.

Input parameters:

- `contact_email` (string): Primary contact email address.
- `contact_name` (string): Primary contact person name.
- `contact_phone` (string): Primary contact phone number.
- `country` (string): Customer country.
- `currency` (string): ISO 4217 currency code (e.g. USD, EUR).
- `customer_id` (string, required): Id of the customer to update (required). Must be a customer in your organization.
- `description` (string): Customer description (max 200 characters).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `name` (string): New customer name (2-50 characters).
- `status` (string): Customer status. One of: Active, Inactive.

### `update_project` (~292 tokens)

Update an existing billing project in your organization. Only the fields you provide are changed (PATCH semantics). You can rename the project, update its description, change its status, toggle which billing types are allowed (TM/Fix/OVH), and set per-type hour limits. Discover ids with find_billing_work - never ask the user for an id.

Input parameters:

- `billing_types` (string): Comma-separated list of billing types to allow on this project. One or more of: TM, Fix, OVH. Replaces the entire set — include all types you want to keep.
- `description` (string): Project description (max 500 characters).
- `fix_hour_limit` (integer): Fixed-price hour limit for this project (0 = unlimited).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `name` (string): New project name.
- `ovh_hour_limit` (integer): Overhead hour limit for this project (0 = unlimited).
- `project_id` (string, required): Id of the project to update (required). Must be a project in your organization.
- `status` (string): Project status. One of: Active, OnHold, Completed, Cancelled.
- `tm_hour_limit` (integer): T&M (Time & Materials) hour limit for this project (0 = unlimited).

### `update_task` (~223 tokens)

Update an existing task in your organization. Only the fields you provide are changed (PATCH semantics). You can rename the task, update its description, change its status, and set per-type hour limits. Discover ids with find_billing_work - never ask the user for an id.

Input parameters:

- `description` (string): Task description.
- `fix_hour_limit` (integer): Fixed-price hour limit for this task (0 = unlimited).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `name` (string): New task name.
- `ovh_hour_limit` (integer): Overhead hour limit for this task (0 = unlimited).
- `status` (string): Task status. One of: Active, Inactive, Completed.
- `task_id` (string, required): Id of the task to update (required). Must be a task in your organization.
- `tm_hour_limit` (integer): T&M (Time & Materials) hour limit for this task (0 = unlimited).

### `update_subtask` (~234 tokens)

Update an existing subtask in your organization. Only the fields you provide are changed (PATCH semantics). You can rename the subtask, update its description, change its status, billing type, and set an hour limit. Discover ids with find_billing_work - never ask the user for an id.

Input parameters:

- `billing_type` (string): Billing type for this subtask. One of: TM, Fix, OVH. Must be allowed by the parent task.
- `description` (string): Subtask description.
- `hour_limit` (integer): Hour limit for this subtask (0 = unlimited). Validated against the parent task's limit for the subtask's billing type.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `name` (string): New subtask name.
- `status` (string): Subtask status. One of: Active, Inactive, Completed.
- `subtask_id` (string, required): Id of the subtask to update (required). Must be a subtask in your organization.

### `create_time_report` (~211 tokens)

Create a new time entry on a subtask for the current user. The entry is always attributed to you — you cannot create entries on behalf of another user. Supply subtask_id, the date (ISO 8601 YYYY-MM-DD), start_time (HH:mm, defaults to 09:00), and hours.

Input parameters:

- `date` (string, required): Date of the work (ISO 8601 YYYY-MM-DD, e.g. 2026-01-15).
- `hours` (number, required): Hours worked (> 0 and ≤ 24).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `start_time` (string): Optional start time in 24-h HH:mm (defaults to 09:00).
- `subtask_id` (string, required): Id of the subtask to log time against.
- `text` (string): Optional description of the work performed (max 1000 characters).

### `update_time_report` (~169 tokens)

Update fields on one of your own time entries (PATCH — only the fields you supply are changed; everything else is left as-is). Supply the time_report_id plus any combination of date, start_time, hours, and text.

Input parameters:

- `date` (string): New date (ISO 8601 YYYY-MM-DD).
- `hours` (number): New duration in hours (> 0 and ≤ 24).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `start_time` (string): New start time in 24-h HH:mm.
- `text` (string): New description (max 1000 characters).
- `time_report_id` (string, required): Id of the time entry to update.

### `bulk_create_time_reports` (~141 tokens)

Create multiple time entries in one call. Supply an 'entries' array where each item has subtask_id, date (YYYY-MM-DD), and hours (> 0 and ≤ 24); optionally start_time (HH:mm, defaults to 09:00) and text. Entries are always attributed to you. Returns per-item results (partial failures are reported rather than aborting the batch). Max 50 entries.

Input parameters:

- `entries` (array, required): List of time entries to create (max 50).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `bulk_update_time_reports` (~131 tokens)

Apply a common text description update to multiple of your own time entries. Supply ids (list of time-report ids, max 100) and text (the new description). Returns per-id results — partial failures are reported rather than aborting the whole batch.

Input parameters:

- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `ids` (array, required): Ids of the time entries to update (max 100).
- `text` (string, required): New description to apply to all entries (max 1000 characters).

### `copy_period` (~184 tokens)

Copy your own time entries from a source date range into a target date range, preserving each entry's weekday offset relative to the source start (e.g. copy last week to this week). New entries are created as Draft. The source range cannot exceed 31 days. Supply source_start_date, source_end_date, and target_start_date (all ISO 8601 YYYY-MM-DD).

Input parameters:

- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `source_end_date` (string, required): Inclusive end of the range to copy FROM (YYYY-MM-DD).
- `source_start_date` (string, required): Inclusive start of the range to copy FROM (YYYY-MM-DD).
- `target_start_date` (string, required): The first date of the target range (source_start_date maps here, YYYY-MM-DD).

### `start_timer` (~130 tokens)

Start (or replace) your running timer on a subtask. There is at most one running timer per user; starting a new one replaces any existing. Stop it later with stop_timer to create a Draft time entry, or cancel it with cancel_timer to discard it. Supply subtask_id.

Input parameters:

- `description` (string): Optional description of the work being tracked.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `subtask_id` (string, required): Id of the subtask to track time against.

### `stop_timer` (~68 tokens)

Stop your running timer. The elapsed time is computed and a Draft time entry is created automatically. Returns the created time entry. No arguments needed.

Input parameters:

- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `cancel_timer` (~62 tokens)

Cancel (discard) your running timer without creating a time entry. The elapsed time is lost. No arguments needed.

Input parameters:

- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `submit_timesheet` (~119 tokens)

Submit your time entries for a given month for manager approval. Draft and Rejected entries in the month are transitioned to Submitted. A billing-closed month cannot be submitted. Supply year and month (1-12).

Input parameters:

- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `month` (integer, required): Calendar month to submit (1-12).
- `year` (integer, required): Calendar year of the month to submit (e.g. 2026).

### `recall_timesheet` (~123 tokens)

Withdraw your submitted timesheet for a given month back to Draft (un-submit), reopening entries for editing. Only valid while the period is Submitted — after approval ask a manager to reopen it. Supply year and month (1-12).

Input parameters:

- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `month` (integer, required): Calendar month to recall (1-12).
- `year` (integer, required): Calendar year of the month to recall (e.g. 2026).

### `assign_user_to_customer` (~162 tokens)

Assign an organization member to a billing customer so they can see that customer and all its projects. Requires the org_user_id (discover it with get_project_team or get_employee_timesheet) and the customer_id. The organization is fixed by your context — never pass an organization id. You cannot target a user more privileged than yourself (Owner is not targetable by Admin).

Input parameters:

- `customer_id` (string, required): Id of the customer to assign the user to.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `org_user_id` (string, required): Id of the OrganizationUser to assign (not the Firebase user id — use get_project_team to discover it).

### `remove_user_project` (~147 tokens)

Remove an organization member's assignment from a specific project. The user will no longer have direct visibility to that project (they may still see it via a customer assignment). Requires org_user_id and project_id. The organization is fixed by your context — never pass an organization id. You cannot target a user more privileged than yourself.

Input parameters:

- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `org_user_id` (string, required): Id of the OrganizationUser to remove from the project (not the Firebase user id).
- `project_id` (string, required): Id of the project to remove the user from.

### `enable_user` (~103 tokens)

Re-enable a previously disabled organization member so they can log in and use the platform again. Requires the org_user_id. The organization is fixed by your context — never pass an organization id. You cannot target a user more privileged than yourself.

Input parameters:

- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `org_user_id` (string, required): Id of the OrganizationUser to enable.

### `resend_invite` (~99 tokens)

Re-send a pending invitation email to the invitee and reset its status to Pending. Requires the invite_id (discover it via list of pending invites). The organization is fixed by your context — never pass an organization id.

Input parameters:

- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `invite_id` (string, required): Id of the pending invitation to resend.

### `set_budget_thresholds` (~197 tokens)

Set the organization-level budget alert thresholds. budget_warning_threshold_percent is the utilization % at which a project is flagged At-Risk; budget_critical_threshold_percent is the % at which it is flagged Over-Budget. The warning threshold must be strictly less than the critical threshold. Supply one or both — only the fields you provide are changed (PATCH semantics). The organization is fixed by your context — never pass an organization id.

Input parameters:

- `budget_critical_threshold_percent` (integer): Utilization % at which a project is flagged Over-Budget (must be greater than the warning threshold, 2-100).
- `budget_warning_threshold_percent` (integer): Utilization % at which a project is flagged At-Risk (must be less than the critical threshold, 1-99).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `update_user_profile` (~185 tokens)

Update a team member's organization-profile fields: first name, last name, country, timezone, and job title. Only the fields you provide are changed (PATCH semantics). Role changes are not supported here — use the dedicated role-change tool. The organization is fixed by your context — never pass an organization id. You cannot target a user more privileged than yourself.

Input parameters:

- `country` (string): Updated country.
- `first_name` (string): Updated first name.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `job_title` (string): Updated job title.
- `last_name` (string): Updated last name.
- `org_user_id` (string, required): Id of the OrganizationUser to update.
- `timezone` (string): Updated timezone (IANA or Windows id).

### `update_user_preferences` (~242 tokens)

Update your own UI preferences: default time-entry view, sub-views, theme, and time format. Only the fields you provide are changed (PATCH semantics). Applies to your account globally across all organizations. The user is fixed by your context — you can only change your own preferences.

Input parameters:

- `default_day_sub_view` (string): Default sub-view for the day view. One of: timeline, list, stats, table.
- `default_month_sub_view` (string): Default sub-view for the month view. One of: calendar, list, timeline.
- `default_time_entry_view` (string): Default time-entry view. One of: day, week, month.
- `default_week_sub_view` (string): Default sub-view for the week view. One of: calendar, list, timeline.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `theme_preference` (string): UI theme preference. One of: light, dark, system.
- `time_format` (string): Clock format. One of: 12h, 24h.

### `set_user_cost_rate` (~219 tokens)

Set the internal hourly COST rate for one member of your organization (used for profit/margin reporting). The organization is fixed by your context - never pass an organization id. You cannot set your own cost rate. The rate value is never echoed back.

Input parameters:

- `currency` (string): Optional ISO 4217 currency code (e.g. USD, EUR). Defaults to USD.
- `effective_from` (string): Optional date this rate takes effect (YYYY-MM-DD). Defaults to today.
- `effective_to` (string): Optional date this rate stops applying (YYYY-MM-DD). Omit for an open-ended rate.
- `hourly_rate` (number, required): The hourly cost rate, a positive number (required).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `user_id` (string, required): Id (or Firebase UID) of the member whose cost rate is being set (required). Must be a member of your organization; cannot be yourself.

### `bulk_update_cost_rates` (~204 tokens)

Apply an organization-wide adjustment to every member's hourly COST rate, effective from a date. Supply EITHER adjustment_percentage (e.g. 5 to raise all rates by 5%, -3 to cut 3%) OR fixed_amount (set every rate to this exact amount), not both. The organization is fixed by your context - never pass an organization id. Rate values are never echoed back.

Input parameters:

- `adjustment_percentage` (number): Percentage to adjust every rate by (e.g. 5 = +5%, -3 = -3%). Provide this OR fixed_amount, not both.
- `effective_from` (string, required): Date the adjusted rates take effect (YYYY-MM-DD) (required).
- `fixed_amount` (number): Set every rate to this exact amount. Provide this OR adjustment_percentage, not both.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `create_custom_field` (~291 tokens)

Define a new custom field on a billing entity type (project, task, subtask, time report, or customer) for your organization. The organization is fixed by your context - never pass an organization id. type is one of String, Number, Date, DateTime, ListOfValues; ListOfValues requires at least one option. Marking a field mandatory blocks creating that entity type until a value is provided.

Input parameters:

- `entity` (string, required): The entity type this field is defined on (required). One of: billing_projects, billing_tasks, billing_sub_tasks, sub_tasks_time_reports, billing_customers.
- `field_id` (string, required): A unique, stable key for the field (required, max 50 chars), e.g. "po_number".
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `is_mandatory` (boolean): Whether a value is required when creating/updating the entity. Defaults to false.
- `list_of_values` (array): Options for a ListOfValues field (required for that type; at least one non-blank option).
- `title` (string, required): Human-readable label shown in the UI (required).
- `type` (string, required): Field data type (required). One of: String, Number, Date, DateTime, ListOfValues.

### `update_custom_field` (~202 tokens)

Update an existing custom field definition (title, type, options, or mandatory flag) in your organization. The organization is fixed by your context. You cannot change a field's field_id or the entity it applies to. Only the properties you supply are changed.

Input parameters:

- `field_definition_id` (string, required): Id of the custom field definition to update (required). Must belong to your organization.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `is_mandatory` (boolean): Whether a value is required when creating/updating the entity.
- `list_of_values` (array): New options (for a ListOfValues field; at least one non-blank option).
- `title` (string): New human-readable label.
- `type` (string): New field data type. One of: String, Number, Date, DateTime, ListOfValues.

### `set_custom_field_value` (~226 tokens)

Set the value of a custom field on a specific entity (a project, task, subtask, time report, or customer). The custom field must already be defined for that entity type. The organization is fixed by your context. You must have permission to update the target entity.

Input parameters:

- `entity` (string, required): The entity type (required). One of: billing_projects, billing_tasks, billing_sub_tasks, sub_tasks_time_reports, billing_customers.
- `entity_id` (string, required): Id of the specific entity instance to set the value on (required). Must be in your organization.
- `field_id` (string, required): The field_id of the custom field definition (required). Must be defined for this entity type.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `value` (string, required): The value to set, as a string. It is validated/coerced to the field's declared type (Number, Date, DateTime, or one of the list options).

### `set_org_work_schedule` (~335 tokens)

Create or update a named organization-level work schedule (a weekly working-time profile). Provide schedule_id to update an existing one, or omit it to create a new one. weekly_schedule is a JSON object mapping lowercase day names to a working window, e.g. {"monday":{"start":"09:00","end":"18:00"},"saturday":null}. The organization is fixed by your context. On update, only the fields you supply are changed.

Input parameters:

- `default_for_countries` (string): Optional comma-separated ISO-2 country codes this profile is the default for, e.g. "US,CA".
- `first_day_of_week` (integer): First day of the week: 0=Sunday .. 6=Saturday (1=Monday default).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `is_active` (boolean): Whether the profile is active. Defaults to true on create.
- `name` (string): Schedule name (required when creating).
- `notes` (string): Optional free-text notes.
- `schedule_id` (string): Id of an existing schedule to UPDATE. Omit to CREATE a new one.
- `weekly_schedule` (string): A JSON object (as a string) mapping lowercase day names (sunday..saturday) to a {"start":"HH:mm","end":"HH:mm"} window, or null for a non-working day. Example: {"monday":{"start":"09:00","end":"18:00…

### `manage_user_work_schedule` (~200 tokens)

Manage YOUR OWN personal work schedule. action is one of: create, update, delete, assign (assign = make a schedule your active one). For update/delete/assign, provide schedule_id. default_hours is your standard daily hours (for a simple schedule). The organization is fixed by your context, and you can only manage your own schedule.

Input parameters:

- `action` (string, required): What to do (required): create, update, delete, or assign.
- `default_hours` (number): Standard daily working hours for a simple schedule (e.g. 8).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `is_active` (boolean): Whether this schedule is active (create/update).
- `name` (string): Optional schedule notes/name.
- `schedule_id` (string): Id of your schedule (required for update, delete, assign).

### `update_holiday_profile` (~266 tokens)

Update an existing holiday profile in your organization (name, holiday list, default-for-countries, active flag, or notes). The organization is fixed by your context. A profile's year cannot be changed. Only the fields you supply are changed; supplying holidays REPLACES the profile's holiday list. Holiday dates must fall within the profile's year.

Input parameters:

- `default_for_countries` (string): Optional comma-separated ISO-2 country codes this profile is the default for, e.g. "US,CA".
- `holidays` (string): A JSON array (as a string) that REPLACES the profile's holidays, each: {"date":"YYYY-MM-DD","name":"...","full_day_off":true|false,"window_start":"HH:mm","window_end":"HH:mm"}. Dates must be within t…
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `is_active` (boolean): Whether the profile is active.
- `name` (string): New profile name.
- `notes` (string): Optional free-text notes.
- `profile_id` (string, required): Id of the holiday profile to update (required). Must belong to your organization.

### `delete_customer` (~117 tokens)

Soft-delete a billing customer and its whole hierarchy (projects, tasks, subtasks) into the recycle bin, where an admin can restore it. Returns a preview unless confirm=true is set.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `customer_id` (string, required): Id of the customer to delete.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `close_month` (~158 tokens)

Close a billing month so no further time can be logged or edited in it. Call once with no token to preview; re-call with the returned confirm_token and an idempotency_key to commit. Reversible only by reopening the month.

Input parameters:

- `confirm_token` (string): Token returned by the preview (call this tool once with no token to get it). Required to commit; expires in ~10 minutes.
- `idempotency_key` (string): Required when committing (confirm_token present): retrying with the same key returns the original result instead of acting twice.
- `month` (integer, required): Calendar month to close (1-12).
- `year` (integer, required): Calendar year of the month to close (e.g. 2026).

### `delete_project` (~112 tokens)

Soft-delete a billing project and its whole task/subtask hierarchy into the recycle bin, where an admin can restore it. Returns a preview unless confirm=true is set.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `project_id` (string, required): Id of the project to delete.

### `delete_task` (~110 tokens)

Soft-delete a billing task and its subtask hierarchy into the recycle bin, where an admin can restore it. Returns a preview unless confirm=true is set.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `task_id` (string, required): Id of the task to delete.

### `delete_subtask` (~109 tokens)

Soft-delete a billing subtask into the recycle bin, where an admin can restore it. Returns a preview unless confirm=true is set.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `subtask_id` (string, required): Id of the subtask to delete.

### `delete_time_report` (~118 tokens)

Delete a time report entry. Members can delete their own reports; Managers/Admins can delete others' (subject to org settings). Returns a preview unless confirm=true is set.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `time_report_id` (string, required): Id of the time report entry to delete.

### `approve_timesheet` (~144 tokens)

Approve a submitted timesheet period for a team member. The period and its time reports transition to Approved. Use confirm=true to proceed. Requires Manager or Admin/Owner role (Finance is excluded — timesheet approval is PM work, not finance).

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `submission_period_id` (string, required): Id of the submission period to approve (from get_pending_approvals or list_approval_history).

### `reject_timesheet` (~178 tokens)

Reject a submitted timesheet period, returning it to the reporter for correction. The period and its time reports revert to Rejected (editable). A rejection comment is required. Use confirm=true to proceed. Requires Manager or Admin/Owner role (Finance is excluded — timesheet approval is PM work, not finance).

Input parameters:

- `comment` (string, required): Rejection reason shown to the reporter. Required so they know what to fix.
- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `submission_period_id` (string, required): Id of the submission period to reject (from get_pending_approvals or list_approval_history).

### `reopen_timesheet` (~194 tokens)

Reopen a Submitted or Approved timesheet period for corrections. The period and its time reports revert to Rejected (editable), allowing the reporter to edit and resubmit. Use this when an approved period needs fixing. An optional comment can be provided. Use confirm=true to proceed. Requires Manager or Admin/Owner role (Finance is excluded — timesheet approval is PM work, not finance).

Input parameters:

- `comment` (string): Optional comment explaining why the period is being reopened. Shown to the reporter.
- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `submission_period_id` (string, required): Id of the submission period to reopen (from get_pending_approvals or list_approval_history).

### `generate_invoice` (~223 tokens)

Generate a DRAFT invoice from a customer's approved billable hours over a billing period. The draft is editable and can be deleted before it is issued.

Input parameters:

- `customer_id` (string, required): Id of the customer to invoice.
- `due_date` (string): Optional explicit due date (ISO 8601). Overrides payment_terms-based calculation.
- `grouping` (string): How to group approved hours into line items: "project" (default) or "task".
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `notes` (string): Optional notes to include on the invoice.
- `payment_terms` (string): Payment terms string, e.g. "Net 30" (default).
- `period_end` (string, required): Billing period end date (ISO 8601, e.g. 2026-05-31).
- `period_start` (string, required): Billing period start date (ISO 8601, e.g. 2026-05-01).

### `update_draft_invoice` (~189 tokens)

Update editable fields on a DRAFT invoice (notes, internal notes, payment terms, payment instructions, due date, purchase order number). Only valid while the invoice is still a Draft.

Input parameters:

- `due_date` (string): Due date override (ISO 8601).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `internal_notes` (string): Internal notes (not on the printed invoice).
- `invoice_id` (string, required): Id of the draft invoice to update.
- `notes` (string): Notes to appear on the invoice.
- `payment_instructions` (string): Bank / payment instructions for the customer.
- `payment_terms` (string): Payment terms, e.g. "Net 30".
- `purchase_order_number` (string): Customer PO number to reference on the invoice.

### `delete_draft_invoice` (~111 tokens)

Delete a DRAFT invoice permanently. Only draft invoices can be deleted; issued invoices are permanent records. Returns a preview unless confirm=true is set.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `invoice_id` (string, required): Id of the draft invoice to delete.

### `send_invoice` (~111 tokens)

Mark an issued invoice as Sent to the customer. The invoice must already be in Issued status. Returns a preview unless confirm=true is set.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `invoice_id` (string, required): Id of the issued invoice to mark as sent.

### `mark_invoice_paid` (~130 tokens)

Mark an issued or sent invoice as Paid. Optionally record the paid amount and payment date. Returns a preview unless confirm=true is set.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `invoice_id` (string, required): Id of the invoice to mark as paid.
- `paid_date` (string): Optional payment date (ISO 8601). Defaults to today.

### `issue_invoice` (~152 tokens)

Issue a Draft invoice: assigns a gapless invoice number, locks the invoice as immutable, and marks source hours as Invoiced. IRREVERSIBLE — corrections require void + reissue. Call once with no token to preview; re-call with the returned confirm_token and an idempotency_key to commit.

Input parameters:

- `confirm_token` (string): Token returned by the preview (call this tool once with no token to get it). Required to commit; expires in ~10 minutes.
- `idempotency_key` (string): Required when committing (confirm_token present): retrying with the same key returns the original result instead of acting twice.
- `invoice_id` (string, required): Id of the Draft invoice to issue.

### `void_invoice` (~158 tokens)

Void an issued invoice (reason required): releases source hours back to Approved and retains the immutable void record. IRREVERSIBLE. Call once with no token to preview; re-call with the returned confirm_token and an idempotency_key to commit.

Input parameters:

- `confirm_token` (string): Token returned by the preview (call this tool once with no token to get it). Required to commit; expires in ~10 minutes.
- `idempotency_key` (string): Required when committing (confirm_token present): retrying with the same key returns the original result instead of acting twice.
- `invoice_id` (string, required): Id of the issued invoice to void.
- `reason` (string, required): Required reason for voiding (recorded in the audit trail).

### `reissue_invoice` (~167 tokens)

Void an issued invoice and clone it into a new editable Draft (void + reissue). The original is voided and retained for audit; the new Draft can be edited then re-issued. The void is IRREVERSIBLE. Call once with no token to preview; re-call with the returned confirm_token and an idempotency_key to commit.

Input parameters:

- `confirm_token` (string): Token returned by the preview (call this tool once with no token to get it). Required to commit; expires in ~10 minutes.
- `idempotency_key` (string): Required when committing (confirm_token present): retrying with the same key returns the original result instead of acting twice.
- `invoice_id` (string, required): Id of the issued invoice to void and reissue as a new Draft.

### `create_frame_order` (~271 tokens)

Create a new Open frame order (blanket PO / commercial envelope) for a customer. A frame order tracks a contracted hours or amount cap that invoices can draw down against. Reversible — the frame order can be deleted while it is still Open.

Input parameters:

- `currency` (string): ISO 4217 currency code (e.g. USD). Defaults to the customer's currency when omitted.
- `customer_id` (string, required): Id of the customer this frame order belongs to.
- `description` (string): Optional human-readable description (max 500 chars).
- `end_date` (string): Optional end date in YYYY-MM-DD format (must be >= start_date).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `notes` (string): Optional free-text notes (max 2000 chars).
- `reference` (string, required): Unique reference string per (org, customer), e.g. 'PO-2026-001'. Max 100 chars.
- `start_date` (string): Optional start date in YYYY-MM-DD format.
- `total_amount` (number): Optional contracted amount cap (must be > 0).
- `total_hours` (number): Optional contracted hours cap (must be > 0).

### `update_frame_order` (~256 tokens)

Update an Open frame order's editable fields (reference, description, caps, dates, currency, notes). Closed frame orders cannot be edited; use this only for Open frame orders.

Input parameters:

- `currency` (string): Updated ISO 4217 currency code (e.g. USD).
- `description` (string): Updated description (max 500 chars).
- `end_date` (string): Updated end date (YYYY-MM-DD, >= start_date), or omit to clear.
- `frame_order_id` (string, required): Id of the frame order to update.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `notes` (string): Updated free-text notes (max 2000 chars).
- `reference` (string, required): New unique reference string for this (org, customer), max 100 chars.
- `start_date` (string): Updated start date (YYYY-MM-DD), or omit to clear.
- `total_amount` (number): Updated contracted amount cap (must be > 0, or omit/null to clear).
- `total_hours` (number): Updated contracted hours cap (must be > 0, or omit/null to clear).

### `close_frame_order` (~119 tokens)

Close an Open frame order so no new invoices may link to it. Returns a preview unless confirm=true is set. Closing is not directly reversible; the order remains in the Closed state.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `frame_order_id` (string, required): Id of the frame order to close.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `delete_frame_order` (~127 tokens)

Soft-delete an Open frame order into the recycle bin (restorable by an Admin). Blocked when Issued/Sent/Paid invoices are linked — void or unlink those first. Returns a preview unless confirm=true is set.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `frame_order_id` (string, required): Id of the frame order to delete.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `reopen_month` (~160 tokens)

Reopen a previously closed billing month, allowing time to be logged and edited again. Call once with no token to preview; re-call with the returned confirm_token and an idempotency_key to commit. Reversible only by closing the month again.

Input parameters:

- `confirm_token` (string): Token returned by the preview (call this tool once with no token to get it). Required to commit; expires in ~10 minutes.
- `idempotency_key` (string): Required when committing (confirm_token present): retrying with the same key returns the original result instead of acting twice.
- `month` (integer, required): Calendar month to reopen (1-12).
- `year` (integer, required): Calendar year of the month to reopen (e.g. 2026).

### `restore_entity` (~125 tokens)

Restore a soft-deleted entity (customer, project, task, or subtask) and all its children from the recycle bin. Requires Admin role. entity_type must be one of: Customer, Project, Task, SubTask.

Input parameters:

- `entity_id` (string, required): Id of the deleted entity to restore.
- `entity_type` (string, required): Type of entity to restore. One of: Customer, Project, Task, SubTask.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `permanent_delete_entity` (~196 tokens)

Permanently and IRREVERSIBLY hard-delete an entity from the recycle bin. The entity and all its children are removed from the database — this cannot be undone. Requires Admin role. Call once with no token to preview; re-call with the returned confirm_token and an idempotency_key to commit. entity_type must be one of: Customer, Project, Task, SubTask.

Input parameters:

- `confirm_token` (string): Token returned by the preview (call this tool once with no token to get it). Required to commit; expires in ~10 minutes.
- `entity_id` (string, required): Id of the recycle-bin entity to permanently delete.
- `entity_type` (string, required): Type of entity to permanently delete. One of: Customer, Project, Task, SubTask.
- `idempotency_key` (string): Required when committing (confirm_token present): retrying with the same key returns the original result instead of acting twice.

### `change_user_role` (~160 tokens)

Change an organization member's role. Returns a preview; re-call with the confirm_token and an idempotency_key to commit. Cannot assign the Owner role. Cannot escalate beyond your own role.

Input parameters:

- `confirm_token` (string): Token returned by the preview (call this tool once with no token to get it). Required to commit; expires in ~10 minutes.
- `idempotency_key` (string): Required when committing (confirm_token present): retrying with the same key returns the original result instead of acting twice.
- `new_role` (string, required): New role to assign: Admin, Finance, Manager, Member, or Viewer.
- `org_user_id` (string, required): Id of the OrganizationUser record to update (not the Firebase userId).

### `disable_user` (~145 tokens)

Disable an organization member so they can no longer sign in or use the app. Reversible — the user can be re-enabled from the web application. Returns a preview unless confirm=true is set.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `org_user_id` (string, required): Id of the OrganizationUser record to disable (not the Firebase userId).
- `reason` (string): Optional reason for disabling the user (stored for audit purposes).

### `remove_user` (~143 tokens)

Permanently remove an organization member. This action is IRREVERSIBLE — the user must be re-invited to rejoin. Returns a preview; re-call with the confirm_token and an idempotency_key to commit.

Input parameters:

- `confirm_token` (string): Token returned by the preview (call this tool once with no token to get it). Required to commit; expires in ~10 minutes.
- `idempotency_key` (string): Required when committing (confirm_token present): retrying with the same key returns the original result instead of acting twice.
- `org_user_id` (string, required): Id of the OrganizationUser record to remove (not the Firebase userId).

### `cancel_invite` (~116 tokens)

Cancel a pending invitation so the invite link is no longer valid. The email address can be re-invited at any time. Returns a preview unless confirm=true is set.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `invite_id` (string, required): Id of the pending invitation to cancel.

### `delete_api_key` (~137 tokens)

Permanently revoke one of your Integration API keys. Any MCP clients or integrations using the key will lose access immediately and cannot be restored. Returns a preview; re-call with the confirm_token and an idempotency_key to commit.

Input parameters:

- `confirm_token` (string): Token returned by the preview (call this tool once with no token to get it). Required to commit; expires in ~10 minutes.
- `idempotency_key` (string): Required when committing (confirm_token present): retrying with the same key returns the original result instead of acting twice.
- `key_id` (string, required): Id of the API key to permanently revoke.

### `delete_organization` (~131 tokens)

Soft-delete this organization. All members will be locked out and the org will be hidden until a platform admin restores it within the retention window. Call once with no token to preview; re-call with the returned confirm_token and an idempotency_key to commit. Owner role required.

Input parameters:

- `confirm_token` (string): Token returned by the preview (call this tool once with no token to get it). Required to commit; expires in ~10 minutes.
- `idempotency_key` (string): Required when committing (confirm_token present): retrying with the same key returns the original result instead of acting twice.

### `delete_custom_field` (~128 tokens)

Delete a custom-field definition from the organization. If the field is mandatory and already has values stored on entities the service will reject the delete with a clear reason. Returns a preview unless confirm=true is set. Admin role required.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `custom_field_id` (string, required): Id of the custom field definition to delete.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `delete_work_schedule` (~116 tokens)

Delete a named organization work schedule profile. Users assigned to this schedule will fall back to the default schedule. Returns a preview unless confirm=true is set. Admin role required.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `work_schedule_id` (string, required): Id of the work schedule to delete.

### `delete_holiday_profile` (~119 tokens)

Delete a named national-holiday profile from the organization. The year's holidays will no longer be applied to time calculations. Returns a preview unless confirm=true is set. Admin role required.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `holiday_profile_id` (string, required): Id of the holiday profile to delete.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `write_off_time` (~162 tokens)

Write off hours from an approved time report, removing them from the billable pool without invoicing (e.g. discounts or goodwill). Requires Finance role or above.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `hours` (number, required): Number of hours to write off (required, must be > 0 and ≤ remaining billable hours).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `reason` (string, required): Reason for the write-off (required).
- `time_report_id` (string, required): ID of the approved time report to write off hours from (required).

### `undo_write_off` (~128 tokens)

Reverse the most-recent write-off on a time report, restoring the written-off hours to the billable pool. The billing month must still be open. Requires Finance role or above.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `time_report_id` (string, required): ID of the time report whose most-recent write-off should be reversed (required).

### `create_credit_note` (~139 tokens)

Create a credit note against an existing invoice, reducing the amount owed. Requires Finance role or above.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `credit_amount` (number, required): Total credit amount (required, must be > 0 and ≤ invoice total).
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `invoice_id` (string, required): ID of the invoice to credit (required).
- `reason` (string, required): Reason for the credit note (required).

### `move_subtask` (~112 tokens)

Move a subtask to a different task within your organization. Both the subtask and the destination task must belong to your organization. Requires Manager role or above.

Input parameters:

- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `new_task_id` (string, required): ID of the destination task (required, must belong to your organization).
- `subtask_id` (string, required): ID of the subtask to move (required).

### `move_task` (~108 tokens)

Move a task to a different billing project within your organization. Both the task and the destination project must belong to your organization. Requires Manager role or above.

Input parameters:

- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `new_project_id` (string, required): ID of the destination project (required, must belong to your organization).
- `task_id` (string, required): ID of the task to move (required).

### `move_project` (~108 tokens)

Move a billing project to a different customer within your organization. Both the project and the destination customer must belong to your organization. Requires Manager role or above.

Input parameters:

- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `new_customer_id` (string, required): ID of the destination customer (required, must belong to your organization).
- `project_id` (string, required): ID of the project to move (required).

### `mark_time_invoiced` (~137 tokens)

Mark one or more time reports as invoiced, optionally linking them to an existing invoice. Requires Manager role or above.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `invoice_id` (string): Optional ID of an existing invoice to link these time reports to.
- `time_report_ids` (array, required): List of time report IDs to mark as invoiced (required, at least one).

### `list_invoices` (~100 tokens)

List invoices for your organization, optionally filtered by customer and status.

Input parameters:

- `customer_id` (string): Optional: filter by customer ID.
- `page_number` (integer): Page number, 1-based (default 1).
- `page_size` (integer): Number of results per page (default 20, max 100).
- `status` (string): Optional: filter by invoice status (e.g. Draft, Issued, Paid, Void).

### `get_invoice` (~35 tokens)

Get the full details of a specific invoice by ID.

Input parameters:

- `invoice_id` (string, required): ID of the invoice to retrieve (required).

### `list_favorites` (~22 tokens)

List the current user's saved time-entry favorites (quick-entry shortcuts).

### `create_favorite` (~136 tokens)

Save a time-entry combination as a favorite for quick reuse. Returns the created favorite.

Input parameters:

- `customer_id` (string, required): Customer id.
- `description` (string): Default time-entry description (optional).
- `display_name` (string, required): Short label for the favorite (e.g. 'Daily standup on Acme').
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `project_id` (string, required): Project id.
- `sub_task_id` (string, required): Subtask id.
- `task_id` (string, required): Task id.

### `use_favorite` (~76 tokens)

Record that a time-entry favorite was used, incrementing its use count and updating last-used timestamp.

Input parameters:

- `favorite_id` (string, required): Id of the favorite to record usage for.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `delete_favorite` (~93 tokens)

Delete a saved time-entry favorite. Requires confirm=true to proceed.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `favorite_id` (string, required): Id of the favorite to delete.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `get_import_template` (~41 tokens)

Return the CSV template for bulk-importing the work hierarchy (customers, projects, tasks, subtasks). Fill the template and call validate_import before commit_import.

### `validate_import` (~57 tokens)

Validate a bulk-import CSV without persisting anything. Returns row-level errors and a summary so you can fix the file before calling commit_import.

Input parameters:

- `csv_content` (string, required): The CSV content to validate (use the template from get_import_template).

### `commit_import` (~94 tokens)

Commit a bulk-import CSV, creating the work hierarchy (customers, projects, tasks, subtasks) in the organization. Call validate_import first to verify the file.

Input parameters:

- `csv_content` (string, required): The CSV content to import. Must pass validate_import with no errors first.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `list_scheduled_reports` (~19 tokens)

List all scheduled report definitions for the organization.

### `create_scheduled_report` (~140 tokens)

Create a new scheduled report definition. The report will be generated and emailed to recipients on the configured cadence.

Input parameters:

- `cadence` (string, required): Schedule cadence: Daily, Weekly, or Monthly.
- `format` (string): Output format: pdf (default) or csv.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `name` (string, required): Name for this scheduled report (max 150 chars).
- `recipients` (string, required): Comma-separated recipient email addresses.
- `report_type` (string, required): Report type: DailySummary or MonthlyHours.

### `update_scheduled_report` (~156 tokens)

Update an existing scheduled report definition. Only the fields you provide are changed; unspecified fields keep their current values.

Input parameters:

- `cadence` (string): New cadence: Daily, Weekly, or Monthly (optional).
- `format` (string): New format: pdf or csv (optional).
- `id` (string, required): Id of the scheduled report to update.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `is_active` (boolean): Enable (true) or disable (false) the schedule (optional).
- `name` (string): New name (optional).
- `recipients` (string): New comma-separated recipient emails (optional).

### `cancel_scheduled_report` (~95 tokens)

Permanently delete a scheduled report definition. Requires confirm=true to proceed.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `id` (string, required): Id of the scheduled report to delete.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.

### `list_recycle_bin` (~88 tokens)

List soft-deleted entities currently in the recycle bin, optionally filtered by entity type and paged.

Input parameters:

- `entity_type` (string): Filter by type: Customer, Project, Task, or SubTask. Omit for all types.
- `page` (number): 1-based page number (default 1).
- `page_size` (number): Items per page (default 20).

### `remove_user_from_customer` (~127 tokens)

Remove a user's assignment from a customer, revoking their access to the customer's projects and tasks. Requires confirm=true to proceed.

Input parameters:

- `confirm` (boolean): Set true to perform the action. Omit or false returns a preview only — nothing is written.
- `customer_id` (string, required): Id of the customer to remove the user from.
- `idempotency_key` (string): Optional caller-supplied key; retrying with the same key returns the original result instead of acting twice.
- `org_user_id` (string, required): OrganizationUsers.Id of the member to unassign.

### `search` (~77 tokens)

Search the organization's work-structure entities (customers, projects, tasks, subtasks, users) by id or name. Returns a flat, assignment-scoped result list.

Input parameters:

- `limit` (number): Maximum results to return (default 30).
- `query` (string, required): Search text — matches by entity id (prefix) and name (contains).

### `get_frame_order_utilization` (~74 tokens)

Report each frame order's contracted cap vs billed draw-down vs remaining, for both hours and amount, with utilization percentage. Optionally filtered by customer and/or status.

Input parameters:

- `customer_id` (string): Filter by customer id (optional).
- `status` (string): Filter by status: Open or Closed (optional).

### `check_budget_limits` (~65 tokens)

Check whether logging additional hours on a subtask would exceed its budget limits. Returns whether the budget is exceeded and a message.

Input parameters:

- `additional_hours` (number, required): Hours to check against the budget limit.
- `sub_task_id` (string, required): Id of the subtask to check.

### `get_cost_rate_history` (~48 tokens)

Get the cost-rate history for a specific user in the organization. Requires Finance role or higher.

Input parameters:

- `user_id` (string, required): Firebase UID of the user whose cost-rate history to retrieve.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-timix-time-tracking/api-integration-v1-mcp#diagnostics

## Score history

- 2026-08-03: 75
- 2026-08-02: 75
- 2026-08-01: 74
- 2026-07-31: 74
- 2026-07-30: 69
- 2026-07-29: 71
- 2026-07-28: 70
- 2026-07-27: 69
- 2026-07-26: 69

## Links

- Remote endpoint: https://api.timix.ai/api/integration/v1/mcp
- Website: https://timix.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-timix-time-tracking/api-integration-v1-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-timix-time-tracking/api-integration-v1-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-timix-time-tracking/api-integration-v1-mcp