Read hours, absences and projects; start timers, add entries, approve leave in TimeTac. For managers and teams that track working time and absences in TimeTac. Hosted by usefulapi — connect from Claude, ChatGPT, Cursor, or any MCP client.
Team and Enterprise: an Owner adds the connector for the organization first.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"timetac": {
"url": "https://timetac.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"timetac": {
"type": "http",
"url": "https://timetac.usefulapi.io/mcp"
}
}
}No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run these commands. The second one opens the login page:
Other MCP clients (Windsurf, Cline, Zed and more): add the URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser. Do not add an Authorization header: see Before you connect.
List the timers that run now, with the person and the task. Add the user list to see the department of each person.
timetac_current_time_trackings timetac_list_users
List the time entries of one user or task for a period. Add the project and task lists to group the hours by project.
timetac_list_time_trackings timetac_list_projects timetac_list_tasks
List the absence requests with dates, duration and approval status. Read the absence types to see which kind of leave each request uses.
timetac_list_absences timetac_list_absence_types
Start or stop a timer for a user. Or add a finished time entry for a task that the person forgot to book.
Changes data · timetac_start_time_tracking timetac_stop_time_tracking timetac_create_time_tracking
Create an absence request for an employee. Approve or reject an open request. TimeTac notifies the employee.
Changes data · timetac_create_absence timetac_approve_absence timetac_reject_absence
The login page asks for your TimeTac account name, Client id and Client secret.
In TimeTac open Account settings → API Credentials (Manager role) and create a client. If you do not see it, ask [email protected] to enable the API. The credentials are used only to call the API for you and to derive a private account id.
Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your TimeTac account name, Client id and Client secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
Turn on the TimeTac connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
timetac_list_users | read | List users List employees (users) of the TimeTac account: id, name, department, active flag, entry/exit dates. Only work-related fields are returned (no credentials, payroll, address or birth data). TimeTac API: GET users/read. |
timetac_get_user | read | Get user Get one employee by user id. Only work-related fields are returned (no credentials, payroll, address or birth data). TimeTac API: GET users/read?id=. |
timetac_list_time_trackings | read | List time trackings List time entries (start, end, duration, task, notes, approval), newest first. Filter by user, task or approval. start_date/end_date filter the returned page only; page with offset. TimeTac API: GET timeTrackings/read. |
timetac_current_time_trackings | read | Running timers List the timers that run right now (who is clocked in, on which task). TimeTac API: GET timeTrackings/current. |
timetac_list_absences | read | List absences List absence and leave requests (holiday, sick leave and others) with dates, duration and approval status. from_date/to_date keep requests that overlap the range, on the returned page only. TimeTac API: GET absences/read. |
timetac_list_absence_types | read | List absence types List the absence types of the account (holiday, sick leave, special leave) with their ids. TimeTac API: GET absenceTypes/read. |
timetac_list_projects | read | List projects List projects (task tree nodes that group tasks) with ids, deadlines and status. TimeTac API: GET projects/read. |
timetac_list_tasks | read | List tasks List tasks that time can be booked on, with their project (mother_id) and status. TimeTac API: GET tasks/read. |
timetac_list_departments | read | List departments List departments with ids and parent departments. TimeTac API: GET departments/read. |
timetac_list_teams | read | List teams List teams with ids and names. TimeTac API: GET teams/read. |
timetac_start_time_tracking | write | Start timer WRITE: start a timer for a user, now or at a given time. Each call can create a new running entry, so do not repeat it. TimeTac API: POST timeTrackings/start. |
timetac_stop_time_tracking | write | Stop timer WRITE: stop the running timer of a user, now or at a given time. TimeTac API: PUT timeTrackings/stop. |
timetac_create_time_tracking | write | Add time entry WRITE: add a finished time entry for a user. Each call creates a new entry, so do not repeat it. TimeTac API: POST timeTrackings/create. |
timetac_create_absence | write | Request absence WRITE: create an absence or leave request for a user. Each call creates a new request, so do not repeat it. type_id is the category (1 holiday, 2 overtime reduction, 3 other paid leave); subtype_id picks the leave type from timetac_list_absence_types. TimeTac API: POST absences/create. |
timetac_approve_absence | write | Approve absence WRITE: approve an open absence request. The employee is notified by TimeTac. TimeTac API: PUT absences/approve. |
timetac_reject_absence | write | Reject absence WRITE: reject an open absence request. The employee is notified by TimeTac. TimeTac API: PUT absences/reject. |
timetac_usage_status | Usage status (free-tier meter) Report the caller's current usage: the plan, calls used this month, the limit of the plan (the free monthly cap or the Pro fair use limit), remaining, and whether the limit is reached. Read-only; does not count against the meter. | |
timetac_request_feature | Request a missing feature Tell usefulapi that the user needs something the TimeTac tools cannot do yet (a missing tool, field or filter). Call it only when the user asks for something none of the tools can do, and tell the user that you send the request. Do not call it for errors or for normal requests. Do not include personal data, credentials or customer records. Stored with the product name and the client type (for example Claude or Cursor), without the user's account. At most 5 requests per day. Does not count against the meter. | |
timetac_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on TimeTac (the free tier caps monthly usage). Plans: "monthly" — $9/month; "yearly" — $90/year (2 months free). Cancel any time: Pro then runs to the end of the paid period, so it also suits a one-time job. *A fair use limit applies. For heavy use (near Pro's limit): "plus" or "plus_yearly" — Pro+, $39/month or $390/year, unlimited tool calls (fair use limit: 100,000 a month); an existing Pro subscription changes to Pro+ in place (needs confirm: true; the price difference for the rest of the period is charged at once). Otherwise returns a short link to open in your browser (it opens Stripe Checkout); after payment the account upgrades automatically. Does not count against the meter. | |
timetac_cancel_subscription | Cancel the Pro subscription Cancel the caller's TimeTac Pro subscription at the end of the paid period (no refund for the current period; Pro continues until then, then the free tier applies). Requires confirm: true. Run timetac_upgrade later to undo the cancel before the period ends. Does not count against the meter. |
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | Unlimited* |
*Pro fair use limit: 10,000 tool calls a month on this server. For more, write to [email protected].
Pro covers this TimeTac server only. Subscribe with timetac_upgrade (it returns a Stripe Checkout link). Cancel any time with timetac_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running timetac_upgrade before then undoes the cancel. Or write to [email protected].
See who is clocked in right now. Report the hours booked last week. Review open absence requests. Start timers and add missing time entries. Request, approve or reject leave. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by TimeTac. The server calls the TimeTac API with your own TimeTac access, so it sees only the data that your account can see.
Yes. In Claude, add this server's URL as a custom connector. In ChatGPT, add it as a custom MCP server in Plugins. Then log in once. Cursor, VS Code, Claude Code and Codex work too. See the setup steps.
The login page asks for your TimeTac account name, Client id and Client secret. See Before you connect for where to find them.
No. Add only the URL. Do not add an Authorization header or an API key to the client config. The server signs you in with OAuth: the login page asks for your TimeTac account name, Client id and Client secret. If the config has such a header, remove it: some clients then send that header instead of the login token, and every call fails with 401.
The login stores them encrypted in the authorization grant of your connection. The server uses them to call the TimeTac API for you and to derive a private account id for usage metering. usefulapi does not show them on any page or in any reply. To stop all access, remove the connector and change or delete these credentials in TimeTac.
Yes, if you approve it. 6 of the 16 TimeTac tools can create or change data. The other 10 are marked read-only. Most MCP clients ask you to approve a tool call before it runs.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with unlimited tool calls (fair use limit: 10,000 tool calls a month), for this TimeTac server only. Cancel any time: Pro then runs to the end of the paid period. Run timetac_usage_status to see how many calls you used.
Ask the AI to run timetac_upgrade: it returns a Stripe Checkout link. To cancel, run timetac_cancel_subscription. Pro continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with timetac_request_feature. We store the text with the server name, the type of AI client and the tool you tried, not with your account, and read every request when we plan new tools. You can send up to 5 requests per day.
Any client that supports remote MCP servers (Streamable HTTP) with OAuth login: Claude (web and desktop), Claude Code, ChatGPT, Codex, Cursor, VS Code, Windsurf and others.
This is a Model Context Protocol endpoint — meant to be connected from an AI client, not opened in a browser. An invalid_token response at the URL is the auth gate working as designed; clients authenticate automatically.
Need a tool this server does not have, or a connection to another system? We build custom integrations and MCP servers.