Skip to content
KiweelyKiweelyKiweely

Workday Agent Gateway vs. User-Delegated MCP Connectors: Prerequisites and Cost

Workday’s Agent Gateway MCP server requires Agent System of Record setup, UMSA (or Innovation Services), Workday Extend Professional, and Flex Credits for curated Agent-Ready Tools. User-delegated MCP connectors work on any standard tenant via Register API Client.

  • By Kiweely
  • Updated
  • 8 min read
On this page

Connecting an external AI assistant to Workday’s first-party MCP server (https://{region}.agent.workday.com/{tenant}/mcp) requires Workday Extend Professional (Extend AI), Agent System of Record (ASOR) setup in every tenant (with no cross-tenant migration tool), a Universal Main Subscription Agreement (UMSA) or Innovation Services opt-in, and Workday Flex Credits metered per block. By contrast, a user-delegated MCP connector—such as Kiweely Bridge (coming next)—connects to any standard Workday tenant using the core Register API Client task (Authorization Code Grant with PKCE) that every Workday customer already owns, with zero Flex Credits and full access to live WQL, SOAP reads, and existing RaaS reports.

Enterprise architects comparing the two routes often assume Workday’s Agent Gateway is simply a toggle on their existing tenant, or assume external MCP connectors require a shared Integration System User. Neither assumption matches how Workday’s platform actually works. Here is the architectural, operational, and commercial comparison verified directly from Workday’s documentation.

Head-to-Head Architecture Comparison

Architectural Layer Workday Agent Gateway (us.agent.workday.com/{tenant}/mcp) User-Delegated Standard-Tenant MCP (Kiweely Bridge, Coming Next)
Architectural LayerCommercial & contract gates Workday Agent Gateway ( us.agent.workday.com/{tenant}/mcp )UMSA (or MSA + Innovation Services opt-in), Flex Credits policy, and Extend Professional (Extend AI) SKU User-Delegated Standard-Tenant MCP ( Kiweely Bridge , Coming Next)None — works on any standard Workday HCM or Financials tenant
Architectural LayerTenant setup & migration Workday Agent Gateway ( us.agent.workday.com/{tenant}/mcp )Enable ASOR functional area, POST JSON to /asor/v1/agentDefinition, configure Agent Management Hub; cannot migrate ASOR configs across tenants User-Delegated Standard-Tenant MCP ( Kiweely Bridge , Coming Next)Run Register API Client once; guided in Sandbox by an AI admin agent
Architectural LayerRuntime identity model Workday Agent Gateway ( us.agent.workday.com/{tenant}/mcp )Agent System User (ASU) in Mode=Delegate (4-hour access token, 24-hour refresh token) or Ambient JWT User-Delegated Standard-Tenant MCP ( Kiweely Bridge , Coming Next)User-delegated OAuth 2.0 + PKCE (Register API Client), never an ISU; respects tenant session & refresh policies
Architectural LayerCallable Workday surfaces Workday Agent Gateway ( us.agent.workday.com/{tenant}/mcp )Curated Agent-Ready MCP Tools (Basic, Advanced, Prompt WIDs) User-Delegated Standard-Tenant MCP ( Kiweely Bridge , Coming Next)Workday REST APIs, live WQL discovery, SOAP XML reads, existing RaaS custom reports, and admin-enabled tasks
Architectural LayerSchema stability & versioning Workday Agent Gateway ( us.agent.workday.com/{tenant}/mcp )Unversioned; updated weekly on Tuesdays; tool/field renames happen without notice; binding prompts to tool names is prohibited User-Delegated Standard-Tenant MCP ( Kiweely Bridge , Coming Next)Versioned Workday REST (v1/v2), WQL (v1), and SOAP WSDLs (v43.2+); semi-annual R1/R2 updates handled by Kiweely
Architectural LayerSupported AI assistants Workday Agent Gateway ( us.agent.workday.com/{tenant}/mcp )MCP hosts on protocol versions 2024-11-05 to 2025-11-25; native Sana connectors only in Claude (beta) & Gemini Enterprise (no ChatGPT app) User-Delegated Standard-Tenant MCP ( Kiweely Bridge , Coming Next)Claude, ChatGPT, and Gemini across Mac, Windows, web, iPhone, and Android
Architectural LayerWrite action safety Workday Agent Gateway ( us.agent.workday.com/{tenant}/mcp )Conversational confirmation inside chat User-Delegated Standard-Tenant MCP ( Kiweely Bridge , Coming Next)Read-only by default; enabled writes pause for an out-of-band browser card showing Now vs. After
Architectural LayerCost structure Workday Agent Gateway ( us.agent.workday.com/{tenant}/mcp )Metered Flex Credits charged in unit blocks on the Platform Consumption Console User-Delegated Standard-Tenant MCP ( Kiweely Bridge , Coming Next)Flat monthly company price by Workday employee band (from $499/mo), unlimited calls, Production + all Sandboxes included

Inside Workday Agent Gateway: Five Real-World Constraints

Workday built Agent System of Record (ASOR) and Agent Gateway (us.agent.workday.com, eu.agent.workday.com, and six other regional endpoints) to govern autonomous agents inside Workday’s commercial AI framework (see Agent Passport governance explained). Before committing your roadmap to Agent Gateway, inspect five operational details documented in Workday’s Connect an External Agent with Workday MCP and Developer Guidelines & Change Policy:

1. The Extend Professional and UMSA Prerequisite

Workday’s external MCP setup guide states plainly: “This functionality is for Extend Professionals only.” Organizations still on a legacy Main Service Agreement (MSA) must either transition to the Universal Main Subscription Agreement (UMSA)—which includes Workday AI data contribution terms unless managed—or enable Innovation Services, and once complimentary credits run out, sign the Workday Flex Credits and Platform Entitlement Policy to keep agents running.

2. Per-Tenant Manual API Registration (No Object Transporter Support)

Workday provides no migration path (such as Object Transporter) for ASOR configurations between Implementation, Sandbox, and Production. And every weekly Sandbox refresh wipes ASOR setups that exist only in Sandbox. In each environment, an admin holding Setup: Agents, Manage: Agents, and Agent Management Hub must:

  1. Enable the Agent System of Record functional area in Maintain Functional Areas and run Activate Pending Security Policy Changes.
  2. Search the MCP Explorer (or call /asor/agentResourceSearch/v1) and copy the 32-character WID of every individual Basic, Advanced, and dependent Prompt tool (missing a Prompt WID breaks write tools; see troubleshooting permission denied and missing tool WIDs).
  3. POST the full ASOR v1.2 JSON definition to /asor/v1/agentDefinition with wd-agent-tenant-alias.
  4. Open Agent Management Hub, set Available To security groups (see fixing skills not showing in Agent Management Hub), save the one-time ASU client secret, and click Activate.

3. Unversioned Weekly Mutations Every Tuesday

Unlike Workday SOAP and REST APIs, Agent-Ready MCP Tools have zero API versioning. Workday’s September 2026 change policy states that Workday renames tools, restructures schemas, and rewrites field descriptions weekly on Tuesdays without advance notice, categorizing those changes as “non-breaking” because LLMs read schemas dynamically. Workday explicitly prohibits binding system prompts or deterministic workflows to specific tool names—and notes that if a long Workday tool name exceeds your AI client’s character limit, your only workaround is deleting that tool WID from your ASOR registration.

4. Curated Skills Only—Not Your Custom RaaS Reports or Ad-Hoc WQL

Every enterprise Workday tenant runs on dozens of custom reports (RaaS) and calculated fields built to match how that specific business defines headcount, cost centers, overtime, or bonus eligibility. Agent-Ready MCP Tools expose Workday-authored task wrappers—not arbitrary WQL queries or your existing RaaS catalog.

5. Block-Metered Flex Credits and 24-Hour Refresh Windows

On the Platform Consumption Console, Workday meters agent skills and API executions against Flex Credits in blocks of units: if a skill’s block size is 10 units for 5 credits, your very first execution charges all 5 credits upfront, and your 11th execution buys another full 10-unit block. Meanwhile, Workday’s ASU Delegate documentation notes that ASU refresh tokens expire after 24 hours, requiring employees to complete browser OAuth re-authorization daily rather than honoring a 14- or 30-day SSO refresh policy.

How User-Delegated Standard-Tenant MCP Connectors Work

A standard-tenant user-delegated MCP connector uses the exact OAuth foundation Workday built for interactive external clients (Register API Client with Authorization Code Grant and PKCE; see PKCE OAuth setup with corporate SSO):

text
Employee in Claude / ChatGPT / Gemini
   │  (1) Signs in once on Workday's own SSO + MFA screen
   ▼
Workday OAuth 2.0 (Register API Client + PKCE)
   │  (2) Issues user-delegated Bearer token scoped to worker's own Security Groups
   ▼
Kiweely Bridge (Stateless in RAM — AES-256-GCM client-sealed token, zero DB storage)
   │  (3) Translates tool call to Workday REST, live WQL, SOAP XML, or Custom RaaS
   │  (4) Strips admin-redacted fields in RAM; holds writes for out-of-band browser approval
   ▼
Standard Workday Tenant (HCM / Financials — zero AI SKUs or Flex Credits required)

Because Workday’s configurable security engine evaluates every REST, WQL, RaaS, and Bearer-authenticated SOAP request against the signed-in worker’s own security groups, data isolation inside Workday is identical to ASOR Delegate mode: an employee sees only their own payslips and balances; a manager sees only their constrained Supervisory Organization; and an HR partner sees only the populations their role permits.

Where Kiweely Bridge Adds Governance Beyond Both Raw APIs and ASOR

Kiweely Bridge (coming next; detailed on Bridge security and Bridge compare) pairs standard-tenant accessibility with enterprise controls that neither raw DIY connectors nor in-chat confirmations provide:

  1. AI admin agent instead of manual WID hunting: Bridge’s AI admin agent inspects your Sandbox tenant, guides Register API Client Functional Area selection, configures RAM-only field redaction (for example, masking national identifiers or sensitive compensation components), and runs live test prompts as real roles (Employee, Manager, HR Partner).
  2. Out-of-band browser write verification: Bridge starts read-only by default. When an admin enables a write task, Bridge pauses the MCP tool call and opens a browser approval card showing Now vs. After. A prompt injection hidden in an email or PDF inside Claude, ChatGPT, or Gemini cannot click Allow in that separate browser context.
  3. Zero stored payloads, three deployment options: Tokens are sealed with AES-256-GCM and carried by the MCP client—idle Bridge workers hold zero customer credentials, and telemetry logs never contain HR bodies. Deploy on Kiweely Cloud, Dedicated single-tenant (with a static outbound IP for Workday Maintain IP Ranges and Manage Authentication Policies), or Self-hosted stateless container inside your own AWS, GCP, Azure, or Kubernetes VPC.
  4. Predictable flat pricing with unlimited calls: One monthly fee per company by licensed Workday employee count—$499/mo (up to 1,000 employees), $1,499/mo (1,001–5,000), $3,999/mo (5,001–20,000), Enterprise by quote above 20,000 or dedicated/self-hosted, and free for one person on a personal Workday developer tenant—covering Production plus every Sandbox, Sandbox Preview, and implementation tenant.

(Looking to put clean custom portals, manager views, or three-button frontline mobile apps in front of Workday without a Workday Extend license? Kiweely Leaf—also coming next—applies the same zero-storage, user-delegated Workday OAuth architecture to employee web, mobile, and Teams/Slack screens.)

Decision Summary

  • Use Workday Agent Gateway if your company already holds Workday Extend Professional (Extend AI), has signed UMSA and the Flex Credits entitlement policy, runs internal agents built inside Workday alongside Claude or Gemini Enterprise, and wants strictly Workday-curated self-service skills.
  • Use a standard-tenant user-delegated MCP connector (Kiweely Bridge) if you want Claude, ChatGPT, and Gemini connected across your whole workforce without buying Extend or metering Flex Credits—while unlocking live WQL, SOAP reads, and existing RaaS reports behind zero-storage pass-through and browser-verified writes.
  • Building and testing the tenant itself during an implementation (configuration, reports, integrations, Extend apps) is neither route’s job: that is Kiweely Vine’s, shown phase by phase with recorded times in what AI agents do in a Workday implementation today.

Frequently asked questions

Can any Workday HCM or Financials customer connect to Workday's MCP server on Agent Gateway?

Not out of the box. Workday's official Connect an External Agent with Workday MCP guide explicitly states that the capability is for Extend Professionals (renamed Extend AI) only, requires Agent System of Record (ASOR) setup in every tenant, and requires either the Universal Main Subscription Agreement (UMSA) or Innovation Services opt-in on MSA.

How does Workday bill Agent Gateway and Agent-Ready MCP Tool usage?

Under UMSA and the Workday Flex Credits and Platform Entitlement Policy, agent skill and API usage is tracked in the Platform Consumption Console and charged in blocks of units against your organization's Flex Credit balance (where using 1 unit inside a 10-unit block purchases the entire 10-unit block).

Why can't I bind prompts or workflows to specific Agent-Ready MCP Tool names?

Workday's September 2026 Developer Guidelines & Change Policy states that Agent-Ready MCP Tools run on a single unversioned surface updated weekly on Tuesdays. Tool names, schemas, field names, and descriptions change without notice, and binding prompts or hard-coded logic to specific tool names is explicitly prohibited.

Does a user-delegated MCP connector sacrifice Workday security compared to ASOR Delegate mode?

No. Both ASOR Delegate ASU tokens and standard Register API Client (Authorization Code Grant with PKCE) tokens execute every call as the signed-in human worker. Workday's configurable security engine enforces identical Domain Security Policies, Business Process Security Policies, and constrained organization boundaries on both.

Your Workday work, done by AI.

Kiweely Vine is the AI agent that builds, deploys and tests Extend apps as real people, makes changes in any Workday task screen, answers from your real tenant and builds reports.

Get the next one in your inbox.

One email a month for Workday teams: what’s changing in Workday and what to retest, one tip tried in a real tenant, and what’s new at Kiweely.

We’ll email you once to confirm. Unsubscribe in one click from any issue.