Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Deputy to Claude Code

Have Claude build shifts and approve timesheets in Deputy. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Deputy to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Deputy, you add a Deputy MCP server: a small hosted service that exposes Deputy's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Deputy account. No API keys pasted into config files.

claude mcp add --transport http deputy https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Deputy once connected?

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

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Deputy access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Deputy API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Deputy changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Deputy connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Deputy connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Deputy account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Deputy's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to Deputy?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Deputy account it signs in with. Revoking access is one click in Deputy.

More on the Deputy connector

Deputy connector for claude.aiDeel + Claude CodeJustworks + Claude CodePaychex + Claude Code

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 connectorTalk to us