IT and HRIS teams rolling out Claude Enterprise or Claude Team across the company have four real options to connect Claude to live Workday data: Workday’s own Agent Gateway and Sana connector (beta), StackOne, building a custom MCP server in-house, and Kiweely Bridge (coming next). Every one of the four can authenticate individual employees as themselves rather than sharing a service account—what separates them is whether you need a Workday AI commercial agreement and Flex Credits, whether Claude can reach your existing RaaS reports and live WQL, whether employee tokens and HR payloads sit in a vendor database, how writes are confirmed, and how you pay.
(Note on developer vs. workforce tools: If you are a Workday consultant or HRIS developer trying to build Extend apps, Studio integrations, or tenant configuration with Claude, Kiweely Vine is live today for Mac and Windows—free on a personal Workday developer tenant and $149/seat/mo for teams. This comparison covers connecting Claude itself—across desktop, browser, iPhone, and Android—for every employee in your company.)
Side-by-Side Comparison of All Four Options
Every factual claim below is verified against Workday’s administrator and developer documentation, Anthropic’s connector directory listing for Sana from Workday, StackOne’s published connector and pricing pages, and Kiweely Bridge’s comparison matrix:
| Evaluation Criteria | Workday Agent Gateway & Sana | StackOne | Build In-House (Custom MCP) | Kiweely Bridge (Coming Next) |
|---|---|---|---|---|
| Evaluation CriteriaWorks on any standard Workday tenant | Workday Agent Gateway & SanaPartial — needs UMSA / Workday AI agreement & Flex Credits; raw Workday MCP requires Extend Professional (Extend AI) | StackOneYes — uses Register API Client OAuth |
Build In-House (Custom MCP)Yes — once your engineers build & host the server | Kiweely Bridge (Coming Next)Yes — uses Register API Client (Authorization Code + PKCE) |
| Evaluation CriteriaPer-employee Workday permissions | Workday Agent Gateway & SanaYes — Delegate ASU / role mirroring | StackOneYes — per-user OAuth | Build In-House (Custom MCP)Partial — only after implementing MCP OAuth 2.1 + PKCE yourself | Kiweely Bridge (Coming Next)Yes — runs under each worker’s own security groups & domains |
| Evaluation CriteriaClaude, ChatGPT, and Gemini from one setup | Workday Agent Gateway & SanaPartial — Sana in Claude (beta) + Gemini Enterprise; no ChatGPT app | StackOneYes — one gateway URL for all three | Build In-House (Custom MCP)Partial — after registering & testing OAuth with each vendor | Kiweely Bridge (Coming Next)Yes — all three across Mac, Windows, browser, and mobile |
| Evaluation CriteriaLive WQL, SOAP reads, and custom RaaS reports | Workday Agent Gateway & SanaPartial — Agent-Ready Tools & Sana skills only; no ad-hoc WQL or arbitrary RaaS | StackOneYes — REST, SOAP, WQL, and RaaS across 162 prebuilt Workday actions | Build In-House (Custom MCP)Partial — weeks of SOAP XML, WQL schema, and pagination engineering | Kiweely Bridge (Coming Next)Yes — REST, live WQL discovery, SOAP reads, and existing RaaS out of the box |
| Evaluation CriteriaWrite approval outside the chat window | Workday Agent Gateway & SanaPartial — policy-based approval confirmed inside the conversation | StackOnePartial — policy-based human sign-off | Build In-House (Custom MCP)Yours to design, security-review, and maintain | Kiweely Bridge (Coming Next)Yes — read-only by default; enabled writes open an out-of-band browser card (Now vs. After) |
| Evaluation CriteriaAI admin agent for setup & role testing | Workday Agent Gateway & SanaNo — manual registration in Agent System of Record | StackOnePartial — dashboard toggles and manual field-level tool policies | Build In-House (Custom MCP)None unless you build an internal admin UI | Kiweely Bridge (Coming Next)Yes — configures Sandbox API client, RAM field redaction, and tests as real roles |
| Evaluation CriteriaToken & payload storage | Workday Agent Gateway & SanaWorkday Cloud only | StackOneUS/EU cloud storing tokens & action logs (VPC as Enterprise add-on) | Build In-House (Custom MCP)Your cloud, your logs, your compliance burden | Kiweely Bridge (Coming Next)Zero stored payloads, zero token DB (AES-256-GCM sealed tokens; Cloud, Static IP, or Self-Hosted container) |
| Evaluation CriteriaPricing model | Workday Agent Gateway & SanaWorkday Flex Credits consumed in blocks per skill/call (+ Sana Enterprise SKU for extended features) | StackOneBase plan fee + monthly active seats + per-call credits | Build In-House (Custom MCP)Engineering build weeks + ongoing DevOps & twice-yearly Workday release maintenance | Kiweely Bridge (Coming Next)Flat per company by Workday headcount ($499 / $1,499 / $3,999 / mo), unlimited calls, Sandbox included; Free on personal dev tenant |
Option 1: Workday Agent Gateway and Sana from Workday (Beta)
Workday offers two overlapping first-party paths into Claude:
- Sana from Workday in Claude’s connector directory (beta): Aimed at conversational self-service for customers on Workday’s Universal Main Subscription Agreement (UMSA) with Sana Core or Sana Enterprise enabled (see Sana Self-Service Agent setup).
- Workday MCP Server on Agent Gateway (
https://us.agent.workday.com/{tenant}/mcp): Exposes Workday’s curated Agent-Ready MCP Tools once an external agent is registered via API in Agent System of Record (ASOR) and assigned an Agent System User (ASU) Delegate token.
Where it shines: Zero third-party vendor review—traffic stays strictly between Anthropic and Workday’s regional Agent Gateway.
Where teams hit limits:
- Contract and SKU gates: Workday’s MCP documentation states that external MCP connectivity is for Extend Professionals only, and production Workday AI requires UMSA plus Flex Credits metered in blocks on the Platform Consumption Console.
- No ad-hoc WQL or existing RaaS reports: Agent-Ready Tools flatten specific Workday tasks for LLMs, and Workday’s change policy updates tool names and schemas weekly on Tuesdays without versioning. If a Finance VP or HR partner asks Claude to run a custom RaaS report with ten calculated fields or an ad-hoc WQL join, Agent-Ready Tools do not expose those surfaces.
- In-chat write confirmation and no ChatGPT parity: Confirmations happen inside the chat stream, and if half your company uses ChatGPT alongside Claude, you still need another connector.
Option 2: StackOne
StackOne is an enterprise AI agent tool gateway covering 640+ SaaS applications, with Workday as one of its flagship connectors.
Where it shines: StackOne already ships today, supports per-user Workday OAuth via Register API Client, reaches REST, SOAP, WQL, and RaaS across 162 prebuilt Workday actions, and connects to Claude, ChatGPT, and Gemini from a single gateway URL. If your goal is buying one multi-SaaS gateway to wire Workday, Greenhouse, Jira, Salesforce, and ServiceNow into Claude under a single procurement contract, StackOne is purpose-built for breadth.
Where teams weigh trade-offs:
- Stored tokens and action logs: Because StackOne manages connections across hundreds of SaaS tools, its US/EU cloud stores customer OAuth tokens and action logs (VPC deployment requires an Enterprise add-on). For CISOs who treat Workday compensation, SSN/Tax IDs, and HR records as Tier-0 crown jewels that must never sit in a third-party log store, stored payloads extend security review.
- Seat + call metering: Pricing combines a platform plan fee, monthly active seats, and per-call credit consumption—meaning heavy WQL or company-wide Claude adoption scales variable cost.
- Manual Workday setup: Admins configure API Client Functional Areas and dashboard tool toggles by hand rather than working with a Workday-specialized AI admin agent that tests
Employeevs.Managerpersonas in Sandbox.
Option 3: Build a Custom Workday MCP Server In-House
For engineering-heavy organizations with an existing platform team, Anthropic’s open MCP SDK makes a basic prototype look deceptively quick—until InfoSec asks to take it from one developer’s laptop to 3,000 employees on web and mobile.
Where it shines: Total source-code ownership inside your own VPC with zero external SaaS vendor.
What you actually end up building and maintaining:
- Remote MCP OAuth 2.1 + Workday PKCE broker: Local
stdio.mcpbbundles cannot run on Claude iOS, Android, or managed web browsers without pushing Python/Node runtimes through MDM. You must host a public HTTPS OAuth 2.1 server that brokers Workday’s PKCE Authorization Code flow and refreshes rotating tokens safely. - WQL schema discovery, SOAP XML pagination, and RaaS parsing: Workday REST covers a fraction of HCM and Financials. Useful answers require dynamic WQL metadata discovery (
/wql/v1/dataSources), SOAP XMLResponse_Filtersnapshot paging (As_Of_Entry_DateTime), and custom RaaS prompt marshaling (see RaaS vs. WQL vs. REST). - Twice-yearly Workday release maintenance (R1 / R2): Every March and September, Workday deprecates older WWS versions, updates WQL aliases, and modifies domain security items—putting your internal platform engineers on permanent HRIS maintenance duty.
Option 4: Kiweely Bridge (Coming Next)
Kiweely Bridge (coming next) focuses exclusively on Workday—combining standard-tenant reach across Claude, ChatGPT, and Gemini with a zero-storage security posture (Bridge security):
- Standard tenant, per-employee OAuth: Uses
Register API Client(Authorization Code Grant + PKCE), never an Integration System User. Every REST, live WQL, SOAP read, and RaaS query runs under the signed-in employee’s own Workday security groups. - Zero stored payloads, client-sealed tokens: Bridge stores zero employee Workday tokens in a database (grants are sealed with AES-256-GCM inside the MCP client token and decrypted only in RAM during a request) and writes zero HR records, worker names, or pay figures to disk or logs.
- Out-of-band browser write card: Read-only by default; when an admin enables a write action, Bridge pauses and opens a browser approval card showing Now vs. After outside the chat thread so prompt injection in Claude cannot submit a change.
- AI admin agent + three hosting modes: An AI admin agent sets up
Register API Clientin Sandbox, applies RAM field redaction rules, and tests real roles (Employee,Manager,HR Partner). Deploy on Kiweely Cloud, Dedicated single-tenant with static outbound IP (Maintain IP Ranges), or self-hosted stateless container in AWS, GCP, Azure, or Kubernetes. - Flat headcount pricing, unlimited calls: $499/mo (up to 1,000 Workday 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, covering Production + all Sandbox and implementation tenants—plus free for one person on their own Workday developer tenant.
How to Pick the Right Path for Your Company
- Choose Workday Agent Gateway / Sana if you have already signed UMSA with Flex Credits, own Extend Professional, only use Claude (and/or Gemini Enterprise), and only need Workday’s preset self-service skills.
- Choose StackOne if you want a single vendor gateway across dozens of non-Workday SaaS tools today and your security policy permits third-party token and action-log storage with seat + call metering.
- Choose In-House if you have dedicated platform and Workday API engineers budgeted to own OAuth 2.1 hosting, SOAP/WQL translators, and R1/R2 release updates indefinitely.
- Register interest in Kiweely Bridge if you want full REST, live WQL, SOAP, and RaaS reach across Claude, ChatGPT, and Gemini on a standard tenant—with zero HR payloads stored at rest, browser-verified writes, an AI admin agent, and one flat monthly company price. (And if you also want custom employee portals or mobile/Teams screens outside chat on the same zero-storage employee OAuth model, look at Kiweely Leaf, also coming next.)
Frequently asked questions
Can we connect Claude Enterprise to Workday without Workday Extend or Flex Credits?
Yes. Both StackOne, an in-house MCP server, and Kiweely Bridge (coming next) connect to any standard Workday tenant through a user-delegated OAuth client created with Register API Client—requiring no Workday AI agreement, no Agent System of Record, no Flex Credits, and no Workday Extend subscription.
Do all four Claude-to-Workday options enforce per-employee Workday permissions?
Workday's Agent Gateway/Sana, StackOne, and Kiweely Bridge all support per-employee OAuth so calls execute under the signed-in worker's own Workday security groups. An in-house MCP server only enforces per-employee permissions if your engineers build full MCP OAuth 2.1 + Workday PKCE authorization instead of taking the shortcut of a shared Integration System User.
What is the difference between connecting Claude for all employees vs. using Kiweely Vine with Claude?
Connecting Claude Enterprise or Team via remote MCP (such as Kiweely Bridge, coming next) gives every employee, manager, and executive live Workday Q&A and self-service inside Claude across web, desktop, and mobile. Kiweely Vine (live today on Mac and Windows) is the dedicated desktop AI co-pilot for Workday consultants and HRIS developers building Extend apps, Studio integrations, WQL reports, and tenant configurations.
How do the four options differ on storing HR data and OAuth tokens?
Workday's connector runs in Workday's cloud; StackOne operates a multi-app cloud gateway in the US or EU that stores customer tokens and action logs (with VPC available as an Enterprise add-on); an in-house server puts storage and logging responsibility on your own DevOps team; and Kiweely Bridge (coming next) runs zero-storage pass-through in RAM with client-sealed AES-256-GCM tokens and payload-free telemetry, plus Dedicated static IP or self-hosted container modes.