# Deputy MCP server

Source: https://agentic-cmms.klementine.xyz/integrations/deputy

> Connect Deputy to Claude, ChatGPT and other AI agents to read rosters, open shifts, timesheets, leave and training records for every site you run.

Deputy is the rostering and timesheet system for shift-based businesses: facilities firms, cleaning and security contractors, hospitals, hospitality and retail. Managers build rosters by location and area, staff swap shifts and clock in from their phones, and timesheets flow into payroll. It works well on the floor. Answering "who can cover the plant room on Sunday?" still means scrolling through rosters, availability and training records.

Agentic CMMS turns Deputy into an MCP server, so Claude, ChatGPT and other AI agents can read rosters and timesheets in plain language. Managers ask one question instead of checking three screens.

## What your AI agent can do with Deputy

- **Find cover fast.** "Sunday's plant room shift at the hospital is open. Who is free, trained and under 38 hours this week?"
- **Read the roster.** "Show me next week's roster for the maintenance area at the Parramatta site." The agent reads shifts by location and area.
- **Check timesheets before the pay run.** "Which timesheets are still unapproved, and which ones have breaks missing?"
- **Spot late starts.** "Who clocked in more than ten minutes late on the early shift this week?"
- **Watch training expiry.** "Whose working-at-heights training expires before the next roster is published?" The agent reads training records with expiry dates.
- **Handle leave.** "Which leave requests are waiting for me, and do any of them leave the weekend short?"
- **Compare cost and hours.** "What was the rostered cost of the cleaning team compared with the hours actually worked last month?"

## Deputy with your other systems

Rosters decide who can do the work. Connect Deputy with your maintenance and finance tools and one question covers both:

- Assign this week's preventive maintenance in [MaintainX](/integrations/maintainx) only to technicians who are rostered on when each job is due.
- Check that every job booked in [ServiceM8](/integrations/servicem8) falls inside the attending technician's Deputy shift.
- Compare Deputy timesheet hours with the wages posted in [Xero](/integrations/xero) for each location.
- Before a contractor inspection in [Brightly Asset Essentials](/integrations/brightly-asset-essentials), confirm a qualified staff member is rostered to meet them.

## For managers who build rosters every week

Rostering is never finished: someone is sick, a shift opens, a certificate lapses. An agent with access to Deputy does the checking for you, so you decide faster. Owners and admins choose which roles may use each Deputy tool, so only managers can publish shifts. Each person approves their own agent, and every action lands in the activity log.

The result is fewer phone calls on a Sunday morning, fewer shifts left open, and fewer people on site with a training record that ran out last month. Your managers keep control; the agent does the looking up.

## Questions and answers

### Can Claude fill an open shift in Deputy?

Claude can find qualified staff who are free for an open shift. If your admins allow the tool and the person gave write access, it can also offer the shift to them.

### Does the agent see timesheets awaiting approval in Deputy?

Yes. It reads timesheets and their approval status, so a manager can see what is waiting before the pay run is exported.

### Can we see which rosters an agent changed in Deputy?

Yes. Every tool call, including each roster change, is recorded in the tamper-evident activity log with the person who asked.