Workday MCP

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.