home / mcp / rippling mcp server

Rippling MCP Server

Queries Rippling data, manages leave, shows company structure, and more via a structured MCP gateway.

Installation
Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "bifrost-mcp-rippling-mcp": {
      "url": "https://api.rippling.com/platform/api",
      "headers": {
        "RIPPLING_BASE_URL": "https://api.rippling.com/platform/api",
        "RIPPLING_API_TOKEN": "YOUR_API_TOKEN"
      }
    }
  }
}

You can connect AI agents or LLMs to your Rippling workspace through this MCP server to query employees, manage leave, view company structure, and more. It provides a structured, token-authenticated gateway to Rippling data and actions, with built-in rate limit handling and AI-friendly errors to help you build effective automation and assistants.

How to use

Use this MCP server with an MCP client to access Rippling data and actions. You will authenticate with a Rippling API token and run the MCP server as a local or remote service that your AI tools can query via the MCP protocol. The server exposes tools across six domains, letting you retrieve company details, employee data, organization structure, leave management, groups, and activity events. When you call a tool, the server validates input, makes authenticated requests to Rippling, handles rate limits, and returns structured results or actionable errors.

How to install

Prerequisites: you need Node.js and npm installed on your machine. Ensure you have a Rippling API token ready before starting.

Install dependencies for the MCP server project in your working directory.

Create and configure the MCP connection in your client configuration as shown in the example below.

Run in development mode using your Rippling API token.

# Install dependencies
npm install

# Run in development mode (replace YOUR_API_TOKEN with your actual token)
RIPPLING_API_TOKEN=YOUR_API_TOKEN npm run dev
```} ]},{

Configuration details

Set a Rippling API token and, optionally, a base URL for the Rippling API. The base URL defaults to the official Rippling platform API.

{
  "mcpServers": {
    "rippling": {
      "command": "npx",
      "args": ["-y", "rippling-mcp-server"],
      "env": {
        "RIPPLING_API_TOKEN": "your_api_token_here"
      }
    }
  }
}
```} ]},{

Security and hosting notes

Use a securely generated Rippling API token and restrict token permissions to the minimum necessary for your automation. Monitor rate limit headers in responses to adjust usage and avoid throttling. The server accepts a base URL parameter to point to the intended Rippling API environment, including sandbox setups if provided.

Development

Prime commands you will likely use during development are shown here. Install dependencies, run in development mode with your token, and run tests or build for production.

# 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 / lint
npm run lint
```}]} ,{

How it works

The MCP server wraps the Rippling API, exposing tools that let you retrieve and manage data via the Model Context Protocol. It validates inputs, makes authenticated API calls, handles rate limits, and returns structured results or clear, actionable errors.

Limitations

Employee endpoints are read-only due to Rippling API constraints. The fields returned for each employee depend on the API token permissions. Rate limits are enforced by Rippling and can be observed via response headers. Processing leave requests requires appropriate admin permissions.

License

MIT

Contributing

Contributions are welcome. Open issues and pull requests to improve functionality, add tools, or fix bugs.

Available tools

get_company

Get company details including name, address, and locations.

list_departments

List all departments with their hierarchical structure.

list_work_locations

List all work locations and addresses.

list_employees

List active employees with pagination.

get_employee

Get details for a specific employee by ID.

list_all_employees

List all employees, including terminated records.

search_employees

Search employees by name, email, title, or department.

list_teams

List teams and subteam relationships.

list_levels

List position levels such as IC, Manager, and Executive.

list_custom_fields

List custom field definitions.

get_leave_balances

Get PTO or sick leave balances for an employee.

list_leave_requests

List leave requests with filters for status, date, and requester.

process_leave_request

Approve or decline a pending leave request.

list_leave_types

List all leave types configured for the company.

list_groups

List all groups.

create_group

Create a new group with members.

update_group

Update group name or members.

delete_group

Delete a group.

get_company_activity

Get company activity events such as hires, changes, and terminations.