MCP connectorsWorkday

Workday MCP: connect Workday to Claude and ChatGPT

Ask Claude or ChatGPT who is off next week, how many holiday days you have left or what the headcount looks like in a department. The answer comes straight from Workday.

Each person signs in with their own Workday account, so Workday’s own security decides what the AI may read for that person, and it only reads. HR data stays with the people who are allowed to see it. We set it up for your company next to your other systems.

Built for your company · Works in Claude, ChatGPT and Copilot

In practice

What your team can do with Workday in Claude and ChatGPT

Managers

Your team without opening Workday

Who reports to you, who is away and when, and what time off is waiting, in one answer.
HR

Answers for the questions that keep coming

Org structure, managers and time off across the departments HR may see, summarised the way you ask.
Every employee

Your own details, quickly

Your time off balance, your manager and your job details, without searching through menus.
Management and finance

Headcount before the meeting

Headcount per organisation and open positions, put into plain language before the planning meeting.
Examples

Ask it like this

  • “Who on my team is off next week?”

  • “How many holiday days do I have left this year?”

  • “Who reports to Karin Lund, and what are their job titles?”

  • “What is the headcount in the Gothenburg warehouse organisation compared with January?”

  • “Which positions are open in Customer Service right now?”

  • “Summarise the time off my team has booked for December.”

  • “Draft a welcome message to the two people joining my team in November. I will send it myself.”

The connector

What we build for Workday

Deployed OS has no ready Workday connector yet. We build it for your company when you start, on Workday’s own API, with the same rules as every other connector: each person’s own login, access decided by group, every call logged.

Workers and organisations
Workers, job titles, managers and supervisory organisations, as the person may see them in Workday.
Time off
Time off balances and booked or requested time off, for the person and for the teams they may see.
Headcount and positions
Headcount per organisation and open positions, for the people whose role allows it.
Your own details
The person’s own job, manager and time off, which every employee can ask about.
Security

Who sees what

Read-only
The connector reads. It does not approve time off, change a worker or start a business process.
Each person’s own Workday login
Everyone signs in to Workday as themselves, and Workday’s security groups and policies apply to every call. The AI sees what the person could see in Workday, no more.
Personal data only for those allowed
Pay, contact details and other sensitive HR data only show up for people Workday already lets see them. A colleague asking about someone else gets what Workday would show them.
Your company decides who gets it
Admins choose which groups get Workday in Deployed OS. A group without access never sees the connector.
Every call logged
Who asked, what was read and when. Deployed OS keeps the log, and it can be exported.
Setup

Set up the Workday connector in three steps

01
Your Workday admin registers an API client in your tenant with the authorization code grant and only the functional areas the connector needs. Your company owns the client, not us.
02
We set up the connector for your Workday tenant, and you choose which groups get it in Deployed OS.
03
Each person connects with their own Workday sign-in. From then on they just ask.
Compared

Workday’s own MCP server or Deployed OS?

Workday has its own MCP tools, called Agent-Ready Tools, generally available as part of Workday Extend AI since Workday Rising in October 2026. Workday says every call runs under the user’s Workday permissions, approvals and audit trail. Your Workday admin registers each outside agent in the Agent System of Record and sets up OAuth credentials, and Workday’s documentation describes it as a feature for Extend Professional customers, so check your subscription. If Workday is the only system your team wants in its AI tool, it is a good fit.

Deployed OS is for when Workday is one system among several. It sits next to your CRM, Microsoft 365 and other tools in one company connection, admins decide which groups get each system, every call is logged in one place, and the same rules apply in Claude and ChatGPT, next to your company’s skills and guardrails.

Their documentation: Workday Agent-Ready Tools (MCP)

Questions

Workday MCP: common questions

Yes. Workday’s Agent-Ready Tools are its own MCP tools, generally available as part of Workday Extend AI since October 2026, and they run under the user’s Workday permissions. Deployed OS adds Workday to one company connection with your other systems, with access per group and one log.

No. The connector we build reads workers, organisations, time off, headcount and open positions. It does not approve requests, change records or start business processes.

Yes. Everyone signs in with their own Workday account, and Workday applies that person’s security groups to every call. The AI cannot see more than the person could in Workday.

It follows Workday’s security. If someone may not see a colleague’s pay or personal details in Workday, they will not get it through the AI either. Admins also decide which groups get the connector at all.

Deployed is an EU company and fully GDPR compliant, and you choose where your data is stored, down to the city. Workday data is fetched when someone asks for it.

It depends on the size of your team. Get in touch and we will walk you through it.

More connectorsAll connectors
Let’s talk

See it on your own tools.

Tell us which systems your company runs on. We’ll show you what your team can ask, and what IT gets to control.