deputy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEPUTY_TIMEOUT | No | Per-request HTTP timeout, seconds. | 30 |
| DEPUTY_BASE_URL | No | Your install origin, e.g. https://your-company.eu.deputy.com. | |
| DEPUTY_ENV_FILE | No | Path to a dotenv file to load `DEPUTY_*` values from. | |
| DEPUTY_API_TOKEN | No | Deputy permanent or OAuth access token (stored redacted). | |
| DEPUTY_CACHE_TTL | No | In-memory read-cache lifetime, seconds. `0` disables caching. | 30 |
| DEPUTY_MAX_RETRIES | No | Automatic retries on `429`/`5xx` (with backoff). | 3 |
| DEPUTY_ALLOW_WRITES | No | Enable the write tools. | false |
| DEPUTY_CALENDAR_URL | No | Your personal iCal feed URL (token-free, roster-only, stored redacted). | |
| DEPUTY_ALLOW_CUSTOM_HOST | No | Allow a base URL host outside `*.deputy.com` (enterprise custom domains). | false |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| deputy_whoamiA | Confirm the Deputy connection. In this configuration (iCal feed mode, no API token) it reports that only your own roster is available. When NOT to use: to read your shifts (use deputy_get_my_roster or deputy_next_shift). Returns markdown or, with response_format="json", an object |
| deputy_get_my_calendar_urlA | Confirm that your personal calendar feed is configured. The feed link itself is a secret in this mode and is never shown. When NOT to use: to read the shifts in the feed (use deputy_get_my_roster). Returns markdown or, with response_format="json", an object |
| deputy_get_my_rosterA | List your own shifts in a date range from your personal Deputy calendar feed. Defaults to today through the next 7 days; dates are ISO YYYY-MM-DD. Times are shown in UTC in this mode. When NOT to use: for only the single next shift (use deputy_next_shift). Returns markdown (a shift list) or, with response_format="json", a list of Roster records. |
| deputy_next_shiftA | Return your own next upcoming shift from your personal Deputy calendar feed. Leave 'employee' empty: other people's shifts are not available in this mode. When NOT to use: for a range of shifts (use deputy_get_my_roster). Returns markdown (one shift, or a note that none is scheduled) or, with response_format="json", a single Roster record or null. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| summarize_my_week | Summarize the user's scheduled shifts and worked hours for the week. |
| coverage_check | Check staffing coverage for a date: rostered staff, open shifts, who is on. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| my_roster_this_week | Your own shifts for the current week (Monday-Sunday), rendered as markdown. |
| my_roster_next_week | Your own shifts for next week (Monday-Sunday), rendered as markdown. |
TDQS
Scored across 4 tools
Each tool has a distinct role (config check, date-range roster, single next shift, connection status) and descriptions include explicit 'When NOT to use' cross-references that steer selection well. The only soft overlap is between deputy_whoami and deputy_get_my_calendar_url, which both act as 'confirm configuration' probes and could be confused by an agent wanting a simple health check.
All four tools share the deputy_ prefix and are snake_case, giving a predictable, readable surface. Minor deviation: two are verb_noun (get_my_roster, get_my_calendar_url) while next_shift drops the verb and whoami is a conventional standalone name.
Four tools is a tight, well-scoped set for a read-only personal-roster integration, and each tool covers a real user intent. It sits at the thin end of the scale, but nothing feels redundant or padded for the stated iCal-feed mode.
For the declared read-only personal calendar domain, the surface is essentially complete: identity/mode check, configuration check, a date-range shift list, and a next-shift shortcut, with both markdown and JSON outputs. Gaps are deliberate (no team visibility, no write/lifecycle operations), so agents cannot get stuck on covered workflows but also cannot do anything beyond reading their own shifts.