Rippling MCP: How to Connect Rippling to AI in 2026
No — Rippling doesn’t offer a documented MCP server for connecting your HR data to Claude or ChatGPT. Its developer portal covers four public things — custom solutions, the REST API, App Shop integrations, and an SDK — and a customer-facing Model Context Protocol connector is not among them. There is one wrinkle worth stating precisely, because it looks like a contradiction: an OAuth-protected endpoint does answer at mcp.rippling.com/mcp. It appears in Rippling’s docs only under an internal access-management section describing an “MCP Gateway,” and the operations around it are policy management rather than employee-record access — the shape of a tool for governing which MCP servers staff may use, not a server exposing your HR data. Treat it as infrastructure, not a connector, unless Rippling documents otherwise. Rippling’s AI bet went the other way: Rippling AI is built into the product, answering questions about your company from live data inside Rippling itself, rather than handing your HR data out to Claude or ChatGPT. So what you’ll actually find searching “Rippling MCP” are community and commercial third-party servers wrapping Rippling’s REST API — not something Rippling built or endorses.
Be careful with what you read here, too: at least one widely-syndicated listing describes a hobby project as “the official Rippling MCP server.” It isn’t.
Even where one of these servers works, the same limit applies: an MCP server hands Rippling to an AI inside a conversation you start. It’s a doorway, not a worker. Nothing watches for a time-off request, nothing fires when someone’s start date arrives, and nothing runs while the chat is closed. Here’s the honest state of Rippling and MCP, the admin gate you’ll hit first, and what to use when you want Rippling work that runs on its own.
Looking beyond Rippling? MCP servers by category covers the rest.
What an MCP connection to Rippling does
Model Context Protocol (MCP) is the open standard that lets an AI client — Claude, ChatGPT, Cursor, and others — talk to an outside app through a shared interface. Rippling hasn’t built one, so the servers people mean fall into two camps:
- Community projects.
bifrost-mcp/rippling-mcpis the most-linked one — MIT-licensed, 18 tools across company, employee, org, leave, group, and activity data. Judge it on its record before trusting it: it’s a single 0.1.0 release, its code hasn’t been touched since February 2026, and it pulls a few dozen npm downloads a month. That’s a weekend project, not infrastructure. - Commercial third-party servers. StackOne and Pipedream host their own Rippling MCP servers with broader action coverage. These are built and maintained by those vendors, and they need their account and their pricing on top of your Rippling one.
With one connected, an AI client can typically:
- Look up people — pull an employee’s title, department, manager, or start date from the live directory instead of a stale spreadsheet.
- Read time off — check leave requests and balances, or ask who’s out on a team next week.
- Read org structure — traverse departments and reporting lines, or pull headcount for a planning conversation.
- Summarize — “which departments grew most this quarter?” answered from real records rather than a guess.
It’s genuinely useful for ad-hoc questions. Note the shape of that list, though: it’s mostly reading. The sensitive write paths in an HR system — running payroll, changing compensation, terminating someone — are not things you want a chat window reaching for, and most of these servers sensibly don’t go there.
The gate you’ll hit first: an admin has to mint the token
This is the part that stops most people, and it has nothing to do with MCP. Every one of these servers authenticates with a Rippling API token, and Rippling’s docs are explicit about how those work:
- Tokens are created in the admin app, under Tools > Developer > API Tokens. If you’re a regular employee, you don’t have this. Someone with an admin permission profile has to make it for you.
- A token inherits the permission profile of whoever created it, intersected with the scopes chosen at creation. A token can only ever see data that both the owner’s profile and the token’s scopes allow. If a scope wasn’t granted, the API returns
nullwhere the data would be, rather than an error — a quietly confusing failure mode. - It’s a bearer token you paste into a config file. Any request made with it “appears as the owner making the request,” so treat it like a password. There is no per-action consent prompt.
- It dies on its own. Rippling automatically revokes a token if it goes unused for more than 30 days, or if its owner leaves the company. For a connector you only reach for occasionally, that’s a real gotcha — the setup you did in March may simply be dead in May.
That last pair is worth sitting with before you wire an AI chat into an HR system. You’re handing a long-lived credential that acts as a named admin to a client, and every lookup it makes is that admin looking. Scope it to the narrowest thing that does the job, and if you’re the one holding it, know that your token’s reach is your whole permission profile.
Where the Rippling MCP stops
Even setting aside which server to trust, the same limits show up:
- It only works inside a chat you start. Close the window and nothing happens. Nothing is watching the time-off queue or the new-hire list for you.
- No triggers. A time-off request landing, a new hire’s start date arriving, someone’s last day, a role change — none of these can start anything through MCP. There’s no “when this happens in Rippling, do that.”
- It’s one app at a time. A Rippling MCP server knows Rippling. Getting a new hire’s details into your calendar, a Slack welcome, and an onboarding checklist means wiring up a separate server for each and hoping your client can juggle them in one turn.
- You own the plumbing and the account risk. No vendor support line, no one reviewing what a community server does with an admin token, and a 30-day expiry clock you’re responsible for noticing.
So a Rippling MCP server is a way to ask Rippling things from a chat. It is not a way to make Rippling run — to have work happen on a schedule or in reaction to an event, across the other tools an employee’s week touches.
Running Rippling work that doesn’t need a chat open
That “run on its own, across apps” gap is exactly where Carly fits. Carly connects to Rippling natively and to the ~260 other apps it supports, plus anything with a public API through your own key — no community server to vet, no config file to babysit. The difference from MCP is the important part: Carly’s workflows are triggered and scheduled, so Rippling work happens whether or not anyone has a chat window open.
Carly stays on the same ground the connector covers — the directory, time off, and org data. She reads it, and she acts on it in your other tools:
- Every Monday → pull who’s out this week from Rippling and post the list to the team’s Slack channel.
- When a new hire’s start date is a week out → create the onboarding tasks, book the manager’s intro meeting on the calendar, and send the welcome email.
- Before you propose meeting times → check Rippling for approved time off so you don’t offer a slot when half the team is away.
You can also just ask. Text or email Carly “what’s my PTO balance?” or “who’s out on the product team this week?” and get an answer back without opening the admin panel — the same ad-hoc lookups an MCP server gives you, minus the server.
The non-AI steps — the moving, matching, and routing between apps — are free and unlimited, the Zapier-style backbone of the workflow. The AI steps (drafting, summarizing, deciding) start at $35/month. You describe the outcome in plain language and Carly wires up the Rippling connection and everything downstream.
If you just want to interrogate the directory from a chat and you can get an admin to mint you a token, a third-party MCP server is the closest thing available. If you want Rippling activity to actually trigger something — on a schedule, in reaction to an event, across every app a new hire or a day off touches — that’s the job no Rippling MCP server was built for.
FAQ
Does Rippling have an official MCP server?
No. Rippling’s developer portal covers custom solutions, the REST API, App Shop integrations, and an SDK — there’s no MCP server among them, and Rippling AI is built into the product rather than exposed to outside AI clients. The servers you’ll find are community projects like bifrost-mcp/rippling-mcp or commercial third-party ones from vendors like StackOne, all calling Rippling’s REST API. Treat any listing that calls one of them “official” as wrong.
Can I connect Rippling to Claude or ChatGPT? Only through a third-party MCP server plus a Rippling API token an admin creates for you. There’s no official Rippling connector for Claude or ChatGPT, and no OAuth “sign in with Rippling” flow for AI clients the way some CRMs offer.
Do I need to be a Rippling admin to use a Rippling MCP server? Effectively, yes. API tokens are created under Tools > Developer > API Tokens in the admin app, and a token can only reach data allowed by both its creator’s permission profile and its selected scopes. A regular employee can’t mint one for the whole directory.
Why did my Rippling MCP connection stop working?
Most likely the token expired. Rippling automatically revokes API tokens that go unused for more than 30 days, or whose owner has been terminated. If lookups return null instead of failing outright, that’s usually a missing scope rather than an expired token.
Can a Rippling MCP server trigger automations? No. MCP is request/response inside an AI chat — it has no triggers and nothing runs when the conversation is closed. For event- or schedule-driven Rippling work across apps, you need a workflow tool like Carly rather than an MCP server.
Can I connect Rippling to AI without coding or hosting a server? Yes. You don’t have to vet a community server or run anything. Carly connects to Rippling for you and lets you build the automation in plain language — describe what you want to happen and it wires up the Rippling connection and the other apps involved, with no server to host and no code to write.
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."
