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. On August 25, 2026, Rippling shipped its own answer for AI access, the Rippling MCP, a first-party server that works with Claude and acts with each person’s own Rippling permissions. It’s genuinely useful for the query side of HR work. This guide covers how to connect it, the gates you’ll hit first, and where a chat window stops being the right tool for people operations.
Connecting Claude to the Rippling MCP
Two things have to be true before anyone connects. A Rippling admin (super admin, full admin, or anyone with the Manage MCP Gateway permission) assigns access under IT › MCP Gateway › Rippling MCP › Access assignments, choosing which groups or people get it and which tools they can use. And your company needs an active Rippling AI subscription or trial, because without one the tools return no data.
Then each person connects their own Claude:
- In Rippling, open My IT › MCP connectors and find Rippling MCP.
- Click +, choose Claude, and follow the steps shown. Or copy the Remote MCP server URL.
- In Claude, open Customize → Connectors, add a custom connector, and paste that URL. On Team and Enterprise plans, an owner adds the connector once and each person then connects to it.
- Sign in with your Rippling account and start asking.
Rippling keeps SSNs, pay, home addresses, personal email, tax IDs and EEO data out of the connection, and nothing it returns goes past what your Rippling role already allows. Queries an HR lead would actually run:
- “Who on the engineering team is out today?”
- “How much PTO does Emily have left, and file a Friday off for me.”
- “Create a draft hire for Michael, starting on the 6th on Claire’s team.”
Claude handles these well. It can walk the org tree, check balances, file a time-off request that lands in the normal approval queue, and start a draft hire for someone to review in Rippling.
People ops runs on events; the connector doesn’t
Here’s the structural mismatch. Nothing in Rippling can wake Claude up.
Give Claude's scheduled tasks a time and they will run. Give them something that just happened and they will not. ChatGPT goes further, but only on web and mobile, and only for apps whose plugin supports events: OpenAI documents Gmail, Slack and GitHub and has not named the rest. A lead moving stage, a form landing, an invoice clearing: neither one has a published way to start on it. Carly starts on all of it.
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 because the hire happened. A Cowork task set to sweep Rippling every morning will find them, unattended, on Sunday; a weekly one finds them the following Thursday. A leave request that lands mid-afternoon waits for the same clock. The work does eventually get done, just never at the moment it mattered.
The scope is deliberately narrow, too. Rippling’s MCP covers people lookups, time off, draft hires and custom objects. Payroll, benefits changes and anything touching pay stay inside Rippling.
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. 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 | On a timer only | Yes |
| Notifies managers about leave requests automatically | No | Yes (email, Slack) |
| Who sets it up | Rippling admin assigns access, then each person connects Claude | You, in a guided conversation |
| Starts from an HR event rather than a clock | No | Yes |
| Pricing | Claude plan + Rippling AI subscription | 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?
Yes. Rippling launched its own MCP server on August 25, 2026. Once an admin assigns you access, add it to Claude from My IT › MCP connectors in Rippling, or paste its Remote MCP server URL as a custom connector under Customize → Connectors. It needs an active Rippling AI subscription or trial.
Can Claude kick off onboarding when a new hire is added?
Not on the hire itself. A new employee record in Rippling can’t start anything on the Claude side; the closest you get is a Cowork task that sweeps for new records on a timer and picks them up late. Trigger-based onboarding — provisioning tasks, manager emails, welcome messages — is what an agent platform like Carly handles.
Who can set up the Claude and Rippling connection?
An admin starts it and each person finishes it. No one has access until a Rippling admin creates an access assignment in the MCP Gateway. After that, each employee connects their own Claude and signs in with their own Rippling account.
Is it safe to connect Claude to Rippling?
Rippling built the server to be. It runs as the signed-in employee, so Claude can’t see or do anything that person couldn’t in Rippling, and SSNs, pay, home addresses, tax IDs and EEO data never pass through it. Offboarding someone in Rippling cuts off their connection immediately.
What’s the cheapest way to get Rippling automation?
Claude’s route needs a Rippling AI subscription on top of your Claude 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, 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."
