workday-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WORKDAY_TENANT | Yes | Your Workday tenant slug |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| workday_healthcheckA | Round-trips a small authenticated Workday endpoint through the fetchproxy bridge and returns diagnostics: the bridge's role (host/peer/null), port, version, round-trip time, and a plain-English hint that distinguishes 'bridge never came up' from 'extension not connected' from 'Workday session expired (re-sign-in)'. Call this when a Workday tool fails and you want to know which hop broke. Read-only. |
| workday_get_appsA | List the Workday apps available on your home screen, each with a launchable task id. Use this to discover what you can read, then pass an app's |
| workday_get_taskA | Fetch a Workday page (task or data card) by its path and return a structured, read-only view: title, current user, each section as label/value fields, navigable references (instance id + drill-in uri), and the page's related tasks + export links. The path is a Workday |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/chrischall/workday-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server