How to Connect Deputy to Claude via MCP

💡 No install? Use cloud.anythingmcp.com directly. Sign in, click Connectors → Deputy, paste your credentials, mint an MCP API key and you're done. No Docker, no git clone, no local server.

Deputy + Claude

Deputy workforce management for one install: employees, locations and areas, rosters (shifts) with copying and publishing, timesheets with clock on and off and approval, leave and unavailability, memos, manager notes and any other record through the resource query API. Connects with a permanent token.

Prerequisites

See the full setup instructions baked into the connector (visible in the in-app store when you select the connector). The required environment variables for this connector are:

DEPUTY_HOST, DEPUTY_ACCESS_TOKEN

Step 1 — Get credentials

Setting up takes about 5 minutes and needs a Deputy system administrator.

1. Note your install address from the browser bar when you are logged in, for example mycompany.au.deputy.com (regions au, eu, uk, and na for the US). Put it into DEPUTY_HOST without https:// and without a path.
2. Open https://<your install address>/exec/devapp/oauth_clients, add an OAuth client (any name and description; the client id itself is not used), then click Get an Access Token.
3. Copy the permanent token right away (it is shown only once) into DEPUTY_ACCESS_TOKEN. Install the connector: deputy_get_me is the install check.

The token works only on the install that issued it and acts as the user who created it, with that user's permissions. A system administrator sees every location.

Personal data: employee records hold names, dates of birth, contact details, addresses and pay data. Ask only for what the task needs.

Deputy's words: a location (workplace) is a Company, an area (department) an OperationalUnit, a shift a Roster, actual worked time a Timesheet and a leave type a LeaveRules record.

What it reads:

• The token user: deputy_get_me and their own shifts, timesheets, leave, unavailability, locations and colleagues (deputy_get_my_rosters, deputy_get_my_timesheets, deputy_get_my_leave, deputy_get_my_unavailability, deputy_get_my_locations, deputy_get_my_colleagues).
• Structure and people: deputy_list_locations, deputy_list_areas (each area belongs to a location; shifts and timesheets use area ids), deputy_list_employees, deputy_get_employee, deputy_query_employees for filters, and deputy_get_employee_shift_status for who is working right now.
• Schedule: deputy_list_rosters covers 12 hours back to 36 hours ahead; deputy_query_rosters any period, employee or area (filter on Date, Employee, OperationalUnit).
• Time: deputy_query_timesheets and deputy_get_timesheet (slots, breaks, pay lines, comments and approval state).
• Leave and availability: deputy_query_leave, deputy_get_employee_leave, deputy_get_employee_unavailability and deputy_query_availability. Leave types come from deputy_query_resource with object LeaveRules.
• Everything else (teams, public holidays, events, training, custom fields, sales data, pay periods and more): deputy_get_resource_info lists an object's fields, deputy_query_resource searches it and deputy_get_resource reads one record.

What it writes:

• Schedule: deputy_save_shift adds a shift or, with roster_id, updates one; deputy_copy_rosters copies a date range of some areas forward (for example last week to this week); deputy_publish_rosters publishes shifts with the chosen notification (notify 1 SMS and email, 2 SMS, 3 email, 4 none, 5 ask employees to confirm).
• Time: deputy_start_timesheet, deputy_pause_timesheet (calling it again ends the break) and deputy_end_timesheet clock an employee on and off; deputy_save_timesheet adds or fixes a finished timesheet; deputy_approve_timesheet approves time so it can be exported to payroll.
• Leave and availability: deputy_add_leave (status 0 waits for manager approval, 1 records leave that is already approved and affects timesheets and balances), deputy_update_leave (approve, decline or cancel with status 1, 2 or 3) and deputy_add_unavailability (once or repeating, for example every second Monday).
• Employees: deputy_add_employee, deputy_update_employee, deputy_invite_employee (emails a login invitation), deputy_terminate_employee (they can no longer log in or be rostered; reversible) and deputy_reactivate_employee.
• Notes and news: deputy_post_journal adds a private manager note to an employee's profile; deputy_post_memo posts to a location's news feed, optionally to selected users and asking them to confirm they read it.

Publishing shifts, invitations and memos reach real employees, so check the shifts and the notification before you ask for them.

Switched off at install: deputy_delete_employee, deputy_discard_rosters and deputy_discard_timesheet. They cannot be undone; a workspace admin switches them on when the team needs them. Terminating an employee is the reversible alternative to deleting one.

Query tools: deputy_query_* and deputy_query_resource send POST but only read. The search body holds clauses that must all match, for example {"s1":{"field":"Date","type":"ge","data":"2026-11-01"},"s2":{"field":"Date","type":"le","data":"2026-11-07"}}, with the operators eq, ne, gt, ge, lt, le, in, not in, starts, contains, is and is not. sort ({"Date":"asc"}) and join (["EmployeeObject"]) are optional.

Data formats: ids are integers. StartTime, EndTime and the start and end inputs are Unix timestamps in seconds; Date fields are local dates of the location (2026-11-03T00:00:00+11:00), so times are converted with the location's time zone. A roster with Employee 0 is an open shift, Published false a draft. Timesheet state is in TimeApproved, PayRuleApproved, Discarded and IsInProgress; TotalTime is in hours. Leave Status: 0 awaiting approval, 1 approved, 2 declined, 3 cancelled, 4 pay approved. Adding or updating a shift answers 200 with an empty body; the AI checks the result with deputy_query_rosters.

Paging: an answer holds at most 500 records. Query tools take max (up to 500) and start (offset); when a page is full, the AI calls again with start raised by max. The list tools without paging return everything Deputy allows in one answer.

Common errors: 401 means a wrong token or a token of another install, 403 a permission the token's user lacks, 404 a wrong install address or record id, 400 a bad field name in a filter (check it with deputy_get_resource_info).

The connector does not export timesheets to a payroll system itself, does not create locations or areas and does not delete anything while the delete tools are switched off.

Step 2 — Install the adapter

curl -fsSL https://raw.githubusercontent.com/HelpCode-ai/anythingmcp/main/docker-compose.quickstart.yml -o docker-compose.yml
printf 'JWT_SECRET=%s\nENCRYPTION_KEY=%s\n' "$(openssl rand -hex 32)" "$(openssl rand -hex 32)" > .env
docker compose up -d

Step 3 — Add the connector in Claude

Your server URL: in AnythingMCP, open MCP Servers → the server this connector is on, and copy its URL (https://cloud.anythingmcp.com/mcp/…). Use it wherever this guide shows YOUR_SERVER_ID.

Recommended path: works on claude.ai web without editing any config file.

1. In Claude, open Customize → Connectors.
2. Click +, then Add custom connector.
3. Enter a name, e.g. Deputy, and the remote MCP server URL https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID, then click Add.
4. Click Connect and sign in to AnythingMCP (OAuth) to allow access.

All tools below appear in your chat: start typing prompts.

Available tools

Example prompts

• "Who is working at the Sydney store right now, and who starts next?"
• "Show next week's roster for the Kitchen area, including open shifts."
• "List last week's timesheets that are not approved yet, with employee and total hours."
• "Copy last week's shifts of the Bar area to this week and show me the drafts before publishing."
• "Which leave requests are awaiting approval this month?"

FAQ

Does it work with Claude Code as well as Claude Desktop? Yes, point both at https://cloud.anythingmcp.com/mcp/YOUR_SERVER_ID.

Next steps

• Connector landing page
• Connect to ChatGPT
• Connect to Cursor
• Connect to Gemini
• Connect to Meta Muse
• Connect to Microsoft Copilot