# workday-mcp [Health: Active]

**Category:** 🏢 Workplace & Productivity  
**Repository:** https://github.com/chrischall/workday-mcp  
**GitHub Stars:** 1  
**npm Downloads (last month):** 2461  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/workday-mcp

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

## Tools
Capabilities this server exposes over MCP:

- **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

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "workday-mcp": {
    "command": "npx",
    "args": ["-y","workday-mcp"],
    "env": {
      "WORKDAY_TENANT": ""
    }
  }
}
```

**Requires environment variables:** `WORKDAY_TENANT` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What workday-mcp does

The workday-mcp MCP server exposes read-only access to Workday through MCP. It can retrieve organizational reporting chains, worker profile catalogs, compensation and benefits information, performance-related records, app hubs, task cards, tables, references, related tasks, and export links. Results are returned as structured JSON where the parser supports the page type.

The server is intended for data available to the signed-in employee. It does not provide write operations, and the GraphQL tool rejects mutations. The project describes this access as reading the same internal `.htmld` endpoints used by the Workday web application.

This listing belongs to the Workplace & Productivity category and is most relevant when an agent needs to answer questions about an employee’s own Workday data or navigate accessible organizational information.

## How it works

Requests are routed through the ContextMint Bridge browser extension to an active, authenticated Workday tab. The extension reuses the browser session, including corporate SSO and MFA that have already been completed. Workday tenant-specific IDs are discovered at runtime from the user’s app menu and organization chart rather than being embedded in the server.

The parser recognizes data cards, real tables, form-like detail pages, worker profiles, organization charts, app hubs, and report prompt forms. `workday_get_task` can optionally expand hub pages, while `workday_fetch` provides a raw `.htmld` response for pages that are not modeled by the parser. `workday_graphql` supplies the read-only route to Workday’s PEX surface, including Inbox and search.

## Setup and configuration

The workday-mcp MCP server runs through `npx` and requires the `WORKDAY_TENANT` environment variable with the tenant slug. A typical MCP configuration uses the `workday-mcp` package as the command and passes `-y` as its argument.

You must also install ContextMint Bridge, currently using its Chrome extension release. After loading the extension, sign in to Workday in the browser tab that the bridge can access. Safari support is not currently available. The bridge can also be built from its public source, or a release archive can be checked against its published SHA-256 file.

The repository points to `SKILL.md` for complete setup instructions. Local development uses `npm install`, `npm test`, and `npm run build`.

## Tools and capabilities

- `workday_get_apps` discovers available Workday apps and launchable task IDs.
- `workday_open_app` opens an app by name and follows its child cards.
- `workday_get_task` reads task or data cards, fields, table rows, references, related tasks, and export links.
- `workday_get_org_chart` returns the reporting chain with titles, locations, report counts, and profile URIs.
- `workday_get_worker` lists readable sections and named tasks for a worker.
- `workday_get_worker_task` opens a selected worker item, such as Compensation or Performance Reviews.
- `workday_get_my_profile` provides the signed-in user’s equivalent profile catalog.
- `workday_fetch` returns raw `.htmld` content with secrets redacted.
- `workday_graphql` performs read-only PEX GraphQL requests and refuses mutations.
- `workday_healthcheck` checks the bridge and session and reports an actionable hint.

## Limitations and notes

The workday-mcp MCP server depends on an active signed-in browser session and the ContextMint Bridge extension. It is not a replacement for an administrator-provisioned Workday REST or SOAP integration.

Access is limited to what the current Workday session can read, and parser coverage may not include every page. Use `workday_fetch` for unsupported page structures, while recognizing that its output is raw rather than normalized. The project advises checking the employer’s acceptable-use policy before using browser-session access to Workday data.

_Full upstream README: https://allmcps.com/mcp/workday-mcp/readme_