Rippling MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Rippling MCP Server Who has pending leave requests that need approval?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Rippling MCP Server
An open-source Model Context Protocol (MCP) server for the Rippling HR/IT/Finance platform. Connect any AI agent or LLM to your Rippling workspace — query employees, manage leave requests, view company structure, and more.
Features
18 tools across 6 domains: Company, Employees, Organization, Leave, Groups, Activity
Bearer token auth — simple API token setup, no OAuth dance required
Rate limit aware — respects Rippling's rate limit headers
AI-friendly errors — structured error messages with actionable fix suggestions
TypeScript — full type safety, built with
@modelcontextprotocol/sdk
Related MCP server: Runn MCP Server
Quick Start
1. Get a Rippling API Token
Go to Rippling > Settings > API Tokens > Create API Token. Copy the token.
2. Configure in Claude Desktop
Add to your claude_desktop_config.json:
{
"mcpServers": {
"rippling": {
"command": "npx",
"args": ["-y", "rippling-mcp-server"],
"env": {
"RIPPLING_API_TOKEN": "your_api_token_here"
}
}
}
}3. Use It
Ask Claude things like:
"List all employees in Engineering"
"Who has pending leave requests?"
"Show me the company org structure"
"What's Alice's PTO balance?"
Tools Reference
Company
Tool | Description |
| Get company details (name, address, locations) |
| List all departments with hierarchy |
| List work locations and addresses |
Employees
Tool | Description |
| List active employees (paginated) |
| Get a specific employee by ID |
| List all employees including terminated |
| Search by name, email, title, or department |
Organization
Tool | Description |
| List teams and subteam relationships |
| List position levels (IC, Manager, Executive) |
| List custom field definitions |
Leave Management
Tool | Description |
| Get PTO/sick leave balances for an employee |
| List leave requests (filter by status, date, requester) |
| Approve or decline a pending leave request |
| List all leave types configured for the company |
Groups
Tool | Description |
| List all groups |
| Create a new group with members |
| Update group name or members |
| Delete a group |
Activity
Tool | Description |
| Get activity events (hires, changes, terminations) |
Configuration
Variable | Required | Default | Description |
| Yes | — | Your Rippling API token |
| No |
| API base URL |
For sandbox/testing, set RIPPLING_BASE_URL to https://sandbox.rippling.com/api/platform/api.
Development
# Install dependencies
npm install
# Run in development mode
RIPPLING_API_TOKEN=your_token npm run dev
# Run tests
npm test
# Build for production
npm run build
# Type check
npm run lintHow It Works
This server wraps the Rippling Platform API (V1) and exposes it through the Model Context Protocol. When an AI agent calls a tool, the server:
Validates the input using Zod schemas
Makes authenticated requests to the Rippling API
Handles rate limiting automatically
Returns structured JSON responses (or actionable error messages)
Limitations
Employee endpoints are read-only (Rippling API V1 restriction)
API token permissions determine which fields are returned per employee
Rate limits are enforced by Rippling (monitor via response headers)
Leave request processing requires appropriate admin permissions
License
MIT
Contributing
Issues and PRs welcome.
Available Tools
19 toolscreate_groupC
Create a new group with specified members
Inputs: name (required), spokeId (required), userIds (required).
delete_groupC
Delete a group by its ID
Inputs: groupId (required).
get_companyB
Get current company details including name, address, and locations
Inputs: no named parameters.
get_company_activityC
Get company activity events such as employee changes, onboarding, and offboarding
Inputs: startDate, endDate, limit.
get_employeeC
Get detailed information for a specific employee by their ID
Inputs: employeeId (required).
get_leave_balancesB
Get leave balances for a specific employee including PTO, sick leave, and other leave types
Inputs: roleId (required).
list_all_employeesA
List all employees including terminated ones. Useful for complete workforce history.
Inputs: limit, offset, ein.
list_custom_fieldsC
List custom field definitions configured in Rippling
Inputs: limit, offset.
list_departmentsC
List all departments in the organization with hierarchical structure
Inputs: limit, offset.
list_employeesB
List active employees with pagination. Returns employee details including name, title, department, and work email.
Inputs: limit, offset.
list_groupsB
List all groups in the organization
Inputs: no named parameters.
list_leave_requestsC
List leave requests with optional filters for status, date range, and requester
Inputs: status, startDate, endDate, requestedBy, +2 more.
list_leave_typesB
List all leave types configured for the company (PTO, sick, etc.)
Inputs: no named parameters.
list_levelsC
List position levels (e.g. Manager, Executive, Individual Contributor)
Inputs: limit, offset.
list_teamsB
List all teams with subteam relationships
Inputs: no named parameters.
list_work_locationsB
List all work locations with addresses
Inputs: no named parameters.
process_leave_requestC
Approve or decline a pending leave request
Inputs: requestId (required), action (required).
search_employeesA
Search employees by name, email, title, or department. Fetches all active employees and filters client-side.
Inputs: query (required), limit.
update_groupC
Update an existing group's name or members
Inputs: groupId (required), name, userIds.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Connect AI agents to 1000+ apps with managed authentication and tool-calling.
Search employee profiles, read profile fields and list HR tasks in Sapling HR.
Connect your AI assistant to your Peak HR portal: HR operations, people, documents and drafts.
PeopleHR MCP server for ChatGPT, Claude and any AI agent: list holiday requests, approve holiday request, decline holiday request, list employees, get employee planner, create task and run saved query in your own PeopleHR account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to PeopleHR yourself; Cotlet does not store your password and you need no PeopleHR API key. About the official PeopleHR API: PeopleHR has a REST API, the Access PeopleHR Integration API v4.0, but no official MCP server (checked 22 Oct 2026). The API covers 31 resources and 150 actions, mostly employee records, holiday and absence data, and every call needs an API key that an HR admin creates in Settings. Setup and FAQ: https://cotlet.dev/integrations/peoplehr-api-mcp-server
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to interact with BambooHR's API through natural language queries. Provides access to employee data, time off management, company files, and HR operations with comprehensive tools for workforce management.108 npm1MIT
- FlicenseNot gradedqualityNot gradedmaintenanceConnects AI assistants to the Runn.io resource planning platform to manage projects, people, assignments, and financial forecasts. It provides 37 tools for accessing real-time data and comprehensive reports with built-in caching and role-based access control.-
- AlicenseBqualityCmaintenanceEnables Claude, Cursor, and other MCP clients to query PeopleForce HRIS data (employees, time-off, recruitment) via 27 read-only tools.284MIT
- AlicenseNot gradedqualityDmaintenanceProvides 50+ tools for interacting with Rippling's HR platform, including employee management, payroll, time tracking, benefits, recruiting, learning, devices, groups, and custom objects, all through natural language.MIT