ClockShark MCP Server
आपके ClockShark खाते में टाइमशीट, शेड्यूल और जॉब।
होस्ट किया गया MCP सर्वर
npx add-mcp 'https://cotlet.dev/mcp/v1/clockshark'Claude Code, Codex, Cursor और अन्य में इंस्टॉल होता है
दस्तावेज़
Cotlet · Integrations · How it works · Security · For developers · For automation agencies · Blog · API docs · Help center · Changelog · Contact · Pricing · Sign up
ClockShark API and MCP server: Let your AI agent clean up ClockShark timesheets.
ClockShark has no public API, no webhooks and no MCP server. The one key an admin can make is a Zapier key, under Admin > Integrations > Connect Zapier (checked 27 Oct 2026). Cotlet runs 15 ClockShark tools hosted, over MCP for agents and REST for scripts, in your own ClockShark login.
Timesheets, schedules and jobs in your ClockShark account. Use it in ChatGPT, Claude or any AI agent over MCP, or in n8n, Make and scripts over REST.
- Free 7-day trial, no card
- Unofficial, not affiliated with ClockShark
- Page: https://cotlet.dev/integrations/clockshark-api-mcp-server
What can you automate in ClockShark?
- Close missed clock outs from the schedule
- Approve timesheets that have no alerts
- Draft a crew on a new job
- Answer time off against the schedule
- Pull payroll hours for the pay period
- See who is clocked in, and where
Does ClockShark have an MCP server or an API?
- Zapier has 6 triggers (clock in, clock out, new job, new notification, new schedule, new task) and 2 actions: Create Job and Create Task. Zapier MCP offers the same 2 and spends 2 Zapier tasks per call.
- Nothing official approves a timesheet, edits a shift, publishes a schedule or answers time off.
- ClockShark Lightning, its own AI since 1 Sep 2026, writes a shift brief for crews in the app. ClockShark says it "doesn't change a schedule, a job, or a record", and no outside agent can call it.
| What you need | Zapier and Zapier MCP | Payroll integrations | Cotlet |
|---|---|---|---|
| Create a job | Yes, Create Job | No | Yes |
| Read time for any date range | New clock ins and outs only | Pushes hours out | Yes, alerts included |
| Fix a shift, approve a timesheet | No | No | Yes |
| Draft and publish shifts | Fires on a new schedule | No | Yes, publish after your OK |
| Approve or decline time off | No | No | Yes, on Pro, after your OK |
| Price on top of ClockShark | Zapier tasks | Included | Pay per call |
Checked 27 Oct 2026. Sources: ClockShark help: How to use the Zapier integration, Zapier: ClockShark triggers and actions, Zapier MCP for ClockShark, ClockShark Lightning
How does Cotlet connect to ClockShark?
- Sign in to ClockShark. Use your own account in its Cotlet Cloud Browser.
- Choose MCP or REST. Connect your agent or create a Cotlet API key.
- Run your workflow. Ask your agent or send an HTTP request.
We never keep your ClockShark password, and no published shift, time off answer or job comment goes out until you approve it.
Connect ClockShark to your agent or workflow
Use MCP with your AI agent, or HTTP requests in n8n, Make, Zapier and scripts. Follow the MCP setup below or jump to the REST guide.
- Open ClockShark in a Cloud Browser. Make a Cotlet account, open ClockShark in its Cloud Browser, log in with your admin or manager account and press Enable for agents.
- Add the Cotlet address. Paste https://cotlet.dev/mcp/v1 where your agent takes an MCP server or connector URL.
- Approve the connection. Chat apps send you to a Cotlet sign-in page. Code editors, n8n and scripts send an API key from the console.
One address, https://cotlet.dev/mcp/v1, serves ClockShark and every other app you enable. If you enable ClockShark after connecting, refresh the connector so its 15 tools appear.
Claude:
Settings > Connectors > Add custom connector
URL: https://cotlet.dev/mcp/v1/connect
Claude Code:
claude mcp add --transport http cotlet-clockshark \
https://cotlet.dev/mcp/v1 \
--header "Authorization: Bearer $COTLET_API_KEY"
ChatGPT:
Settings > Apps & Connectors > Create
MCP server URL: https://cotlet.dev/mcp/v1/connect
Authentication: OAuth
Cursor:
// ~/.cursor/mcp.json
{
"mcpServers": {
"cotlet-clockshark": {
"url": "https://cotlet.dev/mcp/v1",
"headers": { "Authorization": "Bearer ${env:COTLET_API_KEY}" }
}
}
}
Codex:
# ~/.codex/config.toml
[mcp_servers.cotlet-clockshark]
url = "https://cotlet.dev/mcp/v1"
bearer_token_env_var = "COTLET_API_KEY"
n8n:
MCP Client Tool (inside an AI Agent)
Transport: HTTP Streamable
URL: https://cotlet.dev/mcp/v1
Auth: Bearer, <your key>
Tool: clockshark_read
Make, Zapier:
Make: MCP Client > Call a tool
Zapier: MCP Client by Zapier > Run Tool
Server URL: https://cotlet.dev/mcp/v1
Token: <your key>
Tool: clockshark_write
How to use the ClockShark REST API
Create your Cotlet API key
Create a Cotlet API key with access to ClockShark and its read operations. Store it as COTLET_API_KEY in your environment or automation platform's credential store.
Connect ClockShark in Cotlet and enable it for agents. Account access: Your ClockShark admin or manager account.
Make your first ClockShark API request
REST:
curl https://cotlet.dev/api/v1/clockshark/jobs \
-H "Authorization: Bearer $COTLET_API_KEY"
Read jobs and apply the operation limits
A successful REST call puts the tool output in result. This illustrative response excerpt omits call IDs, messages and credit details.
Illustrative response excerpt:
{
"status": "success",
"app": "clockshark",
"tool": "list_jobs",
"result": {
"jobs": [
{
"job_id": "j_3307",
"number": "2041",
"name": "42 Oak Street",
"stage": "Active",
"customer": "Harlow Homes",
"address": "42 Oak Street, Springfield"
}
]
}
}
Returns jobs your account can see. By default only active jobs are listed.
Use job_id from here in time, schedule and comment tools.
Keep the same selection when continuing a list. Compare changed record values as well as identifiers when refreshing your destination.
ClockShark workflows for agents and automations
| Tool | Connect through | Example workflow |
|---|---|---|
| n8n | HTTP Request | Shifts from Time > View: employee, job, task, start, end, breaks, notes, alerts and approval status. Use list_time_entries in your configured business report. |
| Make | HTTP > Make a request | Scheduled shifts, published and draft, with employee, job, task, times and notes. Use list_shifts in your configured business report. |
| Python or Node.js | REST API | The CSV Export report: paid, regular, overtime and double time minutes per shift, as a download link. Use export_time_csv in your configured business report. |
Send Authorization: Bearer <your Cotlet API key> in request headers. You configure the schedule, destination and record comparisons.
Cotlet reads ClockShark; your workflow steps write to your chosen destination. These HTTP workflows do not require a native Cotlet connector or a prebuilt template.
Python and Node.js can use the same HTTP requests without an AI agent. Keep access keys in credentials, outside shared workflow exports.
The API and MCP reference lists operations and inputs. The REST API guide explains authentication, errors and approvals.
ClockShark API endpoints and MCP tools
Time and timesheets
Edits work on unapproved days only: an approved day is unapproved, changed and approved again. ClockShark's Audit Log keeps the old and new value of every edit.
- List time entries (
list_time_entries, read): Shifts from Time > View: employee, job, task, start, end, breaks, notes, alerts and approval status. - List who's clocked in (
list_clocked_in, read): Employees on an active shift now, with job, task and the GPS location of their last punch. - Add time entry (
add_time_entry, write): Manually add a shift to an employee timesheet, the way a manager does on the web. - Edit time entry (
edit_time_entry, write): Change start, end, job, task or notes of an unapproved shift. Saved to the audit log. - Approve timesheets (
approve_timesheets, write): Approve, or unapprove, employee timesheets for a day, week or pay period. Needs timesheet approvals turned on. - Export time CSV (
export_time_csv, read): The CSV Export report: paid, regular, overtime and double time minutes per shift, as a download link.
Schedule
New shifts are drafts the crew cannot see until publish_shifts. If your schedule syncs from Simpro, Simpro owns it and shifts made here do not reach Simpro.
- List shifts (
list_shifts, read): Scheduled shifts, published and draft, with employee, job, task, times and notes. - Create shift (
create_shift, write): Schedule one or more employees on a job, saved as a draft until you publish it. - Publish shifts (
publish_shifts, write, asks first): Publish draft shifts so they appear in employees' mobile app.
Jobs
A job's description shows to the crew in the mobile app. A comment notifies everyone it @mentions.
- List jobs (
list_jobs, read): Jobs from Work > Jobs with number, stage, customer and address. - Get job (
get_job, read): Job details: description, address, customer, stage, labor budget, comments and attachment list. - Create job (
create_job, write): New job employees can clock into, with customer, address and description. - Add job comment (
add_job_comment, write, asks first): Comment on a job thread; @mentioned users get a notification.
Time off
Pro plan only. ClockShark emails the employee either way, and a decline cannot be taken back.
- List time off requests (
list_time_off_requests, read): Requests from Time > Requests with employee, policy, dates, hours and status. Pro plan. - Respond to time off request (
respond_time_off_request, write, asks first): Approve or decline a request. ClockShark emails the employee; a decline cannot be undone.
Inputs, REST path and example response of every tool: https://cotlet.dev/integrations/clockshark-api-mcp-server#tools
Who can see my ClockShark session, and how do I revoke it?
- What we store. Your logged-in ClockShark profile, AES-256-GCM encrypted, in Finland. No password.
- What your agent gets. The 15 ClockShark tools, never the session cookie.
- What the session sees. What your login sees: crews, GPS punches, jobs, hours, time off.
- What no tool touches. Payroll exports to partners, pay rates, billing, company settings, deletes.
- If ClockShark logs you out. You log in again yourself, in the same Cloud Browser.
- How to cut access. Disable for agents, reset the browser, or change your ClockShark password.
A manager login sees only the employees and permissions ClockShark gives it, so the agent does too: a manager without Approve Timesheets cannot approve through Cotlet either. Our site scores A+ on Qualys SSL Labs, securityheaders.com and Mozilla Observatory (live results). There is no SOC 2 report or third-party pentest yet.
Is it against ClockShark's terms? Account safety
If a user has concurrent sessions running, across multiple IP addresses, devices or browsers, the user may be logged out on one, or all sessions.
ClockShark's Terms, EULA and Fair Use Policy have no clause on robots, scraping or bots. They ban misuse, reverse engineering and "excessive automated content outside intended workflows", and they make you "responsible for all access to and use of the services by any third party you authorize". Each paid user belongs to one person, so the agent works in your own login, and ClockShark may log out your phone or desk session while the Cloud Browser is in. A fixable breach gets 10 business days' written notice before a suspension. We found no public case of a ClockShark account closed for automation (checked 27 Oct 2026).
How we keep ClockShark seeing one manager:
- Your own ClockShark login, entered by you
- One Cloud Browser with a steady IP and cookies
- Publishing shifts, time off answers and job comments wait for your OK (3 tools)
- No tool deletes a shift, job, time entry or employee
- If ClockShark objects, we pause the ClockShark tools for everyone within 24 h
ClockShark's quota policy flags use "automated at high volume". The jobs on this page make a few calls per run, read before they write and do not loop over every employee one by one.
What happens when ClockShark changes?
- 12 h between tests of the ClockShark time and schedule reads
- 24 h between tests of writes a crew member would notice
- $0 for a call to a ClockShark tool paused for repair
ClockShark ships often: a new alert type in May, Simpro schedule sync in July, Lightning in September 2026. When a screen like Time > Approvals moves, we fix the tool and your agent calls it the same way. status.cotlet.dev checks the site, console and API every 3 minutes.
Approvals, undo and mistakes
- Finds Missing Out shifts. Yesterday only, night shifts still running left alone.
- Takes the end from the schedule. No scheduled shift, no guess: it asks you.
- Edits, with a note. The Audit Log says what changed and why.
- Keeps other alerts. Out of Bounds or tampering stay for you to read.
| Action | Undo |
|---|---|
| Add or edit a time entry | Yes, edit again; the Audit Log keeps both values |
| Approve timesheets | Yes, action unapprove |
| Create a shift | Stays a draft nobody sees until published |
| Publish shifts | Unpublish in ClockShark; the crew may have seen it |
| Approve time off | Can still become a decline; the email already went |
| Decline time off or comment on a job | No |
3 of 15 tools ask first: publish_shifts, respond_time_off_request and add_job_comment. Time edits, approvals, new jobs and draft shifts reach nobody and can be reversed, so they run at once. You can switch the wait off per tool, for example for a weekly publish you already checked.
A decline is final in ClockShark, so the agent never declines on its own: it drafts the note and waits.
MCP call:
{
"name": "approve_timesheets",
"arguments": {
"employee_ids": [
"e_48213",
"e_48219"
],
"from": "2026-10-05",
"to": "2026-10-11",
"action": "approve"
}
}
REST:
curl -X POST https://cotlet.dev/api/v1/clockshark/timesheets/approve \
-H "Authorization: Bearer $COTLET_API_KEY" \
-H "Content-Type: application/json" \
-d '{"employee_ids":["e_48213","e_48219"],"from":"2026-10-05","to":"2026-10-11","action":"approve"}'
Response:
{
"approved": 2,
"period": {
"from": "2026-10-05",
"to": "2026-10-11"
},
"timesheets": [
{
"employee_id": "e_48213",
"paid_hours": 41.5,
"overtime_hours": 1.5,
"status": "approved"
},
{
"employee_id": "e_48219",
"paid_hours": 38,
"overtime_hours": 0,
"status": "approved"
}
]
}
A cron job or n8n flow can call the same tools over REST at /api/v1/clockshark with the same key and price, for example a Monday 7 am approval of last week. An approval that ClockShark refuses because approvals are off fails, and failed calls are free. Each tool row above shows its REST path.
How much does the ClockShark MCP server cost?
About $19 a month for a 12-person contractor, 3,240 credits. Your ClockShark plan and contract stay as they are.
| Job | Calls | Credits |
|---|---|---|
| Missed clock outs, each workday | 3 × 22 | 660 |
| Who is clocked in, twice a workday | 1 × 44 | 440 |
| Approve the week and pull the CSV | 3 × 4 | 120 |
| New job with a crew of 2 for 3 days | 8 × 4 | 320 |
| Time off requests, weekly | 5 × 4 | 200 |
| Cloud Browser, 30 days | 1,500 | |
| Total | 3,240 |
- Free 7-day trial, no card
- 10 credits per successful call, MCP or REST
- 50 credits a day for the Cloud Browser
- Works on Standard and Pro; time off needs Pro
ClockShark counts 9,500+ companies and 100,000+ field pros, about 10 people each, so the month uses 12; the job counts are our example. For scale, ClockShark Standard for 12 users is $156 a month ($42 plus $9.50 a user) on a three-year term, per its pricing page. Dollars at the $29 pack rate.
ClockShark MCP server on GitHub, Zapier or hosted: which to use
| Option | What it does | Where it stops |
|---|---|---|
| Zapier MCP for ClockShark | Create Job and Create Task as MCP tools. | No reads, edits, approvals, shifts or time off; 2 Zapier tasks per call. |
| Vinkius ClockShark connector | Hosted MCP listing 10 tools, from list_timesheets to create_shift, on your Zapier key. | No approvals, edits, publishing or time off. The Zapier key has no public endpoints, so we could not confirm the reads work. |
| webstermath/ClockShark-Data-Extractor | Google Apps Script that reads ClockShark CSV exports, 1 star. | Files you export by hand; last push 10 Aug 2019. |
We found no ClockShark MCP server or CLI on GitHub, and viaSocket's ClockShark MCP page lists no actions. If Simpro already runs your jobs and schedule, Simpro's own tools are the place to automate. For the daily office work inside ClockShark, from missed clock outs to time off, Cotlet works in the account your crew already clocks into.
Who runs Cotlet
Take Group sp. z o.o. runs Cotlet. It is a software company registered in Poland, EU (VAT PL6342984273), in business since 2019, led by its founders Bart Krawczyk (Co-founder, CTO) and Jake Slugocki (Co-founder, SEO, sales and marketing). Questions about the ClockShark tools go to contact@cotlet.dev.
ClockShark API and MCP: questions
How do I get access?
Sign up free at https://cotlet.dev, open ClockShark under Integrations in the console and log in to ClockShark in its Cloud Browser. The trial starts when you sign up and asks for no card.
How do I connect ClockShark to ChatGPT or Claude?
Sign up at cotlet.dev, log in to ClockShark once in its Cloud Browser and add Cotlet to ChatGPT or Claude, following the steps in your console. No API key is needed. ChatGPT and Claude then work in your ClockShark account through Cotlet, in their phone apps too.
What can ChatGPT do in ClockShark?
With Cotlet, ChatGPT, Claude and other AI agents handle jobs like these in ClockShark: approve weekly timesheets before payroll; fix missed clock outs; export payroll hours. You ask in plain words, and anything that reaches other people waits for your OK first.
Do I need Zapier or a special ClockShark plan?
No. Cotlet works in your own ClockShark admin or manager account and does not use the Zapier API key. Time off requests are a Pro plan feature in ClockShark, and approving timesheets needs timesheet approvals turned on.
Can it change a timesheet that is already approved?
Not directly. edit_time_entry works on unapproved shifts, so your agent first calls approve_timesheets with action unapprove for that range, edits the shift, then approves again.
Will it log me out of ClockShark on my phone?
It can. ClockShark's Fair Use Policy lets it end one or all sessions of a user who is logged in from several IP addresses at once. If the Cloud Browser session is the one that drops, you log in again there; no tool runs until you do.
Does it work if Simpro sends my schedule?
Time, approvals and time off work as usual. Schedules synced from Simpro belong to Simpro, so the agent reads them but does not create or publish shifts there.
Can it start when someone clocks in?
Cotlet has no ClockShark trigger. Run your agent on a schedule, or let a Zapier trigger such as New Clock In or New Schedule start it.
Is the MCP server different from the REST API?
Only in how it is called. Both carry the same 15 tools, inputs, answers, API key and price. Agents use MCP; scripts and HTTP steps use REST.
Is Cotlet affiliated with ClockShark?
No. Cotlet is independent and not affiliated with ClockShark, LLC or the Simpro Group.
Can I use the ClockShark API without an AI agent?
Yes. Call Cotlet's REST API from a script or an HTTP step in n8n, Make or Zapier with your Cotlet key. MCP is the alternative for AI agents; you do not need to connect an agent to use REST.
Give your AI agents your signed-in browser.
Product: Integrations · How it works · Pricing · Security
Resources: Blog · API docs · Help center · Changelog · GitHub
Solutions: For developers · For automation agencies
Company: About · AI info: company facts · Contact
Legal: Terms of service · Privacy policy · Refund policy · Acceptable use · Cookie policy · DPA · Subprocessors
Elsewhere: Status page · Cotlet on GitHub · Cotlet on X · Cotlet on LinkedIn · Cotlet on Product Hunt · Cotlet on Crunchbase · Cotlet on SaaSHub
Cotlet.dev is built by Bart Krawczyk and Jake Slugocki, the founders of Take Group sp. z o.o., ul. Wincentego Janasa 4, 40-855 Katowice, Poland. KRS 0000871398, NIP 6342984273, VAT EU: PL6342984273. About us
Cotlet is an independent service. It is not affiliated with, endorsed by or sponsored by any of the products listed on this site. Product names are trademarks of their respective owners.