Rippling MCP connector
The Rippling connector brings your workers, departments, work locations, employment types, and business partners to Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent through one governed endpoint, so each person asks questions of live HR records inside their own Rippling access.
- Connects with an API key
- Free 14-day trial
- No credit card
List all workers in the Engineering department
Working in Rippling with Elaichi
-
List all Rippling users
-
Get single Rippling user by ID
-
List all Rippling teams
How to connect Rippling to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Rippling MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
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 Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Rippling MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Rippling MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Rippling MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Rippling to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with Rippling through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Rippling is logged.
-
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”
What connecting Rippling gets you
6 screens from Elaichi, each doing one job for your Rippling account.
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, Cursor or Microsoft Copilot
The agent
Ask about workers, get answers from Rippling.
Type a question in plain language and read live Rippling workers and departments.
Copy the endpoint
AI apps
One Rippling endpoint for every MCP client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK and no shared API key.
Tool catalog
All 56 Rippling tools are ready to call.
Workers, teams, departments, work locations and employment types, with no custom code.
Toolboxes
Every team gets its own Rippling toolbox.
Curate one toolbox per team so People, Finance and IT see different Rippling tools.
Shared connections
Teammates use Rippling without seeing a credential.
See who connected each Rippling account and how many teams and members share it.
Audit log
Every Rippling call is on the record.
When, who, what happened, type and resource, appended for each Rippling request.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Rippling digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch workers
Rippling
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Rippling
Queued
Automations
A schedule fires, Rippling work gets done.
Fetch workers, group them, draft a digest, approve it, then post back to Rippling.
Rippling health
Refreshed 4 minutes ago · every 15 minutes · from the workers collection
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%
Collections and dashboards
Rippling headcount numbers arrive before you ask.
Four metrics, 14 days of new workers and a team breakdown, counted not generated.
For IT and engineering
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.
| 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 | Free for one person; $15 per user per month on Gold. | 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.
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.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 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 restricting the actions that create or delete business partners, partner groups, or custom fields. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, Cursor, Microsoft Copilot, or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot, 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, Microsoft Copilot, 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 of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot