Rippling MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| RIPPLING_BASE_URL | No | API base URL. For sandbox/testing, set to https://sandbox.rippling.com/api/platform/api. | https://api.rippling.com/platform/api |
| RIPPLING_API_TOKEN | Yes | Your Rippling API token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_companyB | Get current company details including name, address, and locations |
| list_departmentsC | List all departments in the organization with hierarchical structure |
| list_work_locationsB | List all work locations with addresses |
| list_employeesB | List active employees with pagination. Returns employee details including name, title, department, and work email. |
| get_employeeC | Get detailed information for a specific employee by their ID |
| list_all_employeesA | List all employees including terminated ones. Useful for complete workforce history. |
| search_employeesA | Search employees by name, email, title, or department. Fetches all active employees and filters client-side. |
| list_teamsB | List all teams with subteam relationships |
| list_levelsC | List position levels (e.g. Manager, Executive, Individual Contributor) |
| list_custom_fieldsC | List custom field definitions configured in Rippling |
| get_leave_balancesB | Get leave balances for a specific employee including PTO, sick leave, and other leave types |
| list_leave_requestsC | List leave requests with optional filters for status, date range, and requester |
| process_leave_requestC | Approve or decline a pending leave request |
| list_leave_typesB | List all leave types configured for the company (PTO, sick, etc.) |
| list_groupsB | List all groups in the organization |
| create_groupC | Create a new group with specified members |
| update_groupC | Update an existing group's name or members |
| delete_groupC | Delete a group by its ID |
| get_company_activityC | Get company activity events such as employee changes, onboarding, and offboarding |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Most tools have distinct purposes targeting specific resources like employees, groups, leave, or company data. However, list_employees and list_all_employees could cause confusion as both list employees, with the latter including terminated ones, which might lead to misselection if the agent doesn't carefully read descriptions.
Tool names follow a consistent verb_noun pattern throughout, such as create_group, list_employees, get_company, and process_leave_request. All use snake_case with clear, predictable naming conventions, making the set easy to navigate.
With 19 tools, the count is slightly high but reasonable for an HR/employee management domain, covering groups, employees, leave, and company details. It's well-scoped without being excessive, though it borders on feeling heavy compared to typical 3-15 tool ranges.
The tool surface provides comprehensive coverage for HR operations, including CRUD for groups, extensive employee listing and search, leave management with balances and requests, and company/department/team structures. No obvious gaps exist for core workflows in this domain.