Local stdio MCP servers and .mcpb desktop bundles work fine on one engineer’s MacBook, yet collapse the moment IT tries to connect 2,000 employees to Workday. Rolling out Workday access across Mac, Windows, browser tabs, and mobile AI apps requires a remote HTTPS MCP endpoint where authentication, field redaction, and Workday release updates happen centrally without touching employee devices.
How a One-Developer Prototype Turns into an MDM Ticket Queue
When a developer builds an internal Workday prototype for Claude Desktop, packaging a local stdio server into an .mcpb archive feels fast. The archive bundles a Node.js or Python entrypoint, a manifest.json file, and a handful of tool definitions that call Workday REST or SOAP endpoints. On the author’s laptop, the desktop client spawns that process over standard input and standard output (stdio), opens a local loopback port for OAuth, and returns worker data.
Scale that architecture to Finance, HR Operations, and line managers, and four infrastructure walls appear immediately:
- Runtime drift across Windows and macOS. Non-engineering laptops rarely carry matching Node.js, Python,
uv, or system SSL certificate chains. Corporate proxies and TLS inspection appliances (such as Zscaler or Netskope) routinely reject Node’s bundled CA store unless IT injectsNODE_EXTRA_CA_CERTSinto every user profile. - Endpoint security and application allowlisting. CrowdStrike, Microsoft Defender, Jamf, and Intune flag unsigned child processes spawned by chat apps or block unapproved loopback listeners (
127.0.0.1:<random_port>) required to catch Workday’s OAuth redirect. - Hard exclusion of browser and mobile users. Most employees open ChatGPT, Claude, or Google Gemini in Chrome, Edge, iOS, or Android—none of which can execute a local
.mcpbbinary. - Uncontrolled token storage on endpoints. Many local MCP scripts persist Workday refresh tokens in
~/.config/JSON files or environment variables, creating thousands of unmonitored credential files across the fleet.
{
"mcpServers": {
"workday-local-bundle": {
"command": "node",
"args": ["/Library/Application Support/WorkdayMCP/dist/index.js"],
"env": {
"WORKDAY_TENANT": "production_tenant",
"WORKDAY_CLIENT_ID": "8f3c2a10-local-client",
"NODE_EXTRA_CA_CERTS": "/etc/ssl/certs/corp-root-ca.pem"
}
}
}
}Local .mcpb Bundles vs. Remote HTTPS MCP
The architectural gap between spawning a process on every endpoint and connecting to a remote HTTPS MCP URL affects security, device reach, and Workday maintenance.
| Rollout Dimension | Local .mcpb / stdio Bundle |
Remote HTTPS MCP Server |
|---|---|---|
| Rollout DimensionSupported AI surfaces | Local .mcpb / stdio BundleDesktop app only (Mac and Windows) | Remote HTTPS MCP ServerDesktop, web browser, iPhone, and Android across Claude, ChatGPT, and Gemini |
| Rollout DimensionEmployee setup | Local .mcpb / stdio BundleInstall bundle, runtime dependencies, and CA certs via Jamf/Intune | Remote HTTPS MCP ServerZero install; workspace owner adds one HTTPS URL and employee signs in on Workday |
| Rollout DimensionWorkday OAuth callback | Local .mcpb / stdio BundleLoopback listener (localhost port) per laptop; breaks on strict firewalls |
Remote HTTPS MCP ServerSingle registered HTTPS Redirect URI on Register API Client with PKCE |
| Rollout DimensionWorkday IP allowlisting | Local .mcpb / stdio BundleImpossible for roaming laptops without forcing full-tunnel VPN | Remote HTTPS MCP ServerSingle static outbound IP added to Workday Maintain IP Ranges |
| Rollout DimensionField-level redaction | Local .mcpb / stdio BundleRuns on the employee’s machine; user can inspect local process memory or code | Remote HTTPS MCP ServerEnforced server-side in memory before the AI client ever receives the tool output |
| Rollout DimensionTool & schema updates | Local .mcpb / stdio BundleRepackage .mcpb, re-sign, push MDM update, and restart desktop clients |
Remote HTTPS MCP ServerInstant central update; zero action required from employees or endpoint engineering |
| Rollout DimensionKill switch & revocation | Local .mcpb / stdio BundleRevoke Workday API client (breaking everyone) or wipe files per laptop | Remote HTTPS MCP ServerToggle individual tools, RaaS reports, or user access centrally in seconds |
The Security Flaw Nobody Notices Until Security Review: Client-Side Policy
In Workday, an employee’s security groups and domain policies—such as Self-Service: Pay, Worker Data: Current Staffing Information, or constrained Manager access—govern what Workday returns from REST, Workday WQL, and SOAP calls. Organizations almost always add a second governance layer for AI assistants: hiding National IDs, bank account numbers, or raw compensation elements even if a power user such as an HR Partner can view them inside the Workday UI.
With a .mcpb bundle, that second governance layer lives inside JavaScript or Python files sitting on the user’s hard drive. Any curious technical user can read the unpacked bundle, inspect the raw HTTP response coming back from Workday before the local script strips fields, or modify the script to enable write operations the HRIS team intended to keep disabled.
Workday administrators also rely on the Maintain IP Ranges and Manage Authentication Policies tasks to ensure OAuth tokens can only be exercised from trusted network origins. Local desktop bundles send Workday API requests directly from home Wi-Fi networks, coffee shops, and cellular hotspots unless every employee stays pinned to a full-tunnel corporate VPN. A remote MCP connector routes Workday traffic through a dedicated static outbound IP or a self-hosted VPC container, letting Workday reject token replay from any other network address.
Why Workday’s Release Cadence Punishes Distributed Bundles
Workday is not a static REST API. Tenants move through twice-yearly Feature Releases (R1 and R2), weekly service updates, custom report edits, and security policy activations. Consider what happens to a fleet of 2,000 .mcpb installations during a routine quarter:
- Custom RaaS prompt or column edits: An HRIS analyst updates a custom report enabled as a web service—adding a required
Effective_Dateprompt or renaming an XML column alias. Every laptop bundle with hardcoded RaaS report parameters starts throwing HTTP 400 or 500 errors until everyone updates their local package. - WQL and SOAP version bumps: Adjusting a SOAP
Human_Resourcescall to a newer WSDL version (for example,v45.1) or updating a WQL data source alias requires redeploying code to every Mac and PC. - Write-action safety: Prompt injection inside an email or candidate resume summarized by an AI client can trick a local stdio tool into firing a
Request Time Offor personal data update silently in the background unless an out-of-band confirmation gate exists outside the chat window.
How Remote HTTPS MCP Solves Rollout Governance
Modern MCP specifications support Streamable HTTP with OAuth 2.1 and PKCE, allowing an enterprise workspace owner to register a single remote connector URL once for the entire organization.
{
"mcpServers": {
"workday": {
"url": "https://bridge.kiweely.com/mcp"
}
}
}When an employee asks a Workday question in Claude, ChatGPT, or Gemini—whether on a locked-down Windows laptop, in Safari on an iPhone, or in a Chrome tab—the assistant initiates an OAuth handshake. The employee signs in directly on Workday’s own SSO and MFA screen. Every query then runs under a user-delegated Register API Client grant (Authorization Code Grant with PKCE), never an Integration System User.
Kiweely Bridge, which is coming next, is built around this exact zero-install remote MCP architecture:
- One central connector URL: IT pushes nothing through Jamf or Intune, installs no Python or Node runtimes on laptops, and maintains no
.mcpbarchives. - Client-held sealed tokens, zero stored payloads: Workday OAuth tokens are encrypted with AES-256-GCM and carried by the MCP client; responses stream through RAM where admin-blocked fields are stripped before reaching the model, with zero Workday records or prompts written to disk or logs (see Bridge security).
- Out-of-band browser write approval: Bridge is read-only by default. When admins enable specific write tasks, every write pauses and opens a browser approval card showing Now versus After so a chat prompt injection can never execute a silent transaction.
- Three deployment options: Run on stateless Kiweely Cloud (flat per-company pricing from $499/month for up to 1,000 licensed Workday employees with unlimited calls across Production and Sandbox, or free for one person on a personal Workday developer tenant), Dedicated single-tenant with a static IP for
Maintain IP Ranges, or a Self-hosted stateless container inside your own AWS, GCP, Azure, or Kubernetes perimeter.
Migration Checklist: Moving Off Local MCP Prototypes
If your engineering or HRIS team built a local .mcpb or stdio proof of concept, use these five checks before expanding beyond your pilot developers:
- Audit your Workday API Client type: Confirm you registered a user-delegated client via Register API Client (Authorization Code Grant with PKCE), not Register API Client for Integrations backed by an Integration System User (
ISU). - Eliminate disk-stored refresh tokens: Ensure employee laptops do not hold unencrypted Workday refresh tokens in local configuration directories.
- Test browser and mobile parity: Verify that an executive on an iPhone and a manager in a web browser get the exact same Workday tool behavior as an engineer on macOS.
- Enforce server-side field redaction: Strip sensitive attributes (such as national identifiers or restricted compensation components) in a stateless server layer before tool JSON reaches the LLM context window.
- Gate writes outside the chat stream: Require an explicit browser confirmation showing current and proposed Workday values before any business process is submitted.
Frequently asked questions
What is an .mcpb bundle in desktop AI clients?
An .mcpb bundle packages a local Model Context Protocol server, its Node.js or Python scripts, and manifest metadata so a desktop AI app can spawn it over standard input/output (stdio) on the user's laptop.
Why can't iPhone, Android, or browser AI apps run .mcpb bundles?
Web browsers and mobile operating systems sandbox applications and prohibit spawning local child processes over stdio. Only remote HTTPS MCP servers work across web, iOS, Android, Mac, and Windows simultaneously.
How does user-delegated OAuth differ between local .mcpb bundles and a remote MCP server?
Local bundles typically require localhost callback ports, plain-text config files, or OS keychain wrappers on every machine. A remote HTTPS MCP server handles OAuth 2.0 Authorization Code with PKCE centrally on a verified redirect URI without storing credentials on employee laptops.
What happens to local Workday MCP bundles during R1 and R2 releases?
When Workday updates REST schemas, WSDL versions, or WQL field aliases, every laptop running an older .mcpb bundle begins failing until IT repackages and redistributes the archive through MDM.