Workday MCP: What HR Leaders Need to Know

Workday supports MCP through several products and access paths. Before choosing a connector, establish which Workday data or action you need, which product exposes it, and who is allowed to use it.

This guide separates Workday's published availability from third-party connectors and explains where Doozy fits if your goal is onboarding and training in Slack.

Where Workday stands on MCP

Workday's June 2, 2026 announcement says its Agent-Ready Tools provide access to HR and finance data over MCP. At that announcement, Agent-Ready Tools and Developer Agent were available to early-access customers through Workday Extend Professional. General availability was projected for the second half of 2026.

Workday also states that its Agent System of Record (ASOR) is generally available. ASOR provides governance and visibility for agents. Its availability does not mean every MCP tool is available in every customer tenant.

For an evaluation, ask your Workday account team to confirm access to the specific tools you need, the required subscription, supported regions, and tenant configuration. A projected launch date is not confirmation that your account has access.

What MCP lets an agent do

The Model Context Protocol provides a standard way for an AI application to discover and call tools. Those tools can retrieve information or take actions. For Workday, an implementation might expose a worker lookup, a balance query, or a business-process action.

The available actions depend on the server, permissions, and client. MCP does not by itself supply a complete onboarding program, delivery schedule, or reporting process. An agent can participate in those workflows when the appropriate tools and controls are configured.

Workday tools and third-party connectors

There are two routes to investigate:

Workday's own agent tools. Start here if your organization wants to use Workday's published agent capabilities and governance. Workday describes Agent-Ready Tools as inheriting its security and delegation model, business-process controls, and audit trail. Confirm how that applies to your intended actions and tenant.

Third-party connectors. These expose selected Workday capabilities to an MCP client through a provider's integration. Zapier, CData, and Knit publish Workday MCP offerings. Compare the actual tools, authentication model, and supported operations; sharing a protocol does not make the connectors interchangeable.

Ask each provider to demonstrate your required action with the permissions you intend to grant. A connector listing alone does not establish that every Workday module, field, or workflow is supported.

Questions for your IT and HR systems teams

Whose permissions does the agent use?

Find out whether calls run as the requesting user, a service account, or another delegated identity. Check the fields and actions that identity can access. Test with a restricted user as well as an administrator.

Which employee data reaches the AI application?

Identify what the connector reads, what the model receives, and where requests and responses are retained. Scope the integration to the information needed for the use case. Check the provider's documentation for field filtering, redaction, retention, and regional processing.

What happens before an agent changes a record?

Separate read access from write access. For actions such as updating employee information or submitting a request, establish which approvals apply and how errors are handled. Ask the provider to show the process from the user's request through the final Workday action.

Can you trace an action back to its requester?

Review the logs available in the AI application, connector, and Workday. Confirm which record identifies the requester, tool call, time, result, and any approval. Do not assume that one provider's logging covers the whole chain.

Where Doozy fits

If your immediate job is to query or update Workday records through an AI assistant, evaluate the relevant MCP tools against that job.

If your job is to run new-hire onboarding in Slack, Doozy's Workday integration supplies employee information for the programs you configure. For example:

1. Use a new hire's start date to enroll them in an onboarding track.
2. Schedule welcome messages, manager tasks, and introductions across their first weeks.
3. Include training and knowledge checks at the appropriate points.
4. Review progress and quiz results to identify follow-up work.

You choose the audience, content, and timing. Employee-based targeting depends on the information available from the connection, and Slack activities wait until the participant has joined Slack.

For routine employee tasks such as time-off requests, also review the native Workday Slack integration. That is a separate evaluation from choosing an MCP connector or an onboarding program.

A practical starting point

Write down one task and the access it requires. Ask the vendor to demonstrate that task, its permissions, and its reporting before expanding access.

For onboarding delivery, start with one role and one reusable first-month plan. The Workday integration page explains how Doozy uses the employee information you already maintain.