create_group
Create a new group with specified members
LABSCO SUMMARY
You can read the whole organisation here but write almost none of it: process_leave_request and the four group tools are the only calls that change anything.
Employees, departments, locations, levels and custom fields are read-only, so the question when connecting this is mostly what the token can see rather than what it can damage. The identifiers do not line up across those surfaces — get_employee takes an employeeId while get_leave_balances takes a roleId — so a leave lookup is not a straight continuation of an employee lookup. search_employees states that it fetches all active employees and filters client-side, which makes it a convenience wrapper over list_employees rather than a server-side query, and worth avoiding on a large directory.
What it is
A Rippling client covering the company directory, employee records, leave balances and requests, group membership, and the company activity feed.
What you get
- Directory reads at company scale: get_company returns name, address and locations, list_departments returns the departmental hierarchy, list_work_locations returns addresses, list_teams returns subteam relationships, and list_levels returns position levels such as Manager, Executive and Individual Contributor.
- Employee lookups shaped by what you already know: list_employees pages through active staff with name, title, department and work email; list_all_employees includes terminated staff for full workforce history and accepts an ein; search_employees matches a query against name, email, title or department; get_employee returns one record by employeeId.
- Leave handled end to end: get_leave_balances returns PTO, sick leave and other balances for a roleId, list_leave_requests filters by status, a startDate to endDate range and requestedBy, list_leave_types returns what the company has configured, and process_leave_request approves or declines a pending request.
- Group membership as a writable surface: list_groups reads the groups, create_group creates one from named userIds under a spokeId, update_group changes the name or the members, and delete_group removes it by groupId.
- list_custom_fields returns the custom field definitions configured in Rippling, and get_company_activity returns events such as employee changes, onboarding and offboarding across a date range.
Requirements
A Rippling API token, supplied as RIPPLING_API_TOKEN.
Setup effort
One command plus a key — npx -y rippling-mcp-server, then supply credentials
USE CASES
01
Working out who someone is and where they sit
Search the directory by name, email, title or department, then open the one you meant and read the department and team structure around them. Terminated staff are on a separate call, so a normal search stays current.
02
Clearing the leave requests waiting on you
List what is pending, check the requester's remaining balance against the leave type before deciding, and approve or decline it in the same session.
03
Keeping group membership current
See the groups that exist, create one with its members, and edit or remove it as the team changes — without opening the admin console.
19 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
delete_group
Delete a group by its ID
get_company
Get current company details including name, address, and locations
get_company_activity
Get company activity events such as employee changes, onboarding, and offboarding
get_employee
Get detailed information for a specific employee by their ID
get_leave_balances
Get leave balances for a specific employee including PTO, sick leave, and other leave types
list_all_employees
List all employees including terminated ones. Useful for complete workforce history.
list_custom_fields
List custom field definitions configured in Rippling
list_departments
List all departments in the organization with hierarchical structure
list_employees
List active employees with pagination. Returns employee details including name, title, department, and work email.
list_groups
List all groups in the organization
list_leave_requests
List leave requests with optional filters for status, date range, and requester
list_leave_types
List all leave types configured for the company (PTO, sick, etc.)
list_levels
List position levels (e.g. Manager, Executive, Individual Contributor)
list_teams
List all teams with subteam relationships
list_work_locations
List all work locations with addresses
process_leave_request
Approve or decline a pending leave request
search_employees
Search employees by name, email, title, or department. Fetches all active employees and filters client-side.
update_group
Update an existing group's name or members
BEFORE YOU INSTALL
What to know first
Tools you get
19 tools when we connected. Employee data is read-only because of Rippling's API; writes are process_leave_request and group create, update and delete. Leave approval needs admin permissions, and your token's permissions decide which employee fields return.
Requires
- npx on PATH
- RIPPLING_API_TOKEN in your environment
Where it runs
The documented client runs the server on your machine.
CONTEXT COST
Light Standing cost
Rated by the size of the 19 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y rippling-mcp-serverMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"rippling": {
"command": "npx",
"args": [
"-y",
"rippling-mcp-server"
],
"env": {
"RIPPLING_API_TOKEN": "<YOUR_RIPPLING_API_TOKEN>"
}
}
}
}
