# Timix.AI Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## Timix.AI

Time tracking, project budgets, and billing for service firms

- Record: https://musedirectory.ai/connector/timix-ai
- Category: Productivity
- Developer: Timix (https://timix.ai)
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 1844ms, checked 2026-09-28T07:46:02Z
- Endpoint: https://api.timix.ai/api/integration/v1/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-09-24T00:25:54Z)
- Source: Found in the official MCP Registry (ai.timix/time-tracking) https://registry.modelcontextprotocol.io/v0/servers?search=ai.timix%2Ftime-tracking

Timix.AI connects to your service firm's time tracking and billing system. Muse can log time entries, check project budgets and utilization, retrieve billing reports, manage customers and projects, and submit timesheets for approval.

Example request: "Log 3 hours of work on the website redesign project for today and check if we're still on budget."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use Timix.AI to help me. It is a free service with an MCP server at https://api.timix.ai/api/integration/v1/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- get_hours_summary: Get a summary of hours logged for a user or team over a date range
- get_dashboard_metrics: Get organization dashboard metrics including utilization, revenue, and active projects
- get_customer_info: Get detailed information about a customer including health score and portfolio
- get_project_status: Get detailed project status including budget, hours, and task breakdown
- get_billing_report: Get billing summary for a customer over a date range
- get_budget_alerts: Get all budget alerts for the organization showing projects that are over or near budget
- list_customers: List all customers in the organization
- list_projects: List all projects in the organization with their status and budget information
- get_my_time_entries: 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
- get_resource_utilization: Get team resource utilization summary showing target hours, actual hours, billable hours, and utilization percentage for the organization
- get_unbilled_time: Get a summary of unbilled time across the organization, including total hours, total amount, number of entries, and aging information
- get_budget_health: 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: 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.
- list_my_time_entries: 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.
- find_billing_work: 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.
- get_project_team: 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', espec
- log_time: Create a single time entry on a subtask for the current user. Requires permission to log time.
- suggest_holiday_profile: 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 worki
- create_holiday_profile: 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 co
- create_customer: Create a new billing customer in your organization. The organization is fixed by your context - never pass an organization id.
- create_project: 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.
- create_task: 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.
- create_subtask: 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.
- invite_user: 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 recei
- assign_user_to_project: 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 contex
- update_org_settings: 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 organiz
- update_customer: 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.
- update_project: 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 i
- update_task: 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.
- update_subtask: 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 
- create_time_report: 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.
- update_time_report: 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.
- bulk_create_time_reports: 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 fail
- bulk_update_time_reports: 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.
- copy_period: 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
- start_timer: 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.
- stop_timer: 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.
- cancel_timer: Cancel (discard) your running timer without creating a time entry. The elapsed time is lost. No arguments needed.
- submit_timesheet: 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).
- recall_timesheet: 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).

Screening checks:
- MCP handshake: pass (Answered in 2330ms)
- Domain against threat feeds (Cloudflare security DNS): pass (api.timix.ai, timix.ai not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (114 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (Domain registered 101 days ago)
- AI review of purpose and tool behavior: pass (No concerns)