How to Connect Rippling to Claude (and What It Can't Do)
Rippling sits on some of the most sensitive data a company has — employee records, comp, PTO balances, payroll runs — so it’s no surprise that neither Rippling nor Anthropic has shipped an official bridge between the two. Checked July 2026: Rippling does not appear in Claude’s connector directory, and Rippling publishes no MCP server of its own. What exists instead is a small ecosystem of unofficial options, and they’re genuinely useful for the query side of HR work. This guide covers what they can do, the admin hurdle you’ll hit first, and where a chat window stops being the right tool for people operations.
The unofficial routes into your Rippling data
The most direct option is the open-source rippling-mcp-server on npm: 18 tools spanning employees, org structure, leave, groups, company info, and activity logs, authenticated with a plain bearer token. Integration platforms offer hosted alternatives — StackOne’s Rippling MCP exposes 37 actions through its gateway if you’d rather not run anything yourself.
Whichever you choose, the gate is the same: Rippling API tokens are created by workspace admins (Settings → API Tokens), and Rippling treats API access as an admin-level capability. An individual manager can’t wire this up quietly on the side — this is a decision your HR or IT admin makes, deliberately, about what employee data an AI assistant should see.
With a token in place, you add the server in Claude under Settings → Connectors as a custom connector (paid Claude plans only), authorize it, and start asking. Queries an HR lead would actually run:
- “Who in engineering is on PTO next week, and who approved it?”
- “List everyone who started this month with their manager and department — I’m building the new-hire welcome email.”
- “How many open leave requests are older than five days?”
Claude handles these well. It can cross-reference the org tree, spot the leave request nobody actioned, and draft the message you’d send about it.
People ops runs on events; the connector doesn’t
Here’s the structural mismatch. Claude’s connectors — first-party and custom alike — operate exclusively inside a conversation you begin. Nothing in Rippling can wake Claude up. So:
An offer gets signed and a new employee appears in Rippling on Saturday. The IT provisioning checklist, the manager heads-up, the day-one welcome note — none of it happens until a human opens Claude on Monday and asks. A leave request comes in while you’re in back-to-backs; the manager notification waits on you. Payroll cutoff approaches; Claude won’t remind anyone, because reminding requires the connector to act unprompted, and it can’t.
The unofficial-server route also puts real weight on trust: you’re forwarding employee PII through code Anthropic never reviewed. For read-only headcount questions many teams accept that; for anything touching comp, most don’t.
Handing the event-driven half to Carly
Carly exists for precisely the half that chat can’t reach. It’s an AI executive assistant that runs in the cloud and responds to triggers — a new hire appearing, a leave request landing, a scheduled payroll-week checklist — rather than waiting for a prompt.
You don’t configure it like an iPaaS. You tell it what you want in a sentence — “whenever a new hire is added in Rippling, email their manager the first-week plan and create the IT provisioning tasks” — and Carly asks clarifying questions, then builds the workflow alongside you. It sends the emails for real (Gmail and Outlook, with attachments), files the tasks, and books the onboarding sessions on the calendar. AI agents start at $35/month; steps in a workflow that don’t use AI run free and unlimited. Browse the Rippling integration page or the full integrations catalog.
How the two options divide the work
| Claude (Rippling MCP) | Carly | |
|---|---|---|
| Headcount, org, and PTO queries | Yes | Yes |
| Notices a new hire the moment they’re added | No | Yes |
| Runs the onboarding checklist unattended | No | Yes |
| Notifies managers about leave requests automatically | No | Yes (email, Slack) |
| Who sets it up | Admin API token + unofficial server + paid Claude plan | You, in a guided conversation |
| Works while you’re offline | No | Yes (cloud) |
| Pricing | Paid Claude plan (+ gateway fees if hosted) | AI agents from $35/mo |
Put simply: point Claude at Rippling when you have a question about your people data. Point Carly at Rippling when you want the routine that follows an HR event to stop depending on someone remembering.
Frequently Asked Questions
Does Claude integrate with Rippling?
Only through unofficial MCP servers — an open-source one on npm and hosted gateways like StackOne — added to Claude as a custom connector, which needs a paid Claude plan. Neither Rippling nor Anthropic offers a first-party connector as of mid-2026.
Can Claude kick off onboarding when a new hire is added?
No. A new employee record in Rippling can’t start a Claude conversation, and connectors don’t run outside one. Trigger-based onboarding — provisioning tasks, manager emails, welcome messages — is what an agent platform like Carly handles.
Who can set up the Claude–Rippling connection?
Effectively, an admin. Rippling API tokens are created in admin settings, so whoever owns your Rippling instance has to issue credentials before any MCP server can connect.
Is it safe to route employee data through a community MCP server?
That’s a judgment call your admin should make explicitly. The open-source server’s code is auditable; hosted gateways add a third party to your data path. Either way, scope the token minimally and skip anything comp-related until you’ve reviewed what the server exposes.
What’s the cheapest way to get Rippling automation?
Claude’s route needs a paid plan and still leaves you doing every run manually. Carly’s AI agents start at $35/month, and the non-AI steps of a workflow run free and unlimited, so an onboarding checklist that’s mostly record updates and emails stays cheap.
More: Claude connectors · Can Claude send emails · Claude vs Carly · Claude Cowork alternatives · Best AI tools for executives · Claude + Mural · Claude + Slite · Claude + Outline
Ready to automate your busywork?
Carly schedules, researches, and briefs you—so you can focus on what matters.
See what people say
"Before Carly, I relied on a Calendly link, but the whole process felt impersonal and not very professional. Carly changed that by handling all the back-and-forth, so I'm no longer stuck in endless email threads trying to line up schedules.
Now Carly reaches out to candidates, shares my real-time availability, lets them pick a slot, then sends a Zoom link and drops it straight into my calendar. She sends reminders to both of us before each call, which has significantly reduced no-shows and last-minute confusion.
On top of scheduling, Carly acts like a full executive assistant, sending me my schedule the night before so I can prepare for each call. It reminds me of the old x.ai assistant, but Carly is noticeably smarter, faster, and better suited to my healthcare recruitment business."
