Rippling
HR, payroll, IT.
Verdict
Common use cases
- Pull headcount by department for budget planning
- Check who's out next week before scheduling
- Audit SaaS access across the org
- Generate org chart for investor update
- Verify new hire onboarding status
Integration
- Vendor
- Rippling
- Category
- productivity
- Auth
- OAUTH2
- Composio slug
rippling
Tools
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Find Rippling in the MCP directory and click Connect. 3. You'll be redirected to Rippling's OAuth consent screen — log in with an admin account that has API access enabled. 4. Grant the requested scopes: typically 'employees:read', 'time_off:read', 'payroll:read', and 'directory:read'. 5. Rippling redirects you back to Switchy with a success message. 6. Open any Space and type '@Rippling list employees in Engineering' to confirm the connection works. 7. If the response is empty, check that your Rippling admin role includes API permissions under Settings > Developers. 8. Once verified, invite teammates to the Space so they can @mention Rippling in their own prompts.
What teammates see: by default, memories from Rippling are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Headcount Snapshot
@Rippling show me total headcount right now, grouped by department and employment status (full-time, contractor, intern).Open in a Space →
Upcoming Time Off
@Rippling who on the product and engineering teams has approved time off in the next 14 days?Open in a Space →
Software Access Audit
@Rippling list everyone with active access to Salesforce, including their role and department.Open in a Space →
New Hire Onboarding Check
@Rippling show onboarding status for employees who started in the last 30 days — which tasks are pending?Open in a Space →
Org Chart Export
@Rippling give me the org chart for the entire company, showing each person's manager and direct reports.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@Rippling show me all employees who started in the last 30 days with their department and manager assignments
Based on your Rippling account, 7 employees started in the last 30 days: • Sarah Chen (Engineering, reports to Mike Torres) - started Jan 15 • James Park (Sales, reports to Lisa Wong) - started Jan 22 • Maria Garcia (Marketing, reports to David Kim) - started Jan 28 • Three additional hires in Customer Success and Operations This example illustrates how the MCP would return structured employee data with role context. Actual results depend on your org's current headcount and recent hiring activity.
This read operation requires HR admin permissions in Rippling. The MCP surfaces onboarding cohorts quickly, useful for tracking new-hire progress or planning team introductions. Be aware that employee data access is governed by your Rippling role-based permissions — you'll only see records your account can view.
@Rippling create a new PTO request for me: 3 days off starting February 10th for a family trip
PTO request created in Rippling: • Employee: [Your Name] • Type: Vacation • Dates: Feb 10-12, 2025 (3 days) • Status: Pending manager approval • Reason: Family trip Your manager will receive a notification to approve or deny this request. This example shows how the MCP would confirm the action and next steps. The actual request now exists in your Rippling account and follows your company's approval workflow.
This write operation modifies your HR records and triggers approval workflows. The MCP respects your company's PTO policies (accrual limits, blackout dates). If the request violates policy, Rippling's API will reject it and the MCP will surface that error. Always verify the created request in Rippling's UI before assuming it's final.
@Rippling pull the last 90 days of payroll runs and summarize total compensation costs by department
Analyzing 4 payroll runs from your Rippling account (Oct 15 - Jan 15): **Total compensation: $847,300** • Engineering: $425,000 (50.2%) — 12 employees • Sales: $238,500 (28.1%) — 8 employees • Operations: $183,800 (21.7%) — 6 employees This includes base salary, commissions, and employer taxes. The MCP retrieved payroll summaries and the AI calculated departmental breakdowns. Actual figures depend on your company's pay cycles and employee count during this period.
This synthesis example combines Rippling's payroll data with AI analysis. Requires finance or admin-level access to view compensation data. Useful for budget reviews or headcount planning, but remember that payroll data is sensitive — only run this in Spaces where all members have appropriate access. The MCP cannot access individual salary details unless your Rippling role permits it.
Use-case deep-dives
When Rippling MCP speeds up day-one setup
A 10-person startup hires two engineers in the same week. The ops lead needs to provision laptops, add them to Slack and GitHub, set up payroll, and assign benefits—all before Monday. The Rippling MCP lets an AI agent pull employee records, check provisioning status, and surface blockers without opening five browser tabs. Because Rippling already centralizes HR, IT, and payroll, the MCP becomes a single query layer for onboarding checklists. This works best when your team is under 50 people and you're not running custom HRIS integrations that Rippling's API doesn't expose. If you're manually tracking onboarding in Notion or spreadsheets, connecting Rippling through Switchy cuts the context-switching in half.
Why this MCP matters for distributed payroll checks
A finance team at a 30-person remote company closes the books on the 5th of each month. They need to verify that contractor payments in Rippling match invoices in QuickBooks, and that PTO accruals align with the last pay period. The Rippling MCP lets an AI agent query employee comp data, pull time-off balances, and cross-reference payment runs without exporting CSVs. OAuth2 auth means the finance lead doesn't share admin credentials. This scenario breaks down if Rippling's API rate-limits your queries or if you need real-time payroll edits—the MCP is read-heavy, not transactional. For monthly reconciliation workflows where speed matters more than write access, Rippling in Switchy saves 30 minutes of tab-hopping per close.
When Rippling MCP replaces Slack-based IT requests
A 40-person company's IT lead gets five Slack DMs a day: 'Can I get admin on the design tool?', 'My laptop charger broke', 'When does my benefits enrollment close?' The Rippling MCP lets an AI agent answer these questions by querying device assignments, app permissions, and benefits deadlines in one place. Instead of logging into Rippling's admin panel for every ask, the IT lead uses Switchy to surface answers in seconds. This works when your team uses Rippling for both device management and app provisioning—if you're split across Jamf and Okta, the MCP's value drops. For teams under 100 where IT is a part-time role, connecting Rippling to Switchy turns reactive support into a self-service knowledge layer.
Frequently asked
What does the Rippling MCP do in Switchy?
The Rippling MCP connects your Rippling workspace to Switchy so AI assistants can read employee data, org charts, time-off balances, and payroll summaries. You can ask questions like 'who reports to Sarah' or 'how many days of PTO does the engineering team have left' without opening Rippling. It doesn't write data back — use Rippling directly for approvals or policy changes.
Do I need admin access in Rippling to connect this?
Yes. The OAuth flow requires a Rippling admin account because it requests read access to employee records, compensation data, and org structure. Standard employees can't grant these scopes. If you're not an admin, ask your HR lead or IT admin to connect the integration in Switchy's settings.
Can the MCP approve time-off requests or update employee records?
No. The Rippling MCP is read-only. It surfaces data for AI assistants to answer questions, but it can't approve PTO, change salaries, or edit profiles. For write operations, you still need to log into Rippling or use their native approval workflows.
How is this different from just opening Rippling in a browser tab?
The MCP lets you query Rippling data in natural language inside Switchy's AI workspace, without context-switching. Instead of navigating Rippling's UI to find 'who's out next week', you ask the assistant and get an instant answer. It's faster for ad-hoc questions, but Rippling's interface is still better for bulk edits or complex workflows.
Who on the team should connect the Rippling integration?
Your HR admin or IT lead. They already have the Rippling admin credentials needed to authorize the OAuth scopes. Once connected, any Switchy user in your workspace can query the data through AI assistants — subject to your team's access policies in Switchy.