Workday

@workday show me my current PTO balance and any upcoming holidays in the next 30 days

Based on your Workday profile, you have 12.5 days of PTO remaining for 2024. Your absence balance includes 10 days of vacation time and 2.5 floating holidays. Upcoming holidays in the next 30 days: Memorial Day (May 27), Juneteenth (June 19). Note that these balances reflect accruals as of today and don't account for any pending time-off requests currently in approval.

This example combines two read operations (Get Absence Balance and Get Holiday Events) to give a complete picture of time-off planning. Requires OAuth scope for worker profile and absence data. Balance accuracy depends on your organization's accrual rules and approval workflows.

@workday submit a PTO request for June 10-14, full days, using my vacation balance

Time-off request created successfully. Request ID: TR-2024-05-8472. Submitted 5 days of vacation time for June 10-14, 2024 (Monday through Friday). The request has been routed to your manager Sarah Chen for approval. You'll receive a notification once it's reviewed. After approval, your remaining vacation balance will be 5.5 days.

This demonstrates the Create Time Off Request action, which initiates a business process in Workday. The MCP submits the request but doesn't guarantee approval—your org's approval chain still applies. Requires write permissions for absence requests, and the worker ID must match the authenticated user or have delegate access.

@workday pull the job description and screening questions for posting JR-2024-3891, then draft a candidate evaluation rubric based on the required qualifications

Retrieved job posting for Senior Backend Engineer (JR-2024-3891). Key requirements: 5+ years Go/Python, distributed systems experience, API design expertise. Screening questions cover system design scenarios, concurrency patterns, and past project scope. Based on these, here's a suggested rubric: (1) Technical depth—rate 1-5 on distributed systems knowledge from screening answers; (2) Communication clarity—assess how they explain trade-offs; (3) Scope match—compare their project scale to our requirements. The posting also lists 'mentorship experience' as preferred, worth adding as a tie-breaker criterion.

This showcases how the MCP can feed recruiting data into AI synthesis. Get Job Posting and Get Job Posting Questionnaire provide structured inputs; the AI then generates an evaluation framework. Useful for hiring managers prepping interviews, but the rubric is AI-generated—validate it against your org's actual competency matrix before use.

When this MCP streamlines interview feedback synthesis

A 6-person engineering team hiring for two roles runs debriefs every Friday. The hiring manager pulls interview feedback from Workday, pastes it into a doc, and manually flags patterns. With this MCP, the manager asks Switchy to retrieve feedback for all Thursday interviews, summarize highlights and concerns, and draft the debrief agenda. The MCP's Get Interview Feedback and Get Job Posting tools surface candidate responses against the actual job requirements. This works if your team runs structured interviews with written feedback—if interviewers skip the Workday form and just talk in Slack, the MCP has nothing to pull. Best fit: teams hiring 2-10 people per quarter who already enforce feedback discipline in Workday.

When absence balance lookups beat spreadsheet guesswork

A 12-person customer success team across three time zones plans coverage for Q4. The ops lead needs to know who has PTO left, who's already booked Thanksgiving week, and whether the on-call rotation has gaps. Manually checking Workday for each person takes 20 minutes. With this MCP, the lead asks Switchy to pull absence balances and holiday events for the whole team, then flag weeks where more than two people are out. The Get Absence Balance and Get Holiday Events tools return structured data Switchy can reason over. This breaks down if your Workday instance doesn't sync PTO requests in real time—stale data means bad coverage plans. Best fit: teams of 8-20 where PTO conflicts create customer risk.

When current-user lookups don't justify the OAuth overhead

A 4-person startup wants new hires to ask Switchy for their benefits summary, manager contact, and first-week calendar. The MCP's Get Current User tool can retrieve profile data, but OAuth2 setup requires IT to provision a Workday integration, set redirect URIs, and manage token refresh. For a team this small, the juice isn't worth the squeeze—new hires get the same info from a Notion page or a Slack message in 30 seconds. This MCP makes sense at 50+ employees where onboarding is frequent and HR wants self-service answers at scale. Below that threshold, the auth complexity outweighs the convenience gain. Best fit: mid-market teams (50-200 employees) with dedicated HR ops.