Deputy and your AI assistant: the verdict, tools, and guardrails
Deputy, wired to your AI assistant through a hosted MCP connector: verdict first, tools second, guardrails throughout.
Every system here gets an honest, affirmative path: verified and instant, buildable and provisioned, human-assisted, or a done-for-you conversation. Zero dead ends.
Where Deputy stands today
Employee records, time off, and open roles: people questions answered from the system of record.
Also searched as deputy scheduling, deputy workforce. The vendor's developer documentation lives at developer.deputy.com.
What a Deputy connector would expose
The proposal you review during intake, separated into Read and Write. Nothing writes without asking you first.
Extracted from the vendor's API docs and human-reviewed before going live. Writes start one notch stricter.
- search_employees
Find employee records by name or department
- get_employee
Fetch one employee's profile fields
- list_time_off
List time-off requests and balances
- list_openings
List open positions and candidate counts
- update_employee_fieldconfirm
Update a non-sensitive profile field
fields: title, department, manager
- approve_time_offconfirm
Approve or decline a time-off request
fields: status, note
- add_candidate_noteconfirm
Add a note to a candidate
fields: body
- remove_employee_recorddestructivedry-run
Remove an employee record
fields: id
Every write asks first: it pauses on a preview of the exact change and runs only when you approve it, before anything reaches Deputy. Turn off anything you never want your AI to touch.
From "Deputy" to a working connector URL
Designed for operators, not developers. You never read API docs, manage tokens, or touch a line of code.
- 01
Name it
A 30-second eligibility check confirms your AI client accepts a custom connector URL, then you pick the software. This page pre-fills that step.
- 02
Describe what you need
Plain language, not configuration. What should the assistant be able to look up, and what should it be able to change?
- 03
Review your Connector Blueprint
The exact Read and Write tool list, before you pay anything. Every write ships on in confirm mode and asks before it runs, every tool is individually toggled, and anything destructive carries a distinct warning.
- 04
Deploy and paste the URL
You get a hosted connector URL plus paste-in instructions matched to your AI client, and a live test panel that confirms the connection.
Deputy supports Team mode
Deputy supports per-user credentials, so each team member connects as themselves: upstream audit trails stay truthful, each member's reach is capped by their own Deputy permissions, and per-member URLs are individually revocable.
You sign in to Deputy and approve access. The connector requests the scopes its tool surface needs at connect time; every write still asks first, you can turn tools off at any time, and no password is ever shared.
Write access to Deputy your IT team will approve
Reads run free; every write pauses on a preview a human approves, and every call is recorded in a per-connector activity log with redaction controls.
Confirm mode
Enabled writes run through Multi Round-Trip Requests: the tool pauses, shows a human-readable preview of the exact change, and only proceeds with approval. Nothing reaches Deputy on the model's intent alone.
Guardrails
Any tool can be turned off. Field-level constraints restrict what can be touched, per-tool rate limits are enforced at the gateway edge, and destructive operations ship in dry-run, demonstrating what they would do until you graduate them.
Activity log
Every tool call is logged: who, what, when, result. Write actions and confirmations are highlighted, redaction controls decide how much argument data is stored, and the log is append-only, with updates and deletes refused by the database.
Connecting Deputy: the specifics
Can my AI assistant write to Deputy?
Yes, with guardrails. Write tools work out of the box in confirm mode: every write asks first, pausing on a preview of the exact change before anything reaches Deputy. Destructive operations ship in dry-run and never execute until you graduate them, and you can turn off any tool you never want touched.
Is it safe to connect Deputy to an AI assistant?
Safety is the architecture, not a setting. Every write asks first: it pauses on a human confirmation with the exact change previewed before it reaches Deputy. Destructive operations demonstrate in dry-run and never execute until you graduate them, any tool can be turned off, and every call lands in an activity log with redaction controls.
If my team uses a Deputy connector, whose name is on the actions?
The right one. In Team mode each member connects with their own Deputy identity, so upstream audit trails show the real person, and each member's effective access is the intersection of the connector's guardrails and their own Deputy permissions. Per-member URLs are individually revocable.
Which AI clients work with a Deputy connector?
Any client that accepts a remote MCP connector URL: Claude (Free, Pro, Max, Team, and Enterprise), ChatGPT on paid plans with developer mode enabled, Cursor, and other MCP-compatible clients. Team and Enterprise workspaces may need an admin to allow custom connectors first.
How long until a Deputy connector is live?
Typically 24 to 72 hours. The mapping is generated from the Deputy API documentation and human-reviewed before it goes live.
Anything specific to the Deputy API worth knowing?
Yes. From our index notes on Deputy: Workforce scheduling and timesheets, not payroll processing; install-specific subdomain endpoints.
More HR & People systems
Same category, same connector quality. Every one gets an honest verdict.
See all HR & People connectors or browse the full directory.
Connect Deputy. We take it from there.
Start a 14-day free trial, no card: live reads plus 3 supervised writes, each executed only after you approve it.