Query Workday HCM data including workers, organizations, time off, and job requisitions through a standardized MCP interface.
Also known as mindstone/mcp-servers, mcp-server-workday, @mindstone/mcp-server-workday
- Stars
- 14
- Tools
- 9
- Downloads, 30 days
- —
- Latest version
- 0.3.2
- Last commit
- Nov 16, 2026
- License
- —
What is Workday MCP?
Workday queries Workday HCM data including workers, organizations, time off, and job requisitions through a standardized MCP interface. It exposes 9 tools, such as configure_workday_credentials, list_workday_workers, get_workday_worker.
Summary generated from the project's README
About Workday MCP server
Accessing human capital management data directly from your AI client is what this server enables for HR professionals and developers. It provides a standardized interface to query Workday HCM information, including worker profiles, organizational structures, job assignments, and recruiting data. By connecting to your Workday instance via OAuth 2.0, the server allows an AI to retrieve specific details about employees, their direct reports, work locations, and open job requisitions.
Setup requires Node.js 20+ and specific environment variables such as WORKDAY_HOST, WORKDAY_TENANT, and OAuth credentials. Users can configure the server for use in environments like Claude Desktop, Cursor, or VS Code. The server includes nine specialized tools to manage data retrieval across workers, organizations, time off, and recruiting. To maintain security, the server uses field allowlisting to ensure sensitive free-text data like street addresses or time-off comments never reach the model, and it wraps all returned strings in untrusted content envelopes to prevent instruction injection.
What you can do with it
- 1Retrieve employee profilesAsk the AI to find a specific worker's full profile using their unique ID.
- 2Analyze organizational structuresRequest a list of all direct reports for a specific manager to understand the reporting line.
- 3Monitor open job rolesQuery the system to see a list of current job requisitions and open positions.
- 4Check employee time offIdentify the time-off entries recorded for a particular worker.
Written from the project's README. Every use case is checked against a quote from it.
How to install Workday MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Workday MCP in Claude Code
$ claude mcp add --env 'WORKDAY_CLIENT_SECRET=<YOUR_WORKDAY_CLIENT_SECRET>' --env 'WORKDAY_CLIENT_ID=<WORKDAY_CLIENT_ID>' --env 'WORKDAY_HOST=<WORKDAY_HOST>' --env 'WORKDAY_TENANT=<WORKDAY_TENANT>' --env 'WORKDAY_REFRESH_TOKEN=<YOUR_WORKDAY_REFRESH_TOKEN>' mcp-server-workday -- npx -y @mindstone/mcp-server-workdayInstall Workday MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"mcp-server-workday": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-workday"
],
"env": {
"WORKDAY_CLIENT_SECRET": "<YOUR_WORKDAY_CLIENT_SECRET>",
"WORKDAY_CLIENT_ID": "<WORKDAY_CLIENT_ID>",
"WORKDAY_HOST": "<WORKDAY_HOST>",
"WORKDAY_TENANT": "<WORKDAY_TENANT>",
"WORKDAY_REFRESH_TOKEN": "<YOUR_WORKDAY_REFRESH_TOKEN>"
}
}
}
}Install Workday MCP in VS Code
.vscode/mcp.json
{
"servers": {
"mcp-server-workday": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-workday"
],
"env": {
"WORKDAY_CLIENT_SECRET": "<YOUR_WORKDAY_CLIENT_SECRET>",
"WORKDAY_CLIENT_ID": "<WORKDAY_CLIENT_ID>",
"WORKDAY_HOST": "<WORKDAY_HOST>",
"WORKDAY_TENANT": "<WORKDAY_TENANT>",
"WORKDAY_REFRESH_TOKEN": "<YOUR_WORKDAY_REFRESH_TOKEN>"
}
}
}
}Install Workday MCP in VS Code CLI
$ code --add-mcp '{"name":"mcp-server-workday","type":"stdio","command":"npx","args":["-y","@mindstone/mcp-server-workday"],"env":{"WORKDAY_CLIENT_SECRET":"<YOUR_WORKDAY_CLIENT_SECRET>","WORKDAY_CLIENT_ID":"<WORKDAY_CLIENT_ID>","WORKDAY_HOST":"<WORKDAY_HOST>","WORKDAY_TENANT":"<WORKDAY_TENANT>","WORKDAY_REFRESH_TOKEN":"<YOUR_WORKDAY_REFRESH_TOKEN>"}}'Install Workday MCP in Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"mcp-server-workday": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-workday"
],
"env": {
"WORKDAY_CLIENT_SECRET": "<YOUR_WORKDAY_CLIENT_SECRET>",
"WORKDAY_CLIENT_ID": "<WORKDAY_CLIENT_ID>",
"WORKDAY_HOST": "<WORKDAY_HOST>",
"WORKDAY_TENANT": "<WORKDAY_TENANT>",
"WORKDAY_REFRESH_TOKEN": "<YOUR_WORKDAY_REFRESH_TOKEN>"
}
}
}
}Install Workday MCP in Codex
$ codex mcp add mcp-server-workday --env 'WORKDAY_CLIENT_SECRET=<YOUR_WORKDAY_CLIENT_SECRET>' --env 'WORKDAY_CLIENT_ID=<WORKDAY_CLIENT_ID>' --env 'WORKDAY_HOST=<WORKDAY_HOST>' --env 'WORKDAY_TENANT=<WORKDAY_TENANT>' --env 'WORKDAY_REFRESH_TOKEN=<YOUR_WORKDAY_REFRESH_TOKEN>' -- npx -y @mindstone/mcp-server-workdayInstall Workday MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.mcp-server-workday] command = "npx" args = ["-y", "@mindstone/mcp-server-workday"] [mcp_servers.mcp-server-workday.env] WORKDAY_CLIENT_SECRET = "<YOUR_WORKDAY_CLIENT_SECRET>" WORKDAY_CLIENT_ID = "<WORKDAY_CLIENT_ID>" WORKDAY_HOST = "<WORKDAY_HOST>" WORKDAY_TENANT = "<WORKDAY_TENANT>" WORKDAY_REFRESH_TOKEN = "<YOUR_WORKDAY_REFRESH_TOKEN>"
Install Workday MCP in Gemini CLI
$ gemini mcp add -s user -e 'WORKDAY_CLIENT_SECRET=<YOUR_WORKDAY_CLIENT_SECRET>' -e 'WORKDAY_CLIENT_ID=<WORKDAY_CLIENT_ID>' -e 'WORKDAY_HOST=<WORKDAY_HOST>' -e 'WORKDAY_TENANT=<WORKDAY_TENANT>' -e 'WORKDAY_REFRESH_TOKEN=<YOUR_WORKDAY_REFRESH_TOKEN>' mcp-server-workday npx -- -y @mindstone/mcp-server-workdayInstall Workday MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"mcp-server-workday": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-workday"
],
"env": {
"WORKDAY_CLIENT_SECRET": "<YOUR_WORKDAY_CLIENT_SECRET>",
"WORKDAY_CLIENT_ID": "<WORKDAY_CLIENT_ID>",
"WORKDAY_HOST": "<WORKDAY_HOST>",
"WORKDAY_TENANT": "<WORKDAY_TENANT>",
"WORKDAY_REFRESH_TOKEN": "<YOUR_WORKDAY_REFRESH_TOKEN>"
}
}
}
}Started by HostedMCP on 16 Nov 2026
We ran this command for @mindstone/mcp-server-workday 0.3.2 in an isolated container with no network and no keys. It answered and listed 9 tools.
Workday MCP tools 9
Read from the server with tools/listconfigure_workday_credentialsActionHost-managed setup only. The user adds their Workday OAuth credentials in Settings → Connectors in the app. Do not ask for or accept credentials in chat. SETUP PREREQUISITES: 1. A Workday Integration System User (ISU) with appropriate security group access 2. An API Client registered in Workday (Tenant Setup > API Clients) 3. The Client ID and Client Secret from the API Client registration 4. Optionally, a pre-generated Refresh Token (from OAuth token exchange) PARAMETERS: - host: Workday API domain (e.g., "wd5-impl-services1.workday.com") - tenant: Your Workday tenant name (e.g., "acme_corp") - client_id: OAuth Client ID from API Client registration - client_secret: OAuth Client Secret - refresh_token: (Optional) Pre-generated refresh token. If omitted, uses client_credentials grant. COMMON MISTAKES: - Host should be just the domain (e.g., "wd5-impl-services1.workday.com"), not a full URL - Tenant name is case-sensitive - The ISU must have permissions for the REST API resources you want to access
list_workday_workersRead-onlyList or search workers (employees and contingent workers) in Workday. Returns compact worker summaries: ID, name, email, title, manager status. Example: {} Example: { "search": "Jane Smith" } Example: { "limit": 20, "offset": 100 } Pagination: Returns up to 'limit' results (default 50, max 100). Use 'offset' for next page. RELATED TOOLS: - get_workday_worker: Pass a worker's id to get their full profile - list_workday_direct_reports: See who reports to a worker - list_workday_organizations: Browse organizational structure COMMON MISTAKES: - search is a free-text filter matched client-side against name, email, and business title (case-insensitive substring) — not a Workday query language. Workday's /workers collection only supports limit/offset, so the connector pages through workers and filters locally, scanning at most 1000 workers. On larger tenants a search may miss workers beyond that scan window; narrow with a more specific term. - Maximum limit is 100 per request; use offset for pagination
get_workday_workerRead-onlyGet a worker's full profile by ID from Workday. Returns detailed profile: name, email, title, manager status, location, supervisory organization, years of service. Example: { "worker_id": "3aa5550b7fe348b98d7b5741afc65534" } WORKFLOW - To find a worker: 1. Call list_workday_workers to search by name or email 2. Use the worker's id from the results here RELATED TOOLS: - list_workday_workers: Search/browse workers to find IDs - list_workday_organizations: See org structure
list_workday_organizationsRead-onlyList organizations (departments, supervisory orgs, cost centers, etc.) in Workday. Returns: ID, name/descriptor, type, active status. Example: {} Example: { "limit": 25, "offset": 50 } Pagination: Returns up to 'limit' results (default 50, max 100). Use 'offset' for next page. RELATED TOOLS: - list_workday_workers: Browse workers in the organization - get_workday_worker: See which organization a worker belongs to
list_workday_locationsRead-onlyList work locations (offices, sites) in Workday. Returns per location: ID, name/descriptor, active status, type. Street addresses and other free-text fields are deliberately excluded. Example: {} Example: { "limit": 25, "offset": 50 } RELATED TOOLS: - get_workday_worker: See which location a worker is assigned to - list_workday_job_requisitions: See where open roles are located
list_workday_direct_reportsRead-onlyList a worker's direct reports in Workday (one level of the org chart). Returns compact worker summaries: ID, name, email, title, manager status. Example: { "worker_id": "3aa5550b7fe348b98d7b5741afc65534" } WORKFLOW - To explore the org chart: 1. Call list_workday_workers to find a manager by name 2. Pass their id here to list their team 3. Call again with a report's id to walk deeper RELATED TOOLS: - list_workday_workers: Search/browse workers to find IDs - get_workday_worker: Full profile for one worker
list_workday_time_offRead-onlyList a worker's time-off entries (vacation, sick leave, etc.) from Workday absence management. Returns per-entry: ID, time-off type, start/end dates, quantity, unit, status. Comment and reason fields are deliberately excluded from the response. Example: { "worker_id": "3aa5550b7fe348b98d7b5741afc65534" } REQUIRED PERMISSIONS: - The ISU's security group needs access to the Absence Management domain (Time Off), otherwise Workday returns 403. RELATED TOOLS: - list_workday_workers: Search/browse workers to find IDs - list_workday_direct_reports: Find a manager's team before checking their time off
list_workday_job_requisitionsRead-onlyList job requisitions (open roles being hired for) in Workday recruiting. Returns per requisition: ID, title/descriptor, status, number of openings, hiring manager, supervisory organization, primary location, job profile. Description and other free-text fields are deliberately excluded. Example: {} Example: { "limit": 25, "offset": 50 } REQUIRED PERMISSIONS: - The ISU's security group needs access to the Recruiting domain (Job Requisitions), otherwise Workday returns 403. - The recruiting REST family is versioned by Workday platform release. The connector defaults to v41.2; if the tenant exposes a different version (404s), set WORKDAY_RECRUITING_API_VERSION (e.g. "v42.1"). RELATED TOOLS: - list_workday_organizations: Browse the orgs a requisition belongs to - list_workday_jobs: See current worker job assignments
list_workday_jobsRead-onlyList worker job assignments in Workday (position, title, location, organization per job). Returns per job: ID, business title, job type, worker, location, job profile, supervisory organization (references trimmed to ID + name). Example: {} Example: { "limit": 25, "offset": 50 } REQUIRED PERMISSIONS: - The ISU's security group needs access to the Payroll domain that exposes the jobs collection (payroll/v2 family), otherwise Workday returns 403. RELATED TOOLS: - list_workday_workers: Browse workers directly - get_workday_worker: Full profile for one worker
| configure_workday_credentials | Host-managed setup only. The user adds their Workday OAuth credentials in Settings → Connectors in the app. Do not ask for or accept credentials in chat. SETUP PREREQUISITES: 1. A Workday Integration System User (ISU) with appropriate security group access 2. An API Client registered in Workday (Tenant Setup > API Clients) 3. The Client ID and Client Secret from the API Client registration 4. Optionally, a pre-generated Refresh Token (from OAuth token exchange) PARAMETERS: - host: Workday API domain (e.g., "wd5-impl-services1.workday.com") - tenant: Your Workday tenant name (e.g., "acme_corp") - client_id: OAuth Client ID from API Client registration - client_secret: OAuth Client Secret - refresh_token: (Optional) Pre-generated refresh token. If omitted, uses client_credentials grant. COMMON MISTAKES: - Host should be just the domain (e.g., "wd5-impl-services1.workday.com"), not a full URL - Tenant name is case-sensitive - The ISU must have permissions for the REST API resources you want to access | Action |
| list_workday_workers | List or search workers (employees and contingent workers) in Workday. Returns compact worker summaries: ID, name, email, title, manager status. Example: {} Example: { "search": "Jane Smith" } Example: { "limit": 20, "offset": 100 } Pagination: Returns up to 'limit' results (default 50, max 100). Use 'offset' for next page. RELATED TOOLS: - get_workday_worker: Pass a worker's id to get their full profile - list_workday_direct_reports: See who reports to a worker - list_workday_organizations: Browse organizational structure COMMON MISTAKES: - search is a free-text filter matched client-side against name, email, and business title (case-insensitive substring) — not a Workday query language. Workday's /workers collection only supports limit/offset, so the connector pages through workers and filters locally, scanning at most 1000 workers. On larger tenants a search may miss workers beyond that scan window; narrow with a more specific term. - Maximum limit is 100 per request; use offset for pagination | Read-only |
| get_workday_worker | Get a worker's full profile by ID from Workday. Returns detailed profile: name, email, title, manager status, location, supervisory organization, years of service. Example: { "worker_id": "3aa5550b7fe348b98d7b5741afc65534" } WORKFLOW - To find a worker: 1. Call list_workday_workers to search by name or email 2. Use the worker's id from the results here RELATED TOOLS: - list_workday_workers: Search/browse workers to find IDs - list_workday_organizations: See org structure | Read-only |
| list_workday_organizations | List organizations (departments, supervisory orgs, cost centers, etc.) in Workday. Returns: ID, name/descriptor, type, active status. Example: {} Example: { "limit": 25, "offset": 50 } Pagination: Returns up to 'limit' results (default 50, max 100). Use 'offset' for next page. RELATED TOOLS: - list_workday_workers: Browse workers in the organization - get_workday_worker: See which organization a worker belongs to | Read-only |
| list_workday_locations | List work locations (offices, sites) in Workday. Returns per location: ID, name/descriptor, active status, type. Street addresses and other free-text fields are deliberately excluded. Example: {} Example: { "limit": 25, "offset": 50 } RELATED TOOLS: - get_workday_worker: See which location a worker is assigned to - list_workday_job_requisitions: See where open roles are located | Read-only |
| list_workday_direct_reports | List a worker's direct reports in Workday (one level of the org chart). Returns compact worker summaries: ID, name, email, title, manager status. Example: { "worker_id": "3aa5550b7fe348b98d7b5741afc65534" } WORKFLOW - To explore the org chart: 1. Call list_workday_workers to find a manager by name 2. Pass their id here to list their team 3. Call again with a report's id to walk deeper RELATED TOOLS: - list_workday_workers: Search/browse workers to find IDs - get_workday_worker: Full profile for one worker | Read-only |
| list_workday_time_off | List a worker's time-off entries (vacation, sick leave, etc.) from Workday absence management. Returns per-entry: ID, time-off type, start/end dates, quantity, unit, status. Comment and reason fields are deliberately excluded from the response. Example: { "worker_id": "3aa5550b7fe348b98d7b5741afc65534" } REQUIRED PERMISSIONS: - The ISU's security group needs access to the Absence Management domain (Time Off), otherwise Workday returns 403. RELATED TOOLS: - list_workday_workers: Search/browse workers to find IDs - list_workday_direct_reports: Find a manager's team before checking their time off | Read-only |
| list_workday_job_requisitions | List job requisitions (open roles being hired for) in Workday recruiting. Returns per requisition: ID, title/descriptor, status, number of openings, hiring manager, supervisory organization, primary location, job profile. Description and other free-text fields are deliberately excluded. Example: {} Example: { "limit": 25, "offset": 50 } REQUIRED PERMISSIONS: - The ISU's security group needs access to the Recruiting domain (Job Requisitions), otherwise Workday returns 403. - The recruiting REST family is versioned by Workday platform release. The connector defaults to v41.2; if the tenant exposes a different version (404s), set WORKDAY_RECRUITING_API_VERSION (e.g. "v42.1"). RELATED TOOLS: - list_workday_organizations: Browse the orgs a requisition belongs to - list_workday_jobs: See current worker job assignments | Read-only |
| list_workday_jobs | List worker job assignments in Workday (position, title, location, organization per job). Returns per job: ID, business title, job type, worker, location, job profile, supervisory organization (references trimmed to ID + name). Example: {} Example: { "limit": 25, "offset": 50 } REQUIRED PERMISSIONS: - The ISU's security group needs access to the Payroll domain that exposes the jobs collection (payroll/v2 family), otherwise Workday returns 403. RELATED TOOLS: - list_workday_workers: Browse workers directly - get_workday_worker: Full profile for one worker | Read-only |
Configuration
WORKDAY_CLIENT_SECRETRequiredSecretWorkday OAuth 2.0 client secret
WORKDAY_CLIENT_IDRequiredWorkday OAuth 2.0 client ID
WORKDAY_HOSTRequiredWorkday API host (e.g. wd5-impl-services1.workday.com)
WORKDAY_TENANTRequiredWorkday tenant ID
WORKDAY_REFRESH_TOKENSecretWorkday OAuth 2.0 refresh token (optional; enables the refresh_token grant)
WORKDAY_RECRUITING_API_VERSIONOptional override for the recruiting REST family version (e.g. v41.2) when the tenant exposes a different Workday platform release
| Name | Description | |
|---|---|---|
| WORKDAY_CLIENT_SECRET | Workday OAuth 2.0 client secret | RequiredSecret |
| WORKDAY_CLIENT_ID | Workday OAuth 2.0 client ID | Required |
| WORKDAY_HOST | Workday API host (e.g. wd5-impl-services1.workday.com) | Required |
| WORKDAY_TENANT | Workday tenant ID | Required |
| WORKDAY_REFRESH_TOKEN | Workday OAuth 2.0 refresh token (optional; enables the refresh_token grant) | Secret |
| WORKDAY_RECRUITING_API_VERSION | Optional override for the recruiting REST family version (e.g. v41.2) when the tenant exposes a different Workday platform release |
Automated checks
Ran Nov 12, 2026Full report →Passed our automated checks. That is not a security audit: read the code and give the server the narrowest access it needs. How checks work · What to fix for more points
- Source repository linked and reachablePass
- Open source license (OSI)No licenseFinding
- Commit or release in the last yearPass
- Package name not close to a popular packagePass
- Remote endpoint uses HTTPSNot checked
- Destructive tools are labelledPass
- No hidden instructions to the modelPass
- No critical advisory in the package or its dependenciesPass
README
View on GitHub@mindstone/mcp-server-workday
Workday HCM MCP server for Model Context Protocol hosts. Query workers, profiles, direct reports, organizations, locations, jobs, time off, and job requisitions in Workday through a standardised MCP interface using OAuth 2.0 authentication.
Status
- Version: 0.3.2 · npm
- Auth: OAuth (
WORKDAY_REFRESH_TOKEN) - Tools: 9 (workers, organizations, time off, recruiting, locations, jobs)
- Surface: cloud-api
- Machine-readable:
STATUS.json
Requirements
- Node.js 20+
- npm
One-click install
After clicking the button, your host will prompt you to fill: WORKDAY_HOST, WORKDAY_TENANT, WORKDAY_CLIENT_ID, WORKDAY_CLIENT_SECRET, WORKDAY_REFRESH_TOKEN.
{
"mcpServers": {
"Workday": {
"command": "npx",
"args": [
"-y",
"@mindstone/mcp-server-workday"
],
"env": {
"WORKDAY_HOST": "",
"WORKDAY_TENANT": "",
"WORKDAY_CLIENT_ID": "",
"WORKDAY_CLIENT_SECRET": "",
"WORKDAY_REFRESH_TOKEN": ""
}
}
}
}
Quick Start
Install & build
cd <path-to-repo>/connectors/workday
npm install
npm run build
npx (once published)
npx -y @mindstone/mcp-server-workday
Local
node dist/index.js
Configuration
Environment variables
WORKDAY_HOST— Workday API host (e.g.wd5-impl-services1.workday.com)WORKDAY_TENANT— Workday tenant IDWORKDAY_CLIENT_ID— OAuth 2.0 client IDWORKDAY_CLIENT_SECRET— OAuth 2.0 client secretWORKDAY_REFRESH_TOKEN— optional OAuth 2.0 refresh token (enables the refresh_token grant; without it the client_credentials grant is used)WORKDAY_RECRUITING_API_VERSION— optional override for the recruiting REST family version (defaultv41.2; Workday versions this API by platform release, so tenants on a different release may need e.g.v42.1)MCP_HOST_BRIDGE_STATE— optional path to a host bridge state file used for credential managementMINDSTONE_REBEL_BRIDGE_STATE— backwards-compatible alias forMCP_HOST_BRIDGE_STATE
Host configuration examples
Claude Desktop / Cursor
{
"mcpServers": {
"Workday": {
"command": "npx",
"args": ["-y", "@mindstone/mcp-server-workday"],
"env": {
"WORKDAY_HOST": "wd5-impl-services1.workday.com",
"WORKDAY_TENANT": "your-tenant",
"WORKDAY_CLIENT_ID": "your-client-id",
"WORKDAY_CLIENT_SECRET": "your-client-secret",
"WORKDAY_REFRESH_TOKEN": "your-refresh-token"
}
}
}
}
Local development (no npm publish needed)
{
"mcpServers": {
"Workday": {
"command": "node",
"args": ["<path-to-repo>/connectors/workday/dist/index.js"],
"env": {
"WORKDAY_HOST": "wd5-impl-services1.workday.com",
"WORKDAY_TENANT": "your-tenant",
"WORKDAY_CLIENT_ID": "your-client-id",
"WORKDAY_CLIENT_SECRET": "your-client-secret",
"WORKDAY_REFRESH_TOKEN": "your-refresh-token"
}
}
}
}
Tools (9)
Configuration
configure_workday_credentials— Configure Workday OAuth API credentials
Workers
list_workday_workers— List or search workers (employees and contingent workers)get_workday_worker— Get a worker's full profile by IDlist_workday_direct_reports— List a worker's direct reports (one level of the org chart)
Organizations
list_workday_organizations— List organizations (departments, supervisory orgs, cost centers)list_workday_locations— List work locations (offices, sites)
Time off
list_workday_time_off— List a worker's time-off entries (requires the ISU to have Absence Management domain access)
Recruiting
list_workday_job_requisitions— List job requisitions / open roles (requires Recruiting domain access; seeWORKDAY_RECRUITING_API_VERSIONif your tenant 404s)
Jobs
list_workday_jobs— List worker job assignments (position, title, location, organization)
Notes
- Search is client-side. Workday's
/workerscollection documents onlylimit/offset, solist_workday_workers'searchargument pages through workers and filters locally (case-insensitive match on name, email, title), scanning at most 1000 workers. On larger tenants, use a specific term. - Field allowlisting. Every tool trims Workday's responses to an allowlisted set of fields (and deep-picks nested references to ID + name), so free-text fields such as time-off comments, requisition descriptions, and street addresses never reach the model.
- Untrusted-content envelopes. Every allowlisted string returned from Workday (names, titles, emails, statuses, dates — including values that arrive in an unexpected shape) is wrapped in
<untrusted-content source="workday">envelopes so the model treats them as data, not instructions; keys inside vendor-shaped sub-objects are enveloped too.idandhrefstay raw so they can be passed back into later tool calls. - Strict pagination.
limitmust be an integer 1-100 andoffseta non-negative integer; out-of-range or fractional values are rejected rather than silently clamped.worker_idarguments must be non-blank. - Bounded errors & no redirect following. API and token errors return connector-authored messages (never raw vendor error bodies), and HTTP redirects are refused rather than followed, so credentials can never be replayed to a redirect target. The configured host is validated against loopback/private ranges (including non-canonical IP spellings and IPv6 forms) and re-resolved via DNS before credentials are sent.
- ISU security domains. Workday gates each REST family behind Integration System User domain permissions; a 403 from
list_workday_time_off,list_workday_job_requisitions, orlist_workday_jobsmeans the ISU's security group needs the corresponding domain (Absence Management, Recruiting, Payroll).
Licence
FSL-1.1-MIT — Functional Source License, Version 1.1, with MIT future licence. The software converts to MIT licence on 2030-04-08.
Workday MCP questions
How do I add Workday MCP to Claude Code?
Run claude mcp add --env 'WORKDAY_CLIENT_SECRET=<YOUR_WORKDAY_CLIENT_SECRET>' --env 'WORKDAY_CLIENT_ID=<WORKDAY_CLIENT_ID>' --env 'WORKDAY_HOST=<WORKDAY_HOST>' --env 'WORKDAY_TENANT=<WORKDAY_TENANT>' --env 'WORKDAY_REFRESH_TOKEN=<YOUR_WORKDAY_REFRESH_TOKEN>' mcp-server-workday -- npx -y @mindstone/mcp-server-workday in your terminal. Add --scope user to make it available in every project.
How do I add Workday MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What tools does Workday MCP provide?
It exposes 9 tools, including configure_workday_credentials, list_workday_workers, get_workday_worker, list_workday_organizations, list_workday_locations.
What authentication does this server use?
The server uses OAuth 2.0 authentication, specifically supporting the refresh_token grant if a token is provided.
How does the worker search function work?
Search is performed client-side by paging through workers and filtering locally, scanning a maximum of 1000 workers.
What should I do if I get a 403 error when accessing time off or recruiting tools?
A 403 error indicates that the Integration System User (ISU) needs additional domain permissions, such as Absence Management or Recruiting.