Full read-write Claude connector for Rippling
Let Claude file time off and push candidates into onboarding in Rippling
Stop clicking through HR forms to file time off, push a new candidate into onboarding, or pull a roster. Claude does the workforce busywork where the data already lives in Rippling, and anything sensitive waits for your approval.
Rippling is a workforce platform that unifies HR, payroll, benefits, IT, and spend in one system of record. People want Claude to do more than look up an employee: to file and approve time off, push a candidate into onboarding, and pull people data where it already lives.
What is a Rippling MCP server?
A Rippling MCP server is a small hosted service that exposes Rippling's data and actions to Claude over the Model Context Protocol, so Claude can people, time, and pay inside your own account. We build it as a custom connector with separate read and write tools, and destructive actions stay gated behind your approval.
What can Rippling's current connector do today?
Today, Rippling has no broadly available Claude connector, and any directory-style integration tends to be read-leaning or a thin slice of the platform. Claude can be handed exported data to reason over, but it cannot file time off, push a candidate into onboarding, or pull roster data inside Rippling without a purpose-built connector.
What does full read-write Rippling access unlock?
Scoped Rippling access lets Claude create and approve time-off requests, create a new employee, push a candidate into onboarding, and read employee, compensation, and roster data. The HR busywork that used to mean clicking through forms happens where the workforce data already lives, with you approving anything sensitive.
- Look up an employee's job title, department, manager, or work location
- Push a candidate into the onboarding flow for a new hire
- Create or approve a time-off request and check remaining balances
- Read an employee's current compensation alongside their record
- Create a new employee record in Rippling
- Pull a roster or headcount report and draft the summary for your team
Can Claude update employee fields like title in Rippling?
Not directly. Rippling's public API has no endpoint to change an existing employee's title, department, manager, or location, so Claude reads those fields rather than editing them. A connector can still create a new employee and pull people data through scoped tools that act as your account, with no form clicking by hand.
Can Claude start onboarding for a new hire in Rippling?
Claude can push a candidate into the onboarding flow for a new hire, and create or approve time-off requests along the way. These run as scoped actions through your account, so Claude can only push candidates and touch the records your own Rippling permissions already allow.
Can Claude change compensation in Rippling?
No. Rippling's public API exposes compensation as read-only, so Claude can read an employee's current pay alongside their record but cannot stage or commit a pay-rate or comp change. For sensitive write actions it does support, like approving time off, you decide which run automatically and which need a confirmation step first.
How a Rippling connector works
We build a small MCP server that authenticates to Rippling with OAuth and the narrowest scopes the work needs. Read tools (look up employees, pull reports) and write tools (file or approve time off, push a candidate into onboarding, create an employee) are kept separate, and sensitive or irreversible actions require your confirmation. Claude only ever has the access your own Rippling account already has.
Frequently asked questions
Can Claude update employee fields like title or department in Rippling?
Can Claude change compensation or run payroll in Rippling?
Does a Rippling connector give Claude more access than I have?
Related connectors
Tell us what you run. We'll build the connector.
Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.