Connect
Optimize
Secure
Deputy MCP Server
for AI Agents
Production-ready Deputy MCP server with 48 extensible actions — plus built-in authentication, security, and optimized execution.
Deputy MCP Server
Built by 
StackOne
StackOne 
Coverage
48 Agent Actions
Create, read, update, and delete across Deputy — and extend your agent's capabilities with custom actions.
Authentication
Agent Tool Authentication
Per-user OAuth in one call. Your Deputy MCP server gets session-scoped tokens with zero credentials stored on your infra.
Agent Auth →
Security
Agent Protection
Every Deputy tool response scanned for prompt injection in milliseconds — 88.7% accuracy, all running on CPU.
Prompt Injection Defense →
Performance
Max Agent Context. Min Cost.
Free up to 96% of your agent's context window to enhance reasoning and reduce cost, on every Deputy call.
Tools Discovery →What is the Deputy MCP Server?
A Deputy MCP server lets AI agents read and write Deputy data through the Model Context Protocol — Anthropic's open standard for connecting LLMs to external tools. StackOne's Deputy MCP server ships with 48 pre-built actions, fully extensible via the Connector Builder — plus managed authentication, prompt injection defense, and optimized agent context. Connect it from MCP clients like Claude Desktop, Cursor, and VS Code, or from agent frameworks like OpenAI Agents SDK, LangChain, and Vercel AI SDK.
All Deputy MCP Tools and Actions
Every action from Deputy's API, ready for your agent. Create, read, update, and delete — scoped to exactly what you need.
Locations
- Create Location
Create a new location in Deputy
- List Locations
Get all locations (companies) in the Deputy installation
- Update Location
Update an existing location in Deputy
- Delete Location
Delete a location in Deputy
Employees
- Create Employee
Add an employee
- List Employees
Get details for all employees
- Get Employee
Get details for an employee by ID
- Update Employee
Update an existing employee
Employee Unavailabilitys
- Add Employee Unavailability
Add unavailability details for an employee
- Get Employee Unavailability
Get unavailability details for an employee
Rosters
- Copy Rosters
Copy rosters from one date range to another
- Publish Rosters
Publish rosters to make them visible to employees
Operational Units
- Create Operational Unit
Create a new operational unit (department/area)
- List Operational Units
Get all operational units (areas/departments)
- Update Operational Unit
Update an existing operational unit
- Delete Operational Unit
Delete an operational unit
Other (32)
- Add New Workplace
Add a new workplace/location to Deputy
- Add Location To Employee
Add a location against an employee
- Create Multiple Operational Units
Create multiple operational units (departments/areas) at once
- Create Memo
Create a memo in Deputy
- Get Employee Shift Status
Find out an employee's current status
- List Employee Agreements
Get all employee agreements
- Search Employment Contracts
Search for employment contracts using query filters
- Search Employment Contract Leave Rules
Search for employment contract leave rules
- List Employee Roles
Get all employee roles
- List Employee Workplaces
Get all employee workplace assignments
- Search Employee History
Search for employee history records
- List Employee Availability
Get all employee availability records
- List Employee Appraisals
Get all employee appraisal records
- List Employee Agreement History
Get all employee agreement history records
- List Employment Conditions
Get all employment condition records
- Get Recent Rosters
Get rosters from last 12 hours and forward 36 hours
- List Awards Library
Get awards library list
- Get Agreed Hours By Employee ID
Get agreed hours for a specific employee
- Retrieve Sales Data
Get sales metrics data
- List Categories
Get all categories
- List Custom Fields
Get all custom field definitions
- List Events
Get all events
- Remove Location From Employee
Remove a location from an employee
- Terminate Employee
Terminate an employee
- Activate Employee
Re-activate a terminated employee
- Invite Employee
Invite employee to Deputy
- Post A Journal
Post a journal entry for an employee
- Start Timesheet (Clock On)
Start an employee's timesheet (Clock On)
- Stop Timesheet (Clock Off)
Stop an employee's timesheet (Clock Off)
- Pause/Unpause Timesheet
Pause or unpause an employee's timesheet (take a break/finish break)
- View Timesheet Details
View a timesheet by ID
- Discard Rosters
Discard unpublished rosters
Set Up Your Deputy MCP Server in Minutes
One endpoint. Any framework. Your agent is talking to Deputy in under 10 lines of code.
MCP Clients
Agent Frameworks
JSON{
"mcpServers": {
"stackone": {
"command": "npx",
"args": [
"-y",
"mcp-remote@latest",
"https://api.stackone.com/mcp?x-account-id=<account_id>",
"--header",
"Authorization: Basic <YOUR_BASE64_TOKEN>"
]
}
}
}More HRIS / HCM MCP Servers
UKG Ready
140+ actions
Workday (Rest and Soap)
128+ actions
Factorial
127+ actions
HiBob
123+ actions
Oracle Fusion HCM
120+ actions
Humaans
117+ actions
BambooHR
100+ actions
Deputy MCP Server Resources
MCP Code Mode: Keeping Tool Responses Out of Agent Context
Anthropic's code_execution processes data already in context. Custom MCP code mode keeps raw tool responses in a sandbox. 14K tokens vs 500.
11 min
Comparing BM25, TF-IDF, and Hybrid Search for MCP Tool Discovery
Benchmarking BM25, TF-IDF, and hybrid search for MCP tool discovery across 916 tools. The 80/20 TF-IDF/BM25 hybrid hits 21% Top-1 accuracy in under 1ms.
10 min
Indirect Prompt Injection Defense for MCP Tools: A Technical Guide
MCP tools that read emails, CRM records, and tickets are indirect prompt injection vectors. Here's how we built a two-tier defense that scans tool results in ~11ms.
12 min
Deputy MCP Server FAQ
Deputy MCP server vs direct API integration — what's the difference?
A Deputy MCP server and direct API integration serve different use cases. Direct API integration is for software-to-software — backend code calling Deputy. A Deputy MCP server is for AI agents — MCP clients like Claude and Cursor, plus framework agents built with OpenAI, LangChain, or Vercel AI — discovering and calling Deputy at runtime. StackOne provides both.
How does Deputy authentication work for AI agents?
Deputy authentication for AI agents works through a StackOne Connect Session. Create one via the dashboard or the SDK — you get an auth link and ready-to-paste config for Claude Desktop, Cursor, and other MCP clients. Your user authenticates their own Deputy account; StackOne handles token exchange, storage, and refresh. Credentials never reach the LLM, and each user is isolated via
origin_owner_id.Are Deputy MCP tools vulnerable to prompt injection?
Yes — Deputy MCP tools can be vulnerable to indirect prompt injection. Any tool that reads user-written content — documents, messages, tickets, records, or free-text fields — is a potential vector. StackOne Defender scans every tool response before it enters the agent's context — regex patterns in ~1ms, then a MiniLM classifier in ~4ms. 88.7% accuracy, CPU-only.
What is the context bloat of a Deputy agent and how do I avoid it?
Context bloat happens when Deputy tool schemas and API responses eat your Deputy agent's memory, preventing it from reasoning effectively. A single Deputy query can return a massive JSON response, and connecting multiple tools compounds the problem. Tools Discovery and Code Mode reduce context bloat — loading only relevant tools per query and keeping raw responses out of the agent's context.
Can I limit which actions my Deputy agent can access?
Yes — you can limit which actions your Deputy agent can access directly from the StackOne dashboard. Toggle actions on or off, or restrict them to specific accounts, with no code changes to your agent. Session tokens can be scoped to exact actions so if one leaks, exposure stays contained.
Can I create custom agent actions for my Deputy MCP server?
Yes — you can create custom agent actions for your Deputy MCP server using Connector Builder. It's an integration agent your coding assistant (Claude Code, Cursor, or Copilot) can invoke to research Deputy's API, generate production-ready connector YAML, test against the live API, and validate before you ship.
When should I NOT use a Deputy MCP server?
Skip a Deputy MCP server if your integration is purely software-to-software — direct Deputy API integration is simpler when no AI agent is involved. For deterministic, compliance-critical operations (financial transactions, regulatory reporting), direct API gives you predictable behavior without agent-driven decision-making. MCP shines when AI agents need to dynamically discover and call Deputy actions at runtime.
What AI frameworks and AI clients does the StackOne Deputy MCP server support?
The StackOne Deputy MCP server supports both. MCP clients (paste-and-go apps): Claude Desktop, Claude Code, Cursor, VS Code, Goose. Agent frameworks (code SDKs you build with): OpenAI Agents SDK, Anthropic, Vercel AI, Google ADK, CrewAI, Pydantic AI, LangChain, LangGraph, Azure AI Foundry.
Put your AI agents to work
All the tools you need to build and scale AI agent integrations, with best-in-class connectivity, execution, and security.