Configure the Workday MCP Server
Connect Workday's official hosted MCP server to a Dtwo gateway via OAuth.
On this page
Overview
Workday operates an official hosted MCP server on its Agent Gateway (agent.workday.com) that exposes the Agent-Ready MCP tools you enable for an agent, across HR, talent, and finance data. Access is authorized through OAuth 2.0 with a client that Workday issues when you register and configure your gateway as an external agent in the Agent System of Record.
1. Configure Workday
- Confirm your tenant can use external agents. UMSA customers have it automatically. MSA customers need to enable it first with the Enable Innovation Services Feature and AI Data Contributions for MSA Customers task. The account doing the setup needs the Agent Management Hub and Manage Agents domains (Agent System of Record functional area) and Set Up: Tenant Setup - Security (System functional area).
- Run the Discover Available Agent-Ready MCP Tools task to see which tools you can expose, then register your gateway as an external agent in the Agent System of Record, following Workday’s Register and Authenticate External Agents guide.
- Open the Agent Management Hub report, select the Agent Registry tab, click your agent, and click Configure Agent. Enable the skills the agent should have, and for each one select the security groups that can use it under Available To. Click Confirm.
- For the redirect URI, enter your gateway’s OAuth callback URL — found in the Overview tab for your gateway in the Dtwo UI. Click OK.
- Workday shows the OAuth client details once. Copy the OAuth Client ID, OAuth Client Secret, and Authorize Endpoint URL.
- In Agent Registry, click your agent, then Activate Agent, and confirm.
- Use the View Security for Agent Skill report to make sure the security groups you picked have access to the domains and business processes behind each skill’s tools.
2. Add the MCP server to your gateway config
Go to your gateway in the Dtwo UI and open Configuration → Advanced. In the mcp_servers section add the following entry:
- name: workday
description: "Workday's official hosted MCP server for HR, talent, and finance data."
url: "https://<AGENT_GATEWAY_HOST>/<TENANT>/mcp"
transport_type: streamablehttp
authentication:
type: oauth
grant_type: authorization_code
client_id: "<CLIENT_ID>"
client_secret: "<CLIENT_SECRET>"
authorization_url: "https://<AGENT_GATEWAY_HOST>/auth/authorize/<TENANT>"
token_url: "https://<AGENT_GATEWAY_HOST>/auth/oauth2/<TENANT>/token"
redirect_uri: "<CALLBACK_URL>"
pkce_enabled: true
Replace the placeholder values:
<AGENT_GATEWAY_HOST>— your region’s Workday Agent Gateway host, for exampleus.agent.workday.com. It’s the host in the Authorize Endpoint URL you copied in step 1.<TENANT>— your Workday tenant name.<CLIENT_ID>and<CLIENT_SECRET>— the OAuth client details Workday showed when you configured the agent in step 1.<CALLBACK_URL>— the same redirect URI you set in step 1, found in the Overview tab for your gateway in the Dtwo UI.
Workday doesn’t use OAuth scopes — what the agent can do is set by the skills you enabled and the security groups you assigned to them.
3. Deploy and verify
Save the configuration and deploy the gateway.
Then, in your AI client, ask it to authorize Workday via the gateway. This opens the Workday sign-in screen — sign in as the user whose permissions the agent should inherit. Once authorized, confirm the workday-* tools appear and run a quick read-only call from one of the skills you enabled to make sure the connection and security groups work.
If the tools don’t appear after you authorize, refresh the tool list in your AI client — some clients don’t pick it up automatically.