Connect Workday to Claude Code

Have Claude initiate requests and update worker records in Workday. From the terminal, inside the sessions where you already work.

Build my connector Talk to us

How do you connect Workday to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Workday, you add a Workday MCP server: a small hosted service that exposes Workday's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own Workday account. No API keys pasted into config files.

claude mcp add --transport http workday https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in Workday once connected?

Full read-write Workday access lets Claude initiate a time-off request, advance or approve a business-process step, update worker contact or job details, and act on inbox tasks, all once you approve. The HR admin work that used to mean clicking through screens happens where the data already lives.

Initiate a time-off or leave-of-absence request for a worker
Advance, approve, or send back a business-process step in your Workday inbox
Update worker contact, address, or job-detail fields
Start an onboarding or job-change request and route it to the right approver
Look up a balance or org record, then draft the matching change for review

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same Workday access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the Workday API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Workday changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build Workday connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same Workday connector work in claude.ai and Claude Code?

Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own Workday account, so access always matches what that person can already see and do.

Do I need to host or maintain anything myself?

No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on Workday's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.

Is it safe to give a coding agent write access to Workday?

Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the Workday account it signs in with. Revoking access is one click in Workday.

More on the Workday connector

Workday connector for claude.ai BambooHR + Claude Code Gusto + Claude Code Rippling + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connector Talk to us