Bring Time Tracking
to Cursor
Learn how to connect ClockShark to Cursor and start using 10 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
What is the ClockShark MCP Server?
Connect your ClockShark account to any AI agent and take full control of your field service workforce and time-tracking workflows through natural conversation.
What you can do
- Timesheet Orchestration — List and manage individual time tracking entries programmatically, retrieving detailed historical clock-in/out records and location metadata
- Schedule & Shift Intelligence — Create and monitor work shifts and job assignments in real-time to maintain a perfectly coordinated field operation
- Employee Lifecycle Management — Access complete employee profiles and retrieve directories of active or inactive staff to oversee team distribution
- Job & Task Architecture — Programmatically manage your directory of service jobs and project codes to ensure your crew always has the high-fidelity info they need
- Productivity Monitoring — Monitor labor costs and project progress by creating new service tasks and tracking work types directly through your agent
How it works
1. Subscribe to this server
2. Retrieve your API Key from the ClockShark portal (Admin > Integrations > Connect Zapier)
3. Start managing your field workforce from Claude, Cursor, or any MCP client
No more manual following up on missing timesheets or digging through complex scheduling tables. Your AI acts as your dedicated field operations coordinator and labor analyst.
Who is this for?
- Operations Managers — instantly retrieve labor reports and check project timelines using natural language commands
- HR & Payroll Specialists — monitor employee timesheets and verify clock-in accuracy without leaving your workspace
- Construction Supervisors — automate shift scheduling and job site assignments through simple AI queries
Built-in capabilities (10)
Add a new job/project
Schedule a new shift
Add a new work task
Manually add a time entry
Get details for a staff member
List all employees
List all jobs/projects
List employee shifts
List all service tasks
List time tracking entries
Why Cursor?
Cursor's Agent mode turns ClockShark into an in-editor superpower. Ask Cursor to generate code using live data from ClockShark and it fetches, processes, and writes. all in a single agentic loop. 10 tools appear alongside file editing and terminal access, creating a unified development environment grounded in real-time information.
- —
Agent mode turns Cursor into an autonomous coding assistant that can read files, run commands, and call MCP tools without switching context
- —
Cursor's Composer feature can generate entire files using real-time data fetched through MCP. no copy-pasting from external dashboards
- —
MCP tools appear alongside built-in tools like file reading and terminal access, creating a unified agentic environment
- —
VS Code extension compatibility means your existing workflow, keybindings, and extensions all work alongside MCP tools
ClockShark in Cursor
ClockShark and 3,400+ other MCP servers. One platform. One governance layer.
Teams that connect ClockShark to Cursor through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 3,400+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for ClockShark in Cursor
The ClockShark MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 10 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Cursor only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure
How Vinkius secures
ClockShark for Cursor
Every tool call from Cursor to the ClockShark MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I find my ClockShark API Key?
Log in as an Admin, navigate to Admin > Integrations, click on Connect Zapier, and copy your unique API Key.
Can the agent schedule new work shifts?
Yes! The create_shift tool allows the agent to assign a specific employee to a job with start and end times programmatically.
How do I retrieve a list of all jobs?
Use the list_jobs tool to retrieve your complete directory of active and archived projects directly from the platform.
What is Agent mode and why does it matter for MCP?
Agent mode is Cursor's autonomous execution mode where the AI can perform multi-step tasks: reading files, editing code, running terminal commands, and calling MCP tools. Without Agent mode, Cursor operates in a simpler ask-and-answer mode that doesn't support tool calling. Always ensure you're in Agent mode when working with MCP servers.
Where does Cursor store MCP configuration?
Cursor looks for MCP server configurations in a mcp.json file. You can configure servers at the project level (.cursor/mcp.json in your project root) or globally (~/.cursor/mcp.json). Project-level configs take precedence.
Can Cursor use MCP tools in inline edits?
No. MCP tools are only available in Agent mode through the chat panel. Inline completions and Tab suggestions do not trigger MCP tool calls. This is by design. tool calls require user visibility and approval.
How do I verify MCP tools are loaded?
Open Settings → Features → MCP and look for your server name. A green indicator means the server is connected. You can also check Agent mode's available tools by clicking the tools dropdown in the chat panel.
Tools not appearing in Cursor
Ensure you are in Agent mode (not Ask mode). MCP tools only work in Agent mode.
Server shows as disconnected
Check Settings → Features → MCP and verify the server status. Try clicking the refresh button.