Workday

GitHub Actions

Workday MCP server for Claude — developed and maintained by AI (Claude Code)

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "workday-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ]9    }10  }11}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add workday-mcp -- npx -y workday-mcp@1.1.10

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "workday-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.1.10
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Workday?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Workday need an API key?

No required environment variable is listed on this record.

What transport does Workday use?

Workday runs locally over stdio.

When was Workday last checked?

Last checked 2026-10-28. Workday MCP server for Claude — developed and maintained by AI (Claude Code)

From the publisher

Documentation

workday-mcp

Read-only MCP server for Workday. Reads your Workday org chart, worker profiles, pay, benefits, performance, and any task or data card, and returns them as structured JSON. Every request routes through your own signed-in *.myworkday.com tab via the ContextMint Bridge browser extension, reusing your existing SSO-authenticated session.

⚠️ Workday gives employees no personal API. This server reads the same internal *.htmld endpoints the Workday web app calls, dispatched through your own signed-in browser tab. It is read-only and touches only your own data. Check your employer's acceptable-use policy. Use at your own discretion.

🤖 This project was developed and is maintained by AI (Claude Code).

Why a bridge instead of the official API?

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.

Install

See SKILL.md for full setup. In brief:

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

Then install ContextMint Bridge from its releases page (Chrome: unzip the chrome zip and load it unpacked in chrome://extensions; Safari is not available yet — it will ship inside the ContextMint app, which has no public download link, so use Chrome for now) and sign into Workday in your browser.

ContextMint Bridge is the fetchproxy browser extension under its new name, from the same maintainer — fetchproxy's own README points to it. Its source is public at https://github.com/nullnet-app/contextmint-bridge: build it yourself, or check a release zip against the .sha256 file published beside it (shasum -a 256 -c contextmint-bridge-chrome-<version>.zip.sha256).

Tools

Tool	What it does
`workday_get_apps`	List your Workday apps with launchable task ids — the discovery entry point
`workday_open_app`	Open an app by name ("Talent and Performance", "Absence") and follow it down to the child cards holding its real content
`workday_get_task`	Read any task/data card by id or path → fields, full table rows, references, related tasks, export links. `expand: true` crawls hub pages
`workday_get_org_chart`	Your reporting chain — each person with title, location, report count, and a `profileUri` to drill into
`workday_get_worker`	A worker's profile: the catalog of everything readable about them (9 sections, ~40 named tasks)
`workday_get_worker_task`	Open one named item from that catalog — "Compensation", "Performance Reviews", "Management Chain"
`workday_get_my_profile`	The same catalog, for yourself
`workday_fetch`	Raw `.htmld` read with secrets redacted — the escape hatch for pages the parser doesn't model yet
`workday_graphql`	Read-only GraphQL against Workday's PEX surface (mutations refused). The only route to Inbox / search
`workday_healthcheck`	Verify the bridge + session end-to-end with an actionable hint

The parser understands seven Workday page families — data cards, grids (real tables, with chunking and export links), form-style detail pages, worker profiles, org charts, app hubs, and report prompt forms — and labels each page with its kind. See docs/WORKDAY-API.md.

Manager quick start

workday_get_org_chart                                   → who reports where, with profileUris
workday_get_worker         { worker: "<profileUri>" }   → that person's full catalog
workday_get_worker_task    { worker: "…", task: "Compensation" }
workday_open_app           { app: "talent" }            → a whole app hub, crawled

All ids are discovered at runtime from your own app menu and org chart — nothing tenant-specific is hardcoded, so this works on any Workday tenant.

Development

npm install
npm test          # vitest
npm run build     # tsc --noEmit + esbuild bundle → dist/bundle.js

The widget-tree parser (src/parse.ts) is the durable core; see docs/WORKDAY-API.md for the captured endpoint shapes and schema. License: MIT.

Workday

GitHub Actions

Workday MCP server for Claude — developed and maintained by AI (Claude Code)

Devops Developer Tools

Add to Cursor Add to VS Code Run on PlugMCP

GitHub npm Website

Add to Cursor Add to VS Code Run on PlugMCP

1{2  "mcpServers": {3    "workday-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ]9    }10  }11}

.cursor/mcp.jsonMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

npx -y [email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add workday-mcp -- npx -y workday-mcp@1.1.10

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "workday-mcp": {4      "command": "npx",5      "args": [6        "-y",7        "[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.1.10
Last checked: 2026-10-28

Stars: —
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Workday?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Workday need an API key?

No required environment variable is listed on this record.

What transport does Workday use?

Workday runs locally over stdio.

When was Workday last checked?

Last checked 2026-10-28. Workday MCP server for Claude — developed and maintained by AI (Claude Code)

From the publisher

Documentation

workday-mcp

⚠️ Workday gives employees no personal API. This server reads the same internal *.htmld endpoints the Workday web app calls, dispatched through your own signed-in browser tab. It is read-only and touches only your own data. Check your employer's acceptable-use policy. Use at your own discretion.

🤖 This project was developed and is maintained by AI (Claude Code).

Why a bridge instead of the official API?

Install

See SKILL.md for full setup. In brief:

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

Tools

Tool	What it does
`workday_get_apps`	List your Workday apps with launchable task ids — the discovery entry point
`workday_open_app`	Open an app by name ("Talent and Performance", "Absence") and follow it down to the child cards holding its real content
`workday_get_task`	Read any task/data card by id or path → fields, full table rows, references, related tasks, export links. `expand: true` crawls hub pages
`workday_get_org_chart`	Your reporting chain — each person with title, location, report count, and a `profileUri` to drill into
`workday_get_worker`	A worker's profile: the catalog of everything readable about them (9 sections, ~40 named tasks)
`workday_get_worker_task`	Open one named item from that catalog — "Compensation", "Performance Reviews", "Management Chain"
`workday_get_my_profile`	The same catalog, for yourself
`workday_fetch`	Raw `.htmld` read with secrets redacted — the escape hatch for pages the parser doesn't model yet
`workday_graphql`	Read-only GraphQL against Workday's PEX surface (mutations refused). The only route to Inbox / search
`workday_healthcheck`	Verify the bridge + session end-to-end with an actionable hint

Manager quick start

workday_get_org_chart                                   → who reports where, with profileUris
workday_get_worker         { worker: "<profileUri>" }   → that person's full catalog
workday_get_worker_task    { worker: "…", task: "Compensation" }
workday_open_app           { app: "talent" }            → a whole app hub, crawled

All ids are discovered at runtime from your own app menu and org chart — nothing tenant-specific is hardcoded, so this works on any Workday tenant.

Development

npm install
npm test          # vitest
npm run build     # tsc --noEmit + esbuild bundle → dist/bundle.js

The widget-tree parser (src/parse.ts) is the durable core; see docs/WORKDAY-API.md for the captured endpoint shapes and schema. License: MIT.