Skip to content

Rippling MCP connector

The Rippling connector brings your workers, departments, work locations, employment types, and business partners to Claude, ChatGPT, Cursor, and the Elaichi Agent through one governed endpoint, so each person asks questions of live HR records inside their own Rippling access.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Rippling to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Rippling once

  1. Open Connections, choose Add connection, and pick Rippling.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Rippling API key. One person generates a token in Rippling and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

rippling
Rippling
360learning
7shifts
ADP Workforce Now
Altera Payroll
BambooHR
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Rippling MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Rippling MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Rippling MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Rippling to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Rippling through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • People

    Answer who reports where, in seconds

    Ask which department a worker sits in, which team they belong to, and which office they are based at, and get the answer from the live Rippling record instead of opening three screens.

  • IT

    Check a worker before granting access

    Confirm a person's employment type, department, and work location in Rippling before provisioning software or hardware, so contractors and full-time staff get the right setup.

  • Finance

    Map headcount by department and location

    Pull the current list of Rippling workers grouped by department, employment type, and work location to check budgets and allocations against what HR actually shows.

  • Operations

    Keep business partner records tidy

    List the business partners and partner groups set up in Rippling, add a new partner when a vendor relationship starts, and remove one when it ends.

  • Managers

    Look up a team roster before a review

    Get the members of a Rippling team along with their departments and work locations, so you walk into planning or a review with the current roster rather than last quarter's spreadsheet.

  • People

    Extend Rippling with the fields you track

    See which custom fields already exist in Rippling and add a new custom object field when the organization starts tracking something new, without asking an engineer.

Try asking

  • “List all workers in the Engineering department”
  • “Which work locations have the most workers right now”
  • “Show employment types across every Rippling team”

See all 56 Rippling tools below

Compare

Elaichi vs Zapier MCP vs Composio for Rippling

All three can connect Rippling to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for Rippling, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over Rippling tools Allow or restrict single Rippling tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per Rippling call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

Rippling tools for your AI agents

56 tools are ready to call through Elaichi's MCP endpoint the moment you connect Rippling, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Rippling gets you

6 screens from the product, each doing one job for your Rippling account.

The agent

Ask about workers, get answers from Rippling.

Type a question in plain language and read live Rippling workers and departments.

  • workers
  • users
  • departments
  • teams

Ask Elaichi to work across your apps.

List all workers in the Engineering department

Which work locations have the most workers right now

Show employment types across every Rippling team

Also runs in Claude, ChatGPT or Cursor

MCP clients

One Rippling endpoint for every MCP client.

Claude, ChatGPT and Cursor connect over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

• Connected 4 minutes ago
Cursor
M

Megan Brooks

• Connected 2 hours ago
ChatGPT
R

Ryan Hayes

• Connected Yesterday

Tool catalog

All 56 Rippling tools are ready to call.

Workers, teams, departments, work locations and employment types, with no custom code.

  • List all Rippling users
  • Get single Rippling user by ID
  • List all Rippling teams
  • Get single Rippling team by ID
ElaichiTools
Tool Action Description
List all Rippling users List List users in Rippling. Returns id, created_at, updated_at, active, username, name, display_name, emails, phone_numbers, addresses, photos, preferred_language, locale, timezone, and number fields for each user.
Get single Rippling user by ID Get Get a specific user in Rippling by id. Returns id, created_at, updated_at, active, username, name, display_name, emails, phone_numbers, addresses, photos, preferred_language, locale, timezone, number, and any redacted_fields with reasons in the response.
List all Rippling teams List List teams in Rippling. Returns id, created_at, updated_at, parent_id, parent, and name fields for each team.
Get single Rippling team by ID Get Get a specific team in Rippling. Requires id. Returns id, created_at, updated_at, parent_id, parent, name, and any redacted_fields specified in __meta.
List all Rippling companies List List companies in Rippling. Returns id, created_at, updated_at, name, legal_name, primary_email, legal_entities and parent_legal_entity with key details like country, entity level, registration date, and addresses for each company.

Toolboxes

Every team gets its own Rippling toolbox.

Curate one toolbox per team so People, Finance and IT see different Rippling tools.

  • People Ops
  • Finance
  • IT
  • Recruiting
ElaichiToolboxes
Name Source template Tools Created

People Ops toolbox

Rippling · workers and employment types

Rippling starter 18 Mar 4, 2026

Finance toolbox

Rippling · headcount and departments

— 9 Mar 2, 2026

IT toolbox

Rippling · users and access

— 24 Feb 27, 2026

Recruiting toolbox

Rippling · teams and open roles

Rippling starter 6 Feb 19, 2026

Managers toolbox

Rippling · direct reports and teams

— 31 Jan 30, 2026

Compliance toolbox

Rippling · work locations and custom fields

— 12 Jan 22, 2026

Shared connections

Teammates use Rippling without seeing a credential.

See who connected each Rippling account and how many teams and members share it.

  • People Ops
  • Finance
  • IT
  • Recruiting EMEA
ElaichiConnections
Connection Scope Status Access
RI

Rippling (People Ops)

Connected by Emily Carter

Personal • Active 1 team · 6 members
RI

Rippling (Finance)

Connected by Jake Morgan

Organization • Active 3 teams · 24 members
RI

Rippling (IT)

Connected by Megan Brooks

Organization • Active 2 teams · 11 members
RI

Rippling (Recruiting EMEA)

Connected by Tyler Reed

Personal • Needs re-auth 1 team · 3 members
RI

Rippling (Managers)

Connected by Ryan Hayes

Personal • Active Not shared
RI

Rippling (Compliance)

Connected by Ashley Parker

Personal • Active 2 teams · 9 members

Audit log

Every Rippling call is on the record.

When, who, what happened, type and resource, appended for each Rippling request.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emily Carter

emily.carter@northwind.io

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

Jake Morgan

jake.morgan@northwind.io

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

M

Megan Brooks

megan.brooks@northwind.io

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

T

Tyler Reed

tyler.reed@northwind.io

Rippling Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

R

Ryan Hayes

ryan.hayes@northwind.io

Rippling Workers Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

A

Ashley Parker

ashley.parker@northwind.io

Rippling Workers List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires, Rippling work gets done.

Fetch workers, group them, draft a digest, approve it, then post back to Rippling.

Rippling digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch workers

    Rippling

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Rippling

    Queued

Collections and dashboards

Rippling headcount numbers arrive before you ask.

Four metrics, 14 days of new workers and a team breakdown, counted not generated.

Rippling health

Refreshed 4 minutes ago · every 15 minutes · from the workers collection

Live

Workers

1,284 ↓ 12%

Users

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Workers created

Last 14 days

By team

Share of activity

People Ops 34%

Finance 27%

IT 21%

Recruiting EMEA 18%

FAQ

Frequently asked questions

How do I connect Rippling to Claude?

First connect Rippling in Elaichi, which asks you to paste a Rippling API key, since Rippling connects with an API key rather than an app sign-in. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude asks you to sign in to Elaichi, and from then on it can work with your Rippling records.

Does Rippling work with ChatGPT and Cursor as well as Claude?

Yes. Once Rippling is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Rippling once and every client you use picks it up.

What can an AI agent actually do with my Rippling data?

With Rippling connected, an agent can look up workers and users, tell you which department, team, work location, and employment type a person belongs to, list the companies and departments in your organization, and check which custom fields exist. It can also add or remove business partners and partner groups and create a new custom object field. Rippling exposes a lot of actions, so short concrete asks such as "who is in the Berlin office" work better than long multi-part sentences.

Does connecting Rippling give the AI access to everyone's HR records?

No. Every request to Rippling runs inside the access of the person who signed in, so an agent can only see the workers, departments, and business partners that person can already see in Rippling. Elaichi can narrow that access further with roles and restrictions, but it never widens it beyond what Rippling itself allows.

Can my team share one Rippling connection?

Yes. One person connects Rippling in Elaichi with the API key and shares the connection with a team, and nobody else on the team ever handles the key. Each teammate still signs in to Elaichi as themselves, so every Rippling lookup or change in the audit log is tied to a named person, not to a shared account.

Can I stop an agent from deleting or changing things in Rippling?

Yes. Restrictions in Elaichi apply per action, so you can allow reading workers and departments in Rippling while blocking the actions that create or delete business partners, partner groups, or custom fields. A blocked action is never shown to Claude, ChatGPT, Cursor, or any other client at all, so no prompt, however worded, can reach it.

What happens to a Rippling connection when someone leaves?

When you offboard a person in Elaichi, their access to Rippling through every AI client ends at once. A shared Rippling connection keeps working for everyone else on the team, so nobody has to reconnect. If you want to remove Rippling entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client in one step.

Does the Rippling MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. Rippling is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for Rippling?

Yes. Both let Claude, ChatGPT or Cursor use Rippling. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Rippling call.

How is Elaichi different from Composio for Rippling?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Rippling: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put Rippling in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.