Workday API facts that shape an MCP server
| Fact | Detail | Source |
|---|---|---|
| Official MCP tools | Workday’s press release of October 13, 2026, issued at Workday Rising, says Agent-Ready Tools are Workday’s Model Context Protocol (MCP) tools and that Agent-Ready Tools, Custom Agents and Developer Agent are generally available in Workday Extend AI. It says every agent works under the same Workday permissions, approvals and audit trails. | Workday press release: Trusted Agent Platform delivers headless access to HR and finance (October 13, 2026) |
| Tool catalog | Workday’s launch post says more than 400 pre-built Agent-Ready Tools were available on October 13, 2026, with new tools released every month. It says Workday security permissions are enforced on every call, business rules apply automatically, and every action is traceable to the person who started it. | Workday blog: Workday Extend AI is now agent-ready (October 13, 2026) |
| Endpoint, sign-in and limits | An agent connects to one endpoint per tenant, https://{agentGatewayRegionEndpoint}/{tenantName}/mcp, and authenticates only with OAuth 2.1 and PKCE. Calls use an Agent System User (ASU) token, and in delegate mode the agent’s permissions are never elevated beyond those of the user it acts for. Workday lists a concurrent request limit of 2,000 and rate limiting with a refresh rate of 500 requests and a burst limit of 500, without giving the time window. | Workday Developer Site: Agent-Ready MCP Tools |
| Setup and license | Workday’s setup guide says connecting an external agent to Workday MCP is for Extend Professionals only. The steps are to set up Agent System of Record (ASOR), register and configure the agent, set security policies for its skills, then sign in for a token; access tokens expire after 4 hours. Customers on Workday’s UMSA have the feature automatically, and customers on the MSA must enable it through Innovation Services. | Workday Developer Site: Connect an External Agent with Workday MCP |
| Metering | Workday’s Flex Credits Rate Card (last updated November 5, 2026) meters Agent-Ready Tool calls under Extend AI. Per 100 base calls (data retrieval and inquiry) it lists 5 Flex Credits when used by Custom Agents and 10 when used by other agents; per 100 advanced calls (transactional or administrative tasks), 25 and 50. Standard API calls are listed at 60 Flex Credits per 10,000 calls. | Workday Flex Credits Rate Card (PDF, last updated November 5, 2026) |
| Change policy | Workday’s change policy (dated September 2026) says the tools are for AI agents only and prohibits using them to build hard-coded applications or standard integrations. Tool names, schemas and descriptions change without notice, and the MCP server supports specification versions 2024-11-05, 2025-03-26, 2025-06-18 and 2025-11-25. | Workday Developer Site: Agent-Ready MCP Tools developer guidelines and change policy |
| Clients Workday names | Workday’s product page for the tools says "Connect Workday to Gemini, Copilot, or ChatGPT in hours, not weeks" and lists tools across Core HR, Financials, Workforce Management, Talent and Learning, Payroll, Recruiting and Student. It adds that Workday’s existing REST, SOAP, GraphQL and RaaS catalog remains the standard for system-to-system integrations. | Workday: Agent-Ready Tools and MCP |
| Claude | Workday and Anthropic announced a partnership on October 13, 2026. The release says the Sana in Claude plugin is available to early access customers, with general availability expected in late 2026, and that Agent-Ready Tools will be available through the plugin later in 2026. It also says Workday’s permissions and business rules apply to every request and the user confirms every change. | Workday newsroom: Workday and Anthropic announce new partnership (October 13, 2026) |
| Microsoft Copilot | On November 17, 2026, at Workday Rising EMEA, Workday said the Sana MCP plugin for Microsoft Copilot is available in early access, with general availability expected in early 2027. Workday says everything done in Copilot follows the company’s existing Workday permissions and every action is audited. | Workday blog: Sana is now available in Microsoft Copilot in early access (November 17, 2026) |
| MCP Registry | As of November 18, 2026, a search of the official MCP Registry for "workday" returns no server published by Workday. The results are careers-site scrapers, business-day calculators and two community packages, io.github.chrischall/workday-mcp (read-only, through the user’s signed-in session) and io.github.mindstone/mcp-server-workday. | Official MCP Registry: search for workday |
| APIs behind the gateway | Workday’s administrator guide (November 12, 2026) says all third-party agents interacting with Workday APIs must route their traffic through Agent Gateway using Agent System User security. The gateway carries all public REST and SOAP operations, the Graph API, Workday Query Language (WQL) and RaaS, on regional endpoints for the US, EU, UK, Canada, Australia, Singapore, India and Japan. | Workday Administrator Guide: Workday AI (PDF, November 12, 2026) |
| Integration users | An Integration System User (ISU) is a Workday account that apps use to access data as a system user. It is added to an Integration System Security Group (Unconstrained), which needs View and Modify access for the REST APIs called and Get and Put access for SOAP APIs. | Workday Developer Site: Create Integration System Users for Apps |
| Releases | Workday delivers two major releases a year, R1 in March and R2 in September, plus weekly service updates. Features reach Preview tenants before Production, and Workday publishes release notes on Wednesdays and Fridays. | Workday Administrator Guide: About Workday Documentation (PDF, November 12, 2026) |
Every way to connect Workday to AI
| Option | Type | Fits when | Limits |
|---|---|---|---|
| Workday Agent-Ready Tools (Workday Extend AI) | Official | Workday customers with Extend AI whose agents run in Claude, Copilot Studio, ChatGPT or their own stack: more than 400 MCP tools that read and transact in HR and finance, with each call checked against the user’s Workday security and business rules and recorded against both the agent and the person. | Needs Extend AI, Agent System of Record setup and, per Workday’s guide, an Extend Professional to connect the agent. Calls consume Flex Credits, the tools are unversioned and can be renamed without notice, and Workday’s public pages give no price for Extend AI or for a Flex Credit. |
| Sana from Workday in Claude and Microsoft Copilot | Official | Employees who want Workday answers and actions inside the assistant they already use: checking pay or time off, finding policy answers, submitting expenses and handling approvals, carried out by Workday’s Sana agents under the roles, approval chains and audit controls configured in Workday. | As of November 2026 the Claude connector is a beta that Workday admins apply for, and it needs an active UMSA and Workday agents configured in the Agent Management Hub. Its four listed tools send queries and actions to Workday’s plugin. The Sana MCP plugin for Copilot is in early access, with general availability expected in early 2027. |
| Zapier Workday MCP | Hosted | Teams already on Zapier that want a few chosen Workday actions available in Claude, Cursor or another MCP client without building anything. You select and scope the actions the assistant may use. | The actions shown first are transactions such as Hire Employee, Change Job, Create Position, Approve Task and Create Supplier Credit Memo, so choose carefully. One MCP tool call uses 2 tasks from your Zapier plan, and Zapier says its MCP doesn’t support Enterprise app and action restrictions out of the box. |
| Composio Workday MCP | Hosted | Developers building their own agent who want managed OAuth 2.0 sign-in and a wide catalog: Composio listed 588 Workday tools and 13 triggers on November 18, 2026, built on Workday’s REST services and SOAP operations. | The catalog includes creating, updating and deleting payroll inputs, reading pay slips and federal W-4 elections, and requesting one-time payments, so restrict tools before connecting an assistant. Requests pass through Composio, and previews and confirmations are yours to add. |
| Unified.to (Unified MCP) | Hosted | Software vendors that need real-time, pass-through Workday access for their own product or agent, next to other HR systems. Its Workday integration reads and writes, signs in with OAuth 2.0 or an API key, and covers objects such as employees, groups, jobs, time off, candidates, invoices and expense reports. | The unified model covers common objects; custom objects go through raw fields and a Passthrough API. Supported objects include earnings, so use its options to limit permissions and hide sensitive fields. Usage-based pricing, with a 30-day free trial. |
| Custom Workday MCP server | Custom | A small set of business-specific, payroll-safe tools on reviewed custom reports (RaaS), WQL and the REST and SOAP APIs, registered in Agent System of Record so each call runs for the signed-in person, with writes that start Workday business processes and workflows that span Workday and other systems, hosted in your cloud. | You own hosting, security group design, evaluation and retesting after each Workday release. Workday routes third-party agents’ API traffic through Agent Gateway, and its rate card lists standard API calls at 60 Flex Credits per 10,000, so check how your agreement treats that traffic first. |
Tools a Workday MCP server should expose
Start with read-only tools and add write actions once the team trusts the answers. Every write action below runs with a confirmation or approval step.
| Tool | Access | Risk | Purpose | Guard |
|---|---|---|---|---|
find_worker | Read | Medium | Look up a worker’s name, business title, supervisory organization, manager, location and status. | Runs for the signed-in user in delegate mode; allowlisted fields only, never national IDs, birth date, home address, bank details or compensation. |
get_supervisory_org | Read | Low | A supervisory organization with its place in the org chart and its member count, from the Staffing REST API. | Read-only; returns structure and counts, and member names only where the caller’s Workday security allows. |
get_time_off_balances | Read | Medium | Absence plan balances and approved upcoming time off for a worker or a team, from the Absence Management REST API. | Limited to the caller’s own record, their direct reports or their HR population; leave reasons are never returned. |
list_open_positions | Read | Low | Open and unfilled positions by supervisory organization, job profile or location. | Read-only through a reviewed custom report; returns position, job profile and location, with no compensation ranges. |
run_headcount_report | Read | Medium | Run one of a curated set of custom reports enabled as web services (RaaS), such as headcount by organization or turnover by quarter. | Allowlist of reports approved for AI use; prompts validated; aggregates only, with groups below a minimum size hidden; results capped and paged. |
get_expense_report_status | Read | Low | Status and total of the caller’s expense reports, from the Expense REST API. | Limited to the caller’s own reports or those awaiting their action; no payment elections or bank details. |
list_supplier_invoices | Read | Medium | Supplier invoices by supplier, status or due date, with amounts and payment status. | Finance role required; allowlisted fields from a reviewed report, with no supplier bank or settlement account details; results capped and paged. |
request_time_off | Write | Medium | Submit a time off request for the signed-in worker through the Absence Management REST API. | Workers file only for themselves and confirm the dates and time off type first; the request then follows the normal Workday approval chain. |
submit_supplier_invoice_request | Write | High | Create a supplier invoice request from a reviewed document and submit it, through the Accounts Payable REST API. | Preview of supplier, amount and lines, then confirmation by a user whose Workday role may create supplier invoice requests; Workday’s business process routes the approval; a duplicate check on supplier and invoice number runs before submitting. |
Connect Workday to Claude, ChatGPT or Copilot Studio
Claude
Workday offers two routes into Claude. The Sana from Workday connector in Claude’s directory (made by Workday, added October 2026) is a beta that Workday admins apply for; it brings Workday’s agents into Claude and needs an active UMSA and agents configured in the Agent Management Hub. For your own agent, Workday’s documentation lists Claude among the external platforms that can call Agent-Ready MCP Tools once the agent is registered in Agent System of Record; the guide shows a Cursor example and refers you to each platform’s own MCP documentation for the rest. A hosted or custom server is added as a custom connector; on Team and Enterprise plans an Owner adds it first, and with a per-user OAuth server each person then signs in with their own Workday account. Calls come from Anthropic’s cloud, so a private server must allowlist Anthropic’s IP ranges, and claude.ai and Claude Desktop cap tool results at about 150,000 characters, so keep report and WQL results paged.
ChatGPT
Workday’s Agent-Ready Tools page names ChatGPT ("Connect Workday to Gemini, Copilot, or ChatGPT in hours, not weeks"), and its June 2026 post lists ChatGPT among the clients the tools reach natively over MCP. Workday hasn’t published a ChatGPT setup guide or announced a Sana app for ChatGPT: its October 2026 release on bringing Sana into other tools names Claude, Gemini Enterprise, Microsoft Copilot, Teams and Slack. Workday’s change policy also warns that some MCP clients may not be compatible with its server, so test first. For a custom server, use developer mode (Pro, Plus, Business, Enterprise and Education on the web; on Enterprise and Education an admin grants access) and add the server under ChatGPT Plugins over Streamable HTTP with OAuth. ChatGPT asks for confirmation on tools without a readOnlyHint, so mark reads read-only and let writes ask.
Microsoft Copilot Studio
Workday’s documentation names Microsoft Copilot Studio among the platforms that connect to its MCP endpoint with the agent’s OAuth credentials, and its Microsoft Agent Sync brings agents built in Copilot Studio and Azure AI Foundry into Agent System of Record. In Copilot Studio, add a server with the MCP onboarding wizard on the agent’s Tools page (Streamable HTTP only; OAuth 2.0, API key or none) and turn on generative orchestration; Power Platform data policies govern the connection. For employees, Workday’s Sana Self-Service Agent has been in Microsoft 365 Copilot since May 13, 2026, and the Sana MCP plugin for Copilot entered early access on November 17, 2026. Microsoft also publishes a premium Workday connector that runs RaaS reports and SOAP operations, throttled at 200 calls per connection per 60 seconds.
Claude implementation · Copilot implementation · ChatGPT implementation
Permissions, identity and audit
- Agent skills run in one of two modes. In delegate mode the agent acts for a signed-in person and Workday authorizes each call against both that person’s permissions and the skills the agent is allowed; in ambient mode the agent acts as itself under its own Ambient Agent Security Group. Use delegate mode for anything a person asks for.
- Each delegate skill is made available to named security groups in the Agent Management Hub, and a person must be in a group on the skill and also hold the domain or business process security for the tool behind it. Check each skill with the View Security for Agent Skill report before activating the agent.
- Delegate-mode actions are recorded with the agent as By User and the person as On Behalf Of User. Review the View AI Agent User Audit Trail report with HR and finance on a schedule.
- Avoid the pattern Workday itself warns about: a custom server on a single over-permissioned service account. If a background job must use an Integration System User, give it its own Integration System Security Group with only the domains the tools need, and have the server check the caller’s role before returning anything.
- Expose only reviewed custom reports and WQL queries as tools. Both return what the calling account’s security allows, so a broadly permissioned integration account returns broad data.
- Keep national IDs, bank and payment election details, compensation and full payslips out of every tool response unless a tool is built for an authorized role with its own guard. Keep write tools off until each has a preview, a confirmation and a Workday business process behind it.
Hosting and network
- Workday hosts the Agent-Ready Tools: agents call the Agent Gateway endpoint for the tenant’s region (US, EU, UK, Canada, Australia, Singapore, India or Japan) with the tenant alias, so the official route has no server for you to run. A custom MCP server runs in your AWS or Azure account, or with a hosted provider, and calls Workday through the same gateway.
- Claude, ChatGPT and Copilot Studio connect from their own clouds, so publish a custom server over HTTPS behind OAuth, or use ChatGPT’s Secure MCP Tunnel for a private deployment.
- Plan for change on both sides. Workday updates the MCP tool list weekly on Tuesdays without versioning, and ships weekly service updates and major releases in March and September, so keep prompts free of hard-coded tool names and retest every tool in a non-production tenant; Implementation and Sandbox tenants are refreshed from Production.
- Page and bound every read. WQL returns at most 1 million rows, 10,000 per page, with a 5-minute timeout through Workday’s API gateway and 30 minutes on a tenanted host. Cache reference data such as organizations and job profiles, and stay inside the published limits for Agent-Ready Tool calls.
Cost and timeline
- Workday prices the official route by usage. Its rate card of November 5, 2026 lists Agent-Ready Tool calls from agents other than Custom Agents at 10 Flex Credits per 100 read calls and 50 per 100 transactional calls (5 and 25 from Custom Agents). Workday’s public pages give no price for a Flex Credit or for Extend AI, so ask your account team.
- Agent System of Record needs no extra SKU; Workday says it is included in the core subscription. Workday also offers annual Complimentary Flex Credits based on company size and says most agents can be tested free in non-production.
- A focused read-only custom Workday MCP server, built on reviewed custom reports, WQL and the REST API, typically takes two to four weeks including security and evaluation, once the security groups and agent registration are in place. A prototype can start on a development tenant with sample data from Workday’s open Developer Program (beta).
- Write tools that start Workday business processes, and workflows across Workday and other systems, are scoped after a short discovery. Hosted platforms add their own fees: Zapier counts 2 tasks per MCP tool call, and Unified.to has usage-based pricing with a 30-day free trial.
Workday MCP questions
Does Workday have an MCP server?
Yes. Workday’s MCP offering is called Agent-Ready Tools, and Workday announced it as generally available in Workday Extend AI on October 13, 2026 at Workday Rising. As of November 2026 it has more than 400 tools across HR, finance, payroll and recruiting, served from one endpoint per tenant on Workday’s Agent Gateway, with every call checked against Workday security and recorded. Workday publishes nothing in the official MCP Registry; an agent is registered in the tenant’s Agent System of Record instead.
How do I connect Claude to Workday?
Three ways. Workday’s own Sana from Workday connector is in Claude’s connectors directory as a beta: a Workday admin applies for access, and it needs a UMSA and Workday agents configured in the Agent Management Hub. For your own agent, register it in Agent System of Record, choose its tools and connect to the tenant’s MCP endpoint with OAuth; Workday’s documentation lists Claude among the external platforms that can call the tools. Without Extend AI, add a hosted or custom Workday MCP server to Claude as a custom connector, with each person signing in under their own Workday account.
What license do Workday’s Agent-Ready Tools need?
Workday Extend AI. Workday’s announcements say the tools are generally available to all customers through Extend AI, and its setup guide says connecting an external agent is for Extend Professionals only. Calls are metered in Flex Credits (on the November 5, 2026 rate card, 10 credits per 100 read calls and 50 per 100 transactional calls for agents other than Custom Agents), and customers on the MSA rather than the UMSA must first enable the feature through Innovation Services. Agent System of Record itself needs no additional SKU. Workday doesn’t publish prices for Extend AI or Flex Credits, so confirm the exact SKU and cost with your account team.
Does it work with ChatGPT and Microsoft Copilot?
Workday says so for both. Its Agent-Ready Tools page names Gemini, Copilot and ChatGPT, and its documentation names Microsoft Copilot Studio as a platform that connects to the MCP endpoint, while warning that some MCP clients may not be compatible. Copilot has more: the Sana Self-Service Agent has been in Microsoft 365 Copilot since May 2026, and the Sana MCP plugin for Copilot entered early access on November 17, 2026. Workday hasn’t announced a Sana app for ChatGPT or published a ChatGPT setup guide, so test the connection in developer mode first.
How are payroll and personal data protected?
On the official route, by Workday’s own security: in delegate mode each call is authorized against both the person’s permissions and the agent’s allowed skills, down to field level, and the audit trail records the agent and the person. Workday’s Copilot plugin, for example, can return a person’s own payslip or tax form on request, so decide which skills each security group gets. On a custom server we go further by design: tools return allowlisted fields only, never national IDs, bank details or compensation without a role check and an explicit guard, aggregates hide small groups, and logs record who asked for what without storing the answers.
Can an AI agent change data in Workday?
Yes. Workday’s catalog separates Basic tools, which are read-only, from Advanced tools, which write, and some write tools need Prompt tools that supply valid values first. Workday says business rules apply automatically: in its own example, a manager who approves time off in Copilot has the approval validated against company policy and audited. In a custom server we add a preview and an explicit confirmation before any write, and leave the approval to the Workday business process.
What if we don’t have Workday Extend AI?
Then the choices are a hosted platform or a custom server on Workday’s APIs. Zapier, Composio, Unified.to and CData Connect AI each have a Workday MCP offer; some catalogs include payroll input, hiring or job change actions, so restrict tools before anyone connects an assistant. A custom server uses reviewed custom reports (RaaS), WQL and the REST and SOAP APIs. Workday’s administrator guide says third-party agents must reach those APIs through Agent Gateway after registration in Agent System of Record, which needs no extra SKU, so ask any vendor how its connection is registered.
Should we use Workday’s tools or build our own?
Use Workday’s tools if you have Extend AI and the questions and actions stay inside Workday: they already enforce your security groups, business processes and audit trail, and a custom server would only repeat that work. Sana in Claude or Copilot is enough if employees mainly need self-service. Build when you need tools that span Workday and other systems, a narrow payroll-safe tool set for a specific audience, tool contracts that don’t change week to week, or you don’t have Extend AI. AIONDATA is independent and not a Workday partner, so we will tell you when the official tools are the better choice.
