Full read-write Claude connector for Deputy

Have Claude build shifts and approve timesheets in Deputy

Stop tabbing between Deputy and a spreadsheet to fill rosters and chase hours. Claude drafts and publishes shifts, fills open slots from availability, and approves timesheets right where the roster lives, with pay-affecting steps gated behind your confirmation.

Build my connector Talk to us

Deputy is a workforce management platform for employee scheduling, time and attendance, and timesheet approval across shift-based teams. Managers want Claude to do more than read a roster: to build shifts, approve timesheets, and update availability inside Deputy itself.

What is a Deputy MCP server?

A Deputy MCP server is a small hosted service that exposes Deputy's data and actions to Claude over the Model Context Protocol, so Claude can people, time, and pay inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.

What can Deputy's current connector do today?

Today, Deputy's Claude connection is read-leaning where it exists at all: Claude can typically surface rosters, shifts, and timesheet details, but creating shifts, publishing schedules, and approving timesheets are limited or unavailable. A custom Deputy connector adds those write actions with scoped, human-in-the-loop controls, so Claude works inside the system of record.

What does full read-write Deputy access unlock?

Full read-write Deputy access lets Claude draft and publish shifts, fill open slots from availability, approve or adjust timesheets, manage leave requests, and update employee records once you confirm. The scheduling and timesheet work that used to mean tabbing between Deputy and a spreadsheet happens where the roster already lives.

Draft and publish shifts for a location from a roster template you specify
Fill open shifts by matching available, qualified employees and propose assignments
Approve or adjust submitted timesheets after you review the hours
Approve or decline a leave request and update the schedule accordingly
Add or update employee records, roles, and pay-rate fields
Find every unfilled shift in a date range and propose batched coverage

Can Claude build and publish shifts in Deputy?

Yes. Claude can build shifts in Deputy from a roster template, location, and availability rules, then publish the schedule once you approve. Most default connections only read the roster, so a custom connector adds scoped shift-creation write tools tied to your own Deputy permissions, with publishing gated behind your confirmation.

Can Claude approve timesheets in Deputy?

Claude can review submitted timesheets in Deputy and approve or adjust the hours after you check them. Because approved hours can flow into pay, approval is a separate, gated write action: Claude prepares the change and shows you exactly what it will do, and nothing commits until you confirm it.

Can Claude fill open shifts and manage leave in Deputy?

Yes. Claude can find unfilled shifts across a date range, match available and qualified employees, and propose assignments for you to confirm. It can also approve or decline leave requests and update the schedule accordingly, always working within the locations and teams your own Deputy account already manages.

How a Deputy connector works

We build a small MCP server that connects to Deputy through OAuth or a scoped API token using the narrowest permissions the work needs. Read tools (look up rosters, shifts, timesheets) and write tools (create shift, publish schedule, approve timesheet) are kept separate, and outbound or sensitive actions like publishing a roster or approving pay-affecting timesheets require your confirmation. Claude only ever has the access your own Deputy account already has, and we can add IP allowlisting where your setup supports it.

Frequently asked questions

Can Claude actually build and publish shifts in Deputy, not just read the roster?

Yes. A custom Deputy connector exposes a shift-creation write tool, so Claude drafts shifts from your roster, location, and availability rules and publishes them once you approve. Most default connections are read-leaning, which is why building and publishing schedules needs a purpose-built connector with scoped write access tied to your own permissions.

Will Claude approve timesheets or change schedules without my approval?

No. Approving timesheets and publishing schedules are separate, gated write actions. Because approved hours can flow into pay, Claude can prepare the changes and show you exactly what it will do, but nothing is committed until you confirm. You decide which actions run automatically and which always require an explicit approval step.

Does the Deputy connector get more access than I have?

No. The connector authenticates as your account through OAuth or a scoped token and inherits your existing Deputy permissions, including which locations and teams you can manage. It never grants Claude more access to rosters, timesheets, or employee records than your own account already has, and we scope it to only the tools the work requires.

Related connectors

Deel connector Justworks connector Paychex connector

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us