log_time — Timix.AI MCP Tool
log_time
(log time) is one of 114 tools on the
Timix.AI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call log_time from your client
- Claude Code Timix.AI log_time run in your project directory
- Claude Desktop Timix.AI log_time ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Timix.AI log_time ~/.cursor/mcp.json
- VS Code Timix.AI log_time .vscode/mcp.json
- Zed Timix.AI log_time ~/.config/zed/settings.json
- Windsurf Timix.AI log_time ~/.codeium/windsurf/mcp_config.json
- Cline Timix.AI log_time ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Timix.AI log_time ~/.gemini/settings.json
- Grok Timix.AI log_time .mcp.json (in your project root)
- ChatGPT Timix.AI log_time Settings → Connectors → Advanced → Developer mode
- Claude.ai Timix.AI log_time Settings → Connectors → Add custom connector
- LangChain Timix.AI log_time pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http time-tracking https://api.timix.ai/api/integration/v1/mcpOther tools on this server
- get_hours_summary
- get_dashboard_metrics
- get_customer_info
- get_project_status
- get_billing_report
- get_budget_alerts
- list_customers
- list_projects
- get_my_time_entries
- get_resource_utilization
- get_unbilled_time
- get_budget_health
- get_employee_timesheet
- list_my_time_entries
- find_billing_work
- get_project_team
- suggest_holiday_profile
- create_holiday_profile
- create_customer
- create_project
- create_task
- create_subtask
- invite_user
- assign_user_to_project
- update_org_settings
- update_customer
- update_project
- update_task
- update_subtask
- create_time_report
- update_time_report
- bulk_create_time_reports
- bulk_update_time_reports
- copy_period
- start_timer
- stop_timer
- cancel_timer
- submit_timesheet
- recall_timesheet
- assign_user_to_customer
- remove_user_project
- enable_user
- resend_invite
- set_budget_thresholds
- update_user_profile
- update_user_preferences
- set_user_cost_rate
- bulk_update_cost_rates
- create_custom_field
- update_custom_field
- set_custom_field_value
- set_org_work_schedule
- manage_user_work_schedule
- update_holiday_profile
- delete_customer
- close_month
- delete_project
- delete_task
- delete_subtask
- delete_time_report
- approve_timesheet
- reject_timesheet
- reopen_timesheet
- generate_invoice
- update_draft_invoice
- delete_draft_invoice
- send_invoice
- mark_invoice_paid
- issue_invoice
- void_invoice
- reissue_invoice
- create_frame_order
- update_frame_order
- close_frame_order
- delete_frame_order
- reopen_month
- restore_entity
- permanent_delete_entity
- change_user_role
- disable_user
- remove_user
- cancel_invite
- delete_api_key
- delete_organization
- delete_custom_field
- delete_work_schedule
- delete_holiday_profile
- write_off_time
- undo_write_off
- create_credit_note
- move_subtask
- move_task
- move_project
- mark_time_invoiced
- list_invoices
- get_invoice
- list_favorites
- create_favorite
- use_favorite
- delete_favorite
- get_import_template
- validate_import
- commit_import
- list_scheduled_reports
- create_scheduled_report
- update_scheduled_report
- cancel_scheduled_report
- list_recycle_bin
- remove_user_from_customer
- search
- get_frame_order_utilization
- check_budget_limits
- get_cost_rate_history
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.