Workday MCP logo

Workday MCP

Read-only Workday access through a signed-in browser session, covering profiles, org charts, pay, benefits, tasks, and GraphQL data.

Install Workday MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "workday-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "workday-mcp"
      ],
      "env": {
        "WORKDAY_TENANT": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

workday-mcp connects MCP clients to Workday through your signed-in browser tab and the ContextMint Bridge extension. It discovers apps, reads worker profiles and reporting lines, opens task pages, and exposes raw GET and read-only GraphQL access for less-structured data. All requests use the permissions already granted to your Workday account, with no server-side Workday login. Reach for it when an agent needs to inspect personal or organizational Workday data without an administrator-created API integration.

Use cases

  • Inspect your Workday pay, benefits, time-off, goals, and feedback
  • Trace reporting relationships and open readable worker profiles
  • Discover Workday apps and follow task or data-card references
  • Explore unfamiliar Workday pages through raw GET or GraphQL queries
  • Diagnose browser-bridge and signed-session failures

Key features

  • Reads Workday through an existing signed-in browser session
  • Discovers apps, task IDs, page references, and related links
  • Returns structured worker profiles and organization-chart data
  • Provides raw GET access with secret redaction
  • Supports read-only Workday PEX GraphQL queries
  • Includes bridge and session diagnostics

Tools10

What Workday MCP lets your agent do. Expand a tool for its parameters.

Verified live~2.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

9/9 checks healthy over the last 56d

What it can do

From the 10 tools this server returned when we ran it; 10 declare their own safety hints.

Runs commands · 1Handles credentials · 2Makes network requests · 10Read-only tools · 9
Network at startup3 connections
Files written at startup1
Install scriptsNone
npm provenanceSigned build
Package age133 days
Maintainers1

Observed 2026-10-30 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · workday-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars1Stargazers on the source repository.
npm downloads2.3kPackage downloads in the last 30 days.
Last commitTodayMost recent push to the default branch.
Tools exposed10Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Workday MCP works

What workday-mcp does

workday-mcp provides read-only access to Workday data through MCP. It can discover the apps on your Workday home screen, open supported apps, inspect task and data-card pages, and return structured fields, references, related tasks, and export links. Worker-oriented tools cover your own profile, other workers, reporting relationships, and the named items available in a worker profile, such as compensation, benefits, job details, goals, and performance information.

The server also includes lower-level access for cases that the structured tools do not cover. workday_fetch retrieves raw Workday JSON from GET endpoints with secrets redacted, while workday_graphql sends read-only queries to Workday’s PEX GraphQL surface. The GraphQL tool is intended for areas such as Inbox and global search that may not expose a GET-able .htmld page.

How it works

Requests are relayed through the ContextMint Bridge browser extension and an open, signed-in *.myworkday.com tab. The browser supplies the existing SSO and MFA-authenticated session; the MCP process does not perform a separate Workday login. Tenant-specific identifiers are discovered from the user’s Workday app menu, page references, and organization data at runtime.

A typical exploration starts with workday_get_apps, followed by workday_open_app or workday_get_task. Org-chart results provide profile URIs for workday_get_worker, whose task catalog can then be used with workday_get_worker_task. workday_healthcheck helps distinguish a bridge, extension, browser-capability, or Workday-side failure when another request fails.

Setup and configuration

Run the package as an MCP stdio server and provide the Workday tenant slug:

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

Install ContextMint Bridge separately, sign in to Workday in Chrome, and keep the signed-in tab available for requests. The Chrome extension can be loaded unpacked from its release archive. Safari support is not available yet. The bridge can also be built from its public source, or a release archive can be checked against its accompanying SHA-256 file.

Tools and capabilities

  • Discover Workday apps and launchable task IDs with workday_get_apps.
  • Open named apps and follow their child cards with workday_open_app.
  • Read structured task pages with workday_get_task.
  • Inspect reporting relationships with workday_get_org_chart.
  • Catalog and open worker profile information with workday_get_worker and workday_get_worker_task.
  • Read the signed-in user’s profile with workday_get_my_profile.
  • Retrieve raw GET data with workday_fetch or query supported GraphQL surfaces with workday_graphql.
  • Diagnose the browser bridge and Workday session with workday_healthcheck.

Limitations and notes

The server depends on an active signed-in browser session and the permissions assigned to that Workday account. It is not a replacement for an administrator-provisioned Workday REST or SOAP integration. Workday pages and GraphQL responses can vary by tenant, and some app launchers may need the full URL of an open page when a generic task ID returns little content.

Returned page text is treated as untrusted data because it may be authored by third parties; agents should not follow instructions embedded in that content. GraphQL mutations, subscriptions, and type-system documents are rejected, and sensitive identity, government, and financial fields are redacted by field name. The project is licensed under MIT, and users should follow their employer’s acceptable-use policy when accessing workplace data.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Workday MCP

workday-mcp is an MCP server that connects AI clients to Workday through a signed-in browser tab and ContextMint Bridge. Its main tools discover apps, read tasks, profiles, org charts, pay, and benefits, retrieve raw Workday data, run read-only GraphQL queries, and diagnose the browser session.

Install it as an MCP stdio server with `npx -y workday-mcp` and set `WORKDAY_TENANT` to your tenant slug. Then install ContextMint Bridge, sign in to Workday in Chrome, and keep the authenticated tab available.

No, workday-mcp uses your signed-in browser session instead of a Workday REST or SOAP API client. Requests pass through ContextMint Bridge, so the account’s existing SSO, MFA, and Workday permissions determine what can be read.

No, the exposed tools are read-only and do not mutate Workday data. GraphQL mutations and subscriptions are refused, while raw access is limited to GET requests.

Call `workday_healthcheck` after a failure. It reports bridge and extension state, connection details, round-trip timing, and a plain-language indication of whether the bridge, extension, browser capability, or Workday endpoint is the likely problem.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWorkday MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/workday-mcp?style=directory)](https://allmcps.com/mcp/workday-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/workday-mcp"><img src="https://allmcps.com/api/badge/workday-mcp?style=directory" alt="Workday MCP on AllMCPs" /></a>