Workday MCP Server

Read-only Workday for Claude — fetch tasks, pay, benefits via your signed-in session

Local serverstdio

What is the Workday MCP server?

Read-only Workday for Claude — fetch tasks, pay, benefits via your signed-in session. The workday mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 3 defined tools rather than through you.

What it actually does

The official Workday REST/SOAP API requires a tenant administrator to register an OAuth API client + Integration System User — an employee can't self-provision it. Tenants also sit behind corporate SSO (Ping/Okta/Entra) with MFA, so there's no server-side login. The only surface an employee can reach for their own data is their live browser session, which is what this server relays.

Its toolset

Everything the assistant can do here goes through one of these:

  • workday_get_apps — List your Workday apps with launchable task ids — the discovery entry point
  • workday_get_task — Read a Workday task/data card by task id or path → title, fields, references, related tasks, export links
  • workday_healthcheck — Verify the bridge + session end-to-end with an actionable hint

Adding it to your client

npm on npm is all you need. Most clients run it directly, so configuration is a few lines and a restart.

Configuration

You will need one environment variable: WORKDAY_TENANT. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

When to reach for it

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Workday's toolset — workday_get_apps, workday_get_task, workday_healthcheck — is a fair guide to whether it matches your workflow. It is maintained by chrischall; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Caveats

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the workday mcp server does with a few real requests.

Available tools

ToolWhat it does
workday_get_appsList your Workday apps with launchable task ids — the discovery entry point
workday_get_taskRead a Workday task/data card by task id or path → title, fields, references, related tasks, export links
workday_healthcheckVerify the bridge + session end-to-end with an actionable hint

How to install the Workday MCP server

{
  "mcpServers": {
    "workday": {
      "command": "npx",
      "args": ["-y", "workday-mcp"],
      "env": { "WORKDAY_TENANT": "your-tenant-slug" }
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Configuration

VariableDescriptionRequired
WORKDAY_TENANTConfiguration value read at startup.Optional

Example prompts to try

  • Use Workday to workday get apps.
  • Use Workday to workday get task.
  • Use Workday to workday healthcheck.

Frequently asked questions

It connects Workday to MCP-compatible AI assistants such as Claude and Cursor, exposing 3 tools (workday_get_apps, workday_get_task, workday_healthcheck) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Workday directly.