Skip to content
KiweelyKiweelyKiweely

How to Test a Workday MCP Connector in Claude or ChatGPT Using a Free Developer Tenant

You can test live Workday MCP queries in Claude, ChatGPT, or Gemini without touching your employer’s Sandbox or signing a vendor contract. Pair a free personal Workday Build development tenant (preloaded with sample personas like Logan McNeil) with Kiweely Bridge’s free developer tier.

  • By Kiweely
  • 5 min read
On this page

An individual Workday architect, HRIS analyst, or engineer can evaluate live Workday MCP queries inside Claude, ChatGPT, or Gemini without touching company employee data, opening an InfoSec ticket, or entering a credit card. By provisioning a free personal development tenant through the Workday Open Developer Program at developer.workday.com, you get a real Workday tenant preloaded with synthetic workers, organizations, and security groups where you can verify user-delegated OAuth, WQL, and RaaS behavior firsthand.

Why Enterprise Sandbox Pilots Stall Before Day One

Proposing a live Workday AI pilot inside a corporate environment usually triggers a chicken-and-egg stalemate:

  • Information Security understandably refuses to connect even a company Implementation or Sandbox tenant (which often holds masked or recently refreshed production worker records) until the HRIS team proves how user-delegated OAuth, field redaction, and write approvals behave.
  • HRIS Architects cannot demonstrate those exact guardrails—or compare how constrained Manager security groups behave versus unconstrained HR Administrator roles—without a real Workday tenant wired to Claude or ChatGPT.

A personal Workday development tenant breaks that deadlock cleanly. It runs real Workday HCM, Financials, security domains, business processes, REST APIs, Workday WQL, SOAP web services, and custom RaaS reports, populated exclusively with synthetic sample records.

Step 1: Provision Your Free Personal Workday Developer Tenant

If you do not already have a personal tenant from the Workday Build / Open Developer Program, provisioning takes roughly five minutes:

  1. Navigate to https://developer.workday.com and register with your personal email address (keep personal experimentation separate from corporate SSO).
  2. Sign in to the Workday Build console, open the top-left navigation menu, and select Console → Tenants.
  3. Click Create Tenant. Workday provisions a dedicated development tenant in 1 to 2 minutes and emails a password-setup link.
  4. Set your tenant password and sign in as lmcneil (Logan McNeil), one of the preconfigured synthetic personas included in the sample dataset.

Inside that tenant, you immediately have access to synthetic Supervisory Organizations, active and terminated sample workers, absence plans, job requisitions, and the Security Administration domain needed to run Register API Client.

Step 2: Inspect Register API Client and Persona Boundaries

Before wiring any external AI client, verify the two security primitives that separate an enterprise-grade Workday MCP architecture from a risky integration-user shortcut:

Register a User-Delegated OAuth Client

Run the Register API Client task (never Register API Client for Integrations) in your developer tenant:

Register API Client Field Recommended Test Setting Why It Matters
Register API Client FieldClient Name Recommended Test SettingPersonal MCP Evaluation Why It MattersIdentifies the OAuth client in Workday sign-in and audit logs
Register API Client FieldClient Grant Type Recommended Test SettingAuthorization Code Grant (with PKCE) Why It MattersForces interactive user login so calls execute as the signed-in persona
Register API Client FieldAccess Token Type Recommended Test SettingBearer Why It MattersStandard short-lived OAuth 2.0 bearer token
Register API Client FieldScope (Functional Areas) Recommended Test SettingStaffing, Absence, Time Tracking, System Why It MattersSets the outer functional ceiling for REST, WQL, and RaaS calls
Register API Client FieldInclude Workday Owned Scope Recommended Test SettingSelected Why It MattersEnables core platform endpoints such as common and wql

Compare Two Synthetic Personas

A personal developer tenant lets you test role boundaries using distinct accounts rather than guessing how permissions work:

  • Privileged HR / Admin persona (lmcneil): Holds broad unconstrained access across sample Supervisory Organizations, custom reports, and staffing history.
  • Constrained Manager or Employee persona: Holds Employee As Self or org-constrained Manager security groups, seeing only their own pay/absence balances or direct reports.

Step 3: Run Five Real-World Verification Prompts

Once connected to an MCP client in Claude or ChatGPT, test the exact scenarios your CISO and HRIS director will ask about during a formal Sandbox review:

  1. Self-service read check: Sign in as an individual worker persona and ask, “What are my current vacation and sick time-off balances, and do I have any pending requests?” Confirm the assistant calls Workday’s absenceManagement or WQL surface and returns live numbers matching the Workday UI.
  2. Cross-org boundary check: Staying signed in as that same non-HR worker or line manager, ask, “Show me base compensation and bonus targets for workers outside my Supervisory Organization.” Verify that Workday’s domain and constrained security groups return zero unauthorized rows—proving security is enforced by Workday’s OAuth token, not prompt instructions.
  3. Ad-hoc WQL aggregation: Sign in as lmcneil and ask, “Break down active worker headcount by location and management level.” Inspect the generated WQL GROUP BY query against allWorkers or workersForHCMReporting.
  4. Custom RaaS report reuse: Open Create Custom Report (or edit an existing advanced sample report), check Enable As Web Service on the Advanced tab, and ask the assistant to summarize its output with prompt filters.
  5. Write-approval safety check: Enable a single task such as Request Time Off and ask the assistant to submit one day of leave. Verify whether the connector pauses and requires an out-of-band browser confirmation showing Now and After before touching Workday.
Works
SELECT location, count(worker)
FROM allWorkers
WHERE currentlyActive = true
GROUP BY location

How Kiweely Supports Free Developer Tenant Testing Today and Next

Kiweely treats personal Workday developer tenants as first-class proving grounds so practitioners can validate real product behavior with zero procurement friction:

  • For Workday Extend, Studio, WQL, and tenant configuration today (Kiweely Vine): Kiweely Vine is live today on Mac and Windows. Vine Free is free for your Workday personal developer account and its tenant. Any other tenant needs Vine Personal at $99 a month for one person, or a Vine Team seat at $149 a month. You can connect Vine to your personal developer tenant right now to build Extend apps, write Studio integrations, author calculated fields, and run WQL queries.
  • For Claude, ChatGPT, and Gemini connectivity (Kiweely Bridge, coming next): Kiweely Bridge is free for one person on their own Workday developer tenant and its sample data—with no trial period and no credit card. You get the same remote HTTPS MCP architecture, sealed client-held AES-256-GCM tokens, AI admin setup agent, in-memory field redaction, and out-of-band browser write approval cards that companies run on paid plans ($499/mo up to 1,000 licensed Workday employees, $1,499/mo for 1,001–5,000, $3,999/mo for 5,001–20,000, with unlimited calls across Production and Sandbox).

Turning Your Developer Proof into a Sandbox Proposal

When you finish testing on your personal developer tenant, bring three concrete artifacts to your IT and Workday security stakeholders:

  1. The exact Register API Client scope list: Show which Functional Areas were enabled and confirm zero Integration System Users (ISU) are involved.
  2. Side-by-side persona transcripts: Demonstrate the identical prompt run as an Employee versus an HR Partner, proving Workday’s native domain security blocks unauthorized rows at the source.
  3. Zero-storage telemetry evidence: Show how Bridge security logs only timestamp, tenant ID, tool name, HTTP status, and latency—never worker names, prompts, or payloads—and offer Dedicated static IP or Self-hosted VPC container options if corporate policy requires network-level isolation.

Frequently asked questions

Does a personal Workday Build developer tenant include sample HR and finance data?

Yes. Personal development tenants provisioned at developer.workday.com come preloaded with synthetic Global Modern Services sample workers, Supervisory Organizations, compensation plans, absence balances, and test personas such as Logan McNeil (lmcneil).

Should I ever connect my employer's Sandbox or Production tenant to a personal developer account?

No. Keep evaluation on your own personal Workday developer tenant using synthetic sample data until your company's IT and Workday security team formally reviews and approves a Sandbox pilot.

Is Kiweely Bridge time-limited on a personal Workday developer tenant?

No. When Kiweely Bridge launches (coming next), it is free for one person on their own Workday developer tenant and its sample data, with no trial period and no credit card required.

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.