Read users, clock status, items and reports, and create users or assign items in Timesheets.com. For payroll and operations managers who track hours in Timesheets.com. 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": {
"timesheets-com": {
"url": "https://timesheets-com.usefulapi.io/mcp"
}
}
}Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"timesheets-com": {
"type": "http",
"url": "https://timesheets-com.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 clock status of several users, or of the users one supervisor manages. Then list the running project timers of one user.
timesheets_list_clock_shifts timesheets_list_project_timers
Get the hourly time report for a date range, grouped and summarised or detailed. Choose processed or unprocessed records.
timesheets_get_hourly_report
List the hourly payroll periods, then preview the payroll for a date range and users. The preview does not close a payroll period.
timesheets_list_payroll_periods timesheets_preview_payroll
List the items, then add customers, projects or account codes to a user, and set the default. Existing assignments stay as they are.
Changes data · timesheets_list_items timesheets_assign_user_items
Create a user in the company. Set send_notification_email to true to send the invitation email.
Changes data · timesheets_create_user
The login page asks for your Timesheets.com API key and Timesheets.com authorization token.
A Primary Administrator creates both in Timesheets.com's API settings (API dashboard). The key and token are used only to call the Timesheets.com API on your behalf; they are never shown to anyone. Use the token again when it expires.
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 Timesheets.com API key and Timesheets.com authorization token. 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 Timesheets.com connector, then ask in plain words. The AI picks the tools.
| Tool | Type | What it does |
|---|---|---|
timesheets_list_users | read | List users List users of the company, with UserID, name, email, access level and status. Filter by user ids and status. Timesheets API: GET /users. |
timesheets_get_user_info | read | Get user info Get report details for users: name, pay and tracking settings, supervisor. Empty user_ids returns all users. Timesheets API: GET /report/user/info. |
timesheets_create_user | write | Create a user Create a user in the company. Sends an invitation email only when send_notification_email is true (default false). Timesheets API: POST /user. |
timesheets_assign_user_items | write | Assign items to a user Add customers, projects or account codes to a user. Existing assignments stay. Set defaults with default_id (customer, project) or the default_*_id fields (accountcode). Timesheets API: POST /user/{UserID}/customers|projects|accountcodes. |
timesheets_unassign_user_items | write | Remove items from a user Remove customers, projects or account codes from a user. Only the listed ids are removed. Removing a default resets it to the company default. Timesheets API: DELETE /user/{UserID}/customers|projects|accountcodes. |
timesheets_list_items | read | List items List customers, projects, account codes, vendors or events. Filter by status, text and ids. Timesheets API: GET /items/{kind}. |
timesheets_get_item | read | Get an item Get one customer, project, account code, vendor or event by id. Timesheets API: GET /item/{kind}/{id}. |
timesheets_create_vendor | write | Create a vendor Create a vendor (used on expense records). Timesheets API: POST /item/vendor/0. |
timesheets_update_vendor | write | Update a vendor Change fields of one vendor. Only the given fields change. Timesheets API: PATCH /item/vendor/{id}. |
timesheets_create_event | write | Create an event Create an event (an expense or activity tag). Timesheets API: POST /item/event/0. |
timesheets_update_event | write | Update an event Change the name or description of one event. Timesheets API: PATCH /item/event/{id}. |
timesheets_get_clock_shift | read | Get a user's clock shift Get a user's current clock status: clock-in and break times, location, hours for the shift and for today. Needs admin access to that user. Timesheets API: GET /clock/shift/user/{UserID} (key only). |
timesheets_list_clock_shifts | read | List clock shifts List clock status for several users, or for the users one supervisor manages. Timesheets API: GET /clock/shift/users (key only). |
timesheets_list_project_timers | read | List project timers List a user's running project timers, optionally by customer, project or account code. Timesheets API: GET /project/timers/{UserID}. |
timesheets_get_record_history | read | Get record history Get the revision history of one hourly, project or expense record. Needs admin access to the record's employee. Timesheets API: GET /record/{kind}/history/{RecordID}. |
timesheets_get_hourly_report | read | Get an hourly time report Get an hourly time report for a date range, grouped and summarised or detailed. Processed = approved and finished records; unprocessed = the rest. Timesheets API: POST /report/hourly/customizable/{processed|unprocessed}. |
timesheets_list_payroll_periods | read | List hourly payroll periods List hourly payroll periods that start and end in a date range. Timesheets API: GET /report/hourly/payroll/periods. |
timesheets_get_payroll_period | read | Get one hourly payroll period Get the hourly payroll report of one period, optionally for some users. Timesheets API: GET /report/hourly/payroll/period/{PayrollID}. |
timesheets_preview_payroll | read | Preview an hourly payroll run Preview the hourly payroll for a date range and users. It is a preview: the call does not close a payroll period. Timesheets API: POST /report/hourly/payroll/preview. |
timesheets_get_project_report | read | Get a project time report Get a project time report for a date range, by user, customer, project or account code. Timesheets API: POST /report/project/customizable. |
timesheets_get_expense_report | read | Get an expense report Get an expense report for a date range, by user, vendor, event, customer, project or account code. Timesheets API: POST /report/expense/customizable. |
timesheets_get_server_reference | read | Get server reference data Get the company's enum constants (user statuses, access types, record statuses) or the timezone ids used by timesheets_create_user. Timesheets API: GET /server/constants or /server/timezones. |
timesheets_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. | |
timesheets_request_feature | Request a missing feature Tell usefulapi that the user needs something the Timesheets.com 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. | |
timesheets_upgrade | Upgrade to Pro (unlimited*) Get Pro: unlimited tool calls (fair use limit: 10,000 a month) on Timesheets.com (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. | |
timesheets_cancel_subscription | Cancel the Pro subscription Cancel the caller's Timesheets.com 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 timesheets_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 Timesheets.com server only. Subscribe with timesheets_upgrade (it returns a Stripe Checkout link). Cancel any time with timesheets_cancel_subscription: Pro continues to the end of the paid period, with no refund for the current period, and running timesheets_upgrade before then undoes the cancel. Or write to [email protected].
See who is clocked in today. Build the hourly report for a period. Preview a payroll run before it closes. Assign customers or projects to a user. Invite a new employee. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by Timesheets.com. The server calls the Timesheets.com API with your own Timesheets.com 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 Timesheets.com API key and Timesheets.com authorization token. 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 Timesheets.com API key and Timesheets.com authorization token. 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 Timesheets.com 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 Timesheets.com.
Yes, if you approve it. 7 of the 22 Timesheets.com tools can create or change data. The other 15 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 Timesheets.com server only. Cancel any time: Pro then runs to the end of the paid period. Run timesheets_usage_status to see how many calls you used.
Ask the AI to run timesheets_upgrade: it returns a Stripe Checkout link. To cancel, run timesheets_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 timesheets_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.