Read employees, time clock, timesheets, time off, schedules and payroll data in WebClock. Hosted by usefulapi: connect it to Claude, ChatGPT, Cursor or any MCP client.
Turn on the WebClock connector, then ask in plain words. The AI picks the tools.
For HR, payroll and operations teams that use WebClock for time clock and timesheet data.
Check the current in or out status of each employee, with the last in and last out times and the time-off flag. Read the employee list with its pay group and department.
Read the timesheet hours by pay code, client and task, with lock and approval status. Compare them with the raw punch times for the same dates.
List shift anomalies such as missing punches for a date range. Read the time-clock records of the same days to check them.
Read the accrual balance of each employee and accrual type. List the time-off requests in a date range, filtered by status or employee.
Read units, rates, pay codes and PTO balance for one pay group over a date range. Add time totals per week or month for the same period.
The login page asks for your WebClock Client ID, WebClock API username and WebClock API password.
Ask WebClock Support for API access with an active WebClock account. Your credentials are used only to call the WebClock API on your behalf and to derive a private account id; they are never shown to anyone.
Team and Enterprise: an Owner adds the connector for the organization first.
No Add custom MCP server option? It depends on your account or workspace settings: see OpenAI's guide.
Run this command, then run /mcp in Claude Code to log in:
Add to Cursor or add this to ~/.cursor/mcp.json:
{
"mcpServers": {
"webclock": {
"url": "https://webclock.usefulapi.io/mcp"
}
}
} Add to VS Code or add this to .vscode/mcp.json:
{
"servers": {
"webclock": {
"type": "http",
"url": "https://webclock.usefulapi.io/mcp"
}
}
} Run these commands. The second one opens the login page:
Windsurf, Cline, Zed and other MCP clients: add this URL as a remote MCP server (Streamable HTTP). The client then opens the login page in your browser.
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 WebClock Client ID, WebClock API username and WebClock API password. 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.
| Plan | Price | Limit |
|---|---|---|
| Free | $0 | 50 tool calls / month |
| Proper user | $9/mo · $90/yr | 10,000 tool calls / month |
| Pro+per user | $39/mo · $390/yr | 100,000 tool calls / month |
Each paid plan covers this WebClock server only. Ask your AI to run webclock_upgrade and choose Pro or Pro+, billed monthly or yearly (it returns a Stripe Checkout link). If you already have Pro, ask to change it to Pro+. The change requires your confirmation, keeps your billing interval and charges the price difference for the rest of the period immediately. Cancel any time with webclock_cancel_subscription: your paid plan continues to the end of the paid period, with no refund for the current period, and asking to resume the same plan with webclock_upgrade before then undoes the cancel. Or write to [email protected].
webclock_list_employeeswebclock_get_time_clockwebclock_get_timesheetswebclock_get_time_off_requestswebclock_get_time_off_requests_adminwebclock_whos_in_outwebclock_get_licensewebclock_get_time_summarywebclock_get_scheduleswebclock_get_anomalieswebclock_get_hr_certificationswebclock_get_accrual_balanceswebclock_get_payroll_datawebclock_list_locationswebclock_list_taskswebclock_list_job_functionswebclock_usage_statuswebclock_request_featurewebclock_upgradewebclock_cancel_subscriptionSee who is in and who is out now. Review timesheets for a pay period. Find shifts with missing punches. Check accrual balances and time-off requests. Prepare payroll-ready data for one pay group. See what you can do for the details.
No. usefulapi is an independent service. It is not affiliated with or endorsed by WebClock. The server calls the WebClock API with your own WebClock 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 WebClock Client ID, WebClock API username and WebClock API password. 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 WebClock Client ID, WebClock API username and WebClock API password. 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 WebClock 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 WebClock.
All 16 WebClock tools are marked read-only.
The Free plan gives 50 tool calls / month. Pro costs $9/mo or $90/yr, with 10,000 tool calls / month. Pro+ costs $39/mo or $390/yr, with 100,000 tool calls / month. Each subscription covers this WebClock server only. Cancel any time: your paid plan then runs to the end of the paid period. Run webclock_usage_status to see how many calls you used.
Ask the AI to run webclock_upgrade and choose Pro or Pro+, billed monthly or yearly: it returns a Stripe Checkout link. If you already have Pro, ask to change it to Pro+. After you confirm, your existing subscription changes in place, keeps its billing interval and charges the price difference for the rest of the period immediately. To cancel, run webclock_cancel_subscription. Your paid plan continues to the end of the paid period.
Tell the AI what you wanted to do. It can send the request with webclock_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.