Timers Start and Stop on the Project You Name
WebWork starts the timer on the project or task you name, and stops it when you say so. Time entries can be added, edited and deleted the same way, including on work from earlier in the week.
Cursor Time Tracking Integration
Ask the agent in Cursor to start your timer and it starts. Ask how many hours went into a service this sprint and get the reply in the same pane as the code. You can track time in Cursor without opening a dashboard, a browser tab or a second app.
The WebWork MCP server connects your workspace to Cursor with 120 tools — timers, time entries, reports, tasks, timesheets and approvals. Each one runs at your own WebWork permission level, and Cursor asks you to approve every call before it runs.
Integrate Cursor with WebWork
No credit card | Cancel anytime
Track Time Without Leaving the Editor
Time tracking with Cursor runs through the agent you already have open. You describe what you want in the same place you describe a refactor, and the agent calls the WebWork tool that does it.
Reports Come Back as Answers
Tracked hours, task reports, activity levels, activity descriptions and daily timelines are all available by asking. Project budgets and billable hours come back the same way, so you can check where a project sits without building a report first.
Approvals Finish in the Editor
The agent can approve or reject timesheets, clear time requests and handle leave requests, with the reason you give attached to a rejection. An engineering lead can close the week's approvals in the same pane they reviewed the diff in.
What to Ask While You're Working
Ask the agent the following and it resolves the workspace, project and person from the names you use, so there are no IDs to look up.
- hours on the payments service this sprint
- time on the auth refactor vs the estimate
- start my timer on the API rewrite
- log 2 hours on yesterday's migration task
- who's tracking right now
- create a task for the failing integration test and assign it to Karen
- whose timesheets are still unsubmitted
- approve the backend team's timesheets for last week
- comment on the task: ready for review
- how many vacation days do I have left
All WebWork Tools Your Agent Can Use
The WebWork Cursor MCP server publishes 120 tools across 21 areas of the product, grouped below.
| Area | What the AI can do | Example ask |
|---|---|---|
| Timers | Start, stop, check the running timer | “Start my timer on the API rewrite” |
| Time entries | Add, view, edit, delete tracked time | “Log 2 hours on yesterday's migration” |
| Time requests | Request missed time; approve or reject requests | “Approve Davit's missed time request” |
| Timesheets | View, submit, unsubmit, approve, reject | “Approve the backend team's timesheets” |
| Reports | Time, activity, activity descriptions, apps & websites, daily attendance, daily timeline, real-time, GPS, task reports | “Hours on the payments service this sprint” |
| Projects | Create, view, update, archive | “Create a project for the mobile rewrite” |
| Project groups | Group projects; add or remove projects from groups | “Group the platform projects together” |
| Client access | Give outside viewers read access to chosen projects | “Give the client read access to their project” |
| Tasks | Create, assign, update, delete, see assignees | “Assign the failing integration test to Karen” |
| Task comments | Add, edit, delete comments on tasks | “Comment on the task: ready for review” |
| Members | Invite, update, archive, restore | “Invite the new backend hire to the workspace” |
| Teams | Create teams; add and remove members | “Move Davit to the platform team” |
| Job titles | Create titles; assign them to members | “Make Lilit a Senior Engineer” |
| Leave | Request leave, approve or reject, check balances and policies | “How many vacation days do I have left?” |
| Shifts | Create shifts; assign and unassign members | “Put Maria on next week's early shift” |
| Contracts | Create, view, update, delete | “Show me the active contracts” |
| Expenses | Add, edit, delete expenses; browse categories | “Add a $40 tooling expense” |
| Job sites (GPS) | Define and manage locations for on-site tracking | “Add the office as a job site” |
| Custom fields | Create and manage custom data fields | “Add a repo field to projects” |
| Screenshots | List and review captured screenshots | “Show today's screenshots for the QA team” |
| Workspace | List workspaces, workspace info, connection health | “Which workspaces do I have?” |
Every other time tracker with an MCP server gives a coding agent a way to write a time entry. WebWork gives it a way to run the workspace — and no other official time tracking MCP server exposes an approval tool at all.
Built for the Way Developers Already Work
Developer time tracking in Cursor works because the agent already has tools, permissions and an approval step. WebWork uses all these rather than asking you to learn something new.
Nothing Changes Until You Approve It
Cursor asks for approval before it uses an MCP tool. You can expand the call to see exactly what it will send, then let it run. Write access to a workspace is only useful if you can see what it's about to do, and Cursor shows you.
The Numbers Are There While the Agent Is Still Planning
MCP tools work in Plan Mode, not only once the agent is executing. That means hours, estimates and project totals are available at the point you're deciding what to build, rather than after.
Turn It On Only Where You Need It
WebWork can be enabled and disabled from Customize without being removed, so the tools are present on the repositories where hours matter and out of the way everywhere else. Teams already on GitHub or Jira can connect those to WebWork too, so the projects and tasks the agent names are the ones the team already works in.
How to Set Up the Cursor Time Tracking Integration
Cursor supports MCP natively, so there is no plugin to build and nothing to install on your team's machines.
A WebWork Workspace Owner or Executive Manager connects the server once, signs in with their WebWork account and approves the access they want the agent to have. Follow our quickstart guide for the exact steps.
-
Connect the server
Add WebWork's MCP server in Cursor — once
-
Sign in to WebWork
Authenticate with your WebWork account
-
Approve access
Grant only the access the agent needs
Who Can Connect WebWork to Cursor
The WebWork and Cursor integration needs a decision on both sides.
In WebWork: a Workspace Owner or Executive Manager
Only a Workspace Owner or an Executive Manager with a verified email address can connect the server. The tools it publishes are administrative, so other member types cannot make the connection.
In Cursor: your team's admins
Team admins can distribute an approved MCP server to the team, and enterprise admins can restrict which servers a team may run and which tools from an approved server run automatically.
What Your Agent Can and Cannot Do
Two approval steps sit between the agent and your workspace. Cursor asks before it calls a tool, and WebWork checks the call against your role before it answers.
- The connector never exceeds your member type. A tool your role cannot use returns a permission error rather than a result.
- You grant read, write and administrative access during the OAuth sign-in, and you approve tools individually in Cursor.
- Deletions and archiving require an explicit confirmation before anything happens.
- Some actions send real email, including member invitations and leave approvals, and the assistant tells you before it sends them.
- Disconnecting revokes access immediately, from Cursor.
- The connector keeps no separate copy of your workspace data.
Where WebWork Stands Against Every Other Tracker
Most time trackers have no official MCP server. The few that do read and write time entries and stop there. WebWork's covers the whole platform, which is why an agent can finish a workflow instead of editing one entry at a time.
| Time tracker | Server | What it covers |
|---|---|---|
| WebWork | Official | 120 tools across 21 areas — timers, reports, approvals, members, teams, shifts, contracts |
| TrackingTime | Official | Entries, projects, customers. No approvals or workforce management |
| Timely | Official | Narrow scope — time entries, projects, tags |
| Hubstaff | Official | Read-only. Cannot create, modify or delete |
| Clockify | Community only | Unofficial GitHub projects |
| Harvest | Community only | Unofficial GitHub projects |
| Time Doctor | Community | Report export only |
| Toggl Track | None | No official server |
A note on what you'll find in MCP directories: several third-party gateways wrap competitor APIs and offer one-click install into Cursor. Those are resellers of an API, not servers the vendor built, published or supports. The table above lists official vendor servers.
What Developers Say About WebWork
Comprehensive Dashboard, Great ROI
The dashboard is super comprehensive, and the reports are perfect. The UI/UX of the dashboard makes it really easy to use, and you can get a review of the working of the team’s work fast and easily. Overall performance of the application is great, and there are no missed entries. The prices are quite reasonable, and they provide a great return over the investment.
Reliable Tracking and Great Support
Before using WebWork, it was difficult to remember exactly how much time I had spent on different tasks throughout the day. Now I just start the timer, switch between tasks whenever needed, and everything gets recorded automatically. It has made my daily work much more organized. I also use the Timeline Report a lot to review what I worked on during the day, especially when I need to recall a specific task or explain how my time was spent. One thing I really like is the timer UI it shows all the important information in one place, so I don't have to open the WebWork web app every time to check my hours, current task, or other details. It saves me time, and overall it has made time tracking and reporting much easier.
24/7 Global Customer Support
Ranked Top Quality on G2
99.9% Uptime in the Last 90 Days
Advanced Security and Data Privacy
FAQ
It means running your time tracker from the agent in Cursor instead of a dashboard. WebWork's MCP server gives Cursor access to your workspace, so cursor time tracking covers starting timers, logging hours, pulling reports and clearing approvals by describing what you want.
Both. Reading and writing are available at whatever level your WebWork role allows, and a tool your role cannot use returns a permission error rather than a result.
Yes. Cursor asks for approval before it uses an MCP tool, and you can expand the call to see what it will send. Deletions and archiving need a second explicit confirmation on the WebWork side.
No. The connector reaches your WebWork workspace — hours, projects, tasks, timesheets and reports. It publishes no tools that read your repository, your files or your editor contents.
Only a WebWork Workspace Owner or Executive Manager with a verified email address. On the Cursor side, team and enterprise admins decide which MCP servers their team may run.
No. The connector runs on WebWork's side and Cursor supports MCP natively, so nothing installs in the editor or on your team's machines.
The MCP server is included on every plan, starting with Pro at $3.99 per user per month. Shifts, custom fields and expenses need the Plus plan, and a few capabilities need Premium.
Voted Top Time Tracking Software of 2026
Ready to Integrate WebWork with Cursor?
Integrate Cursor with WebWork
No credit card | Cancel anytime
