Is this an official Rippling MCP server?

No. It is Memtro's MCP server with Memtro's Rippling connector behind it: the connector reads Rippling through its API with the credentials you connect on Dashboard → Connections, and Rippling publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Rippling?

Only when you ask, and only what it has been granted: request time off for a worker (pending goes to approvers, approved records leave already agreed); approve, reject or cancel a leave request; change the dates, hours, leave type or comments of a pending leave request; create a department. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

MCP server · People and HR

Rippling MCP server

Rippling in any MCP client, through Memtro: Rippling does not publish this server. Memtro's Rippling connector reads Rippling through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.

What the model can do

Rippling HR: workers with title, department, manager, status, employment type and start date, departments, leave requests and leave types. When asked it can request time off for a worker, approve, reject or cancel a leave request, edit a pending one, and create a department. Never reads pay, SSN, date of birth, addresses or phone numbers.

Reads

rippling_list_workersPeople in Rippling (workers): name, work email, title, department, manager, status (INIT, HIRED, ACCEPTED, ACTIVE, TERMINATED), employment type…
rippling_get_workerOne Rippling worker by id: name, work email, title, department, manager, status, employment type, start and end date.
rippling_list_departmentsDepartments in Rippling with their parent department and reference code.
rippling_list_leave_requestsLeave (time-off) requests in Rippling, newest first: who, leave type, paid or not, start and end, hours requested, status (PENDING, APPROVED…
rippling_list_leave_typesLeave types in Rippling (Vacation, Sick…): id, name, type, whether paid, and whether another system manages it.

Acts, when you ask

These change something in Rippling. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

rippling_create_leave_requestRequest time off in Rippling for one worker, only when the person asked.
rippling_set_leave_statusApprove, reject or cancel a Rippling leave request, only when the person asked.
rippling_update_leave_requestChange a PENDING Rippling leave request's dates, partial-day hours, leave type or comments, only when the person asked.
rippling_create_departmentCreate a department in Rippling, optionally under a parent department, only when the person asked.

Connect it

First connect Rippling on Dashboard → Connections, then add Memtro to your client once. The Rippling tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

Claude Code

The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

Cursor

Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Claude Desktop

Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…

OpenCode

A remote server in opencode.json.

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Pi

One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.

Any other client

Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Rippling connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

› Who reports to Priya Nair?
› Who is on leave next week?
› Which leave requests are waiting for approval?
› What is Dan Fletcher's title, and who is his manager?
› Approve Dan Fletcher's pending leave for 3 to 5 December

Questions

Is this an official Rippling MCP server?: No. It is Memtro's MCP server with Memtro's Rippling connector behind it: the connector reads Rippling through its API with the credentials you connect on Dashboard → Connections, and Rippling publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
What does it cost?: Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
Can it change anything in Rippling?: Only when you ask, and only what it has been granted: request time off for a worker (pending goes to approvers, approved records leave already agreed); approve, reject or cancel a leave request; change the dates, hours, leave type or comments of a pending leave request; create a department. Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
Which clients work?: Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.