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

Rippling MCP Server