Skip to main content
Book a demo

Connect Rippling to OpenCode

Give OpenCode governed access to Rippling’s 1 tools through Runlayer, with identity, policy, scanning, and audit on every call.

Book a demo OpenCode setup guide

Set up

Add Rippling to OpenCode in four steps

Admins approve the server once. Everyone in OpenCode then gets it through the same governed connection.

  1. 1

    Add Rippling to Runlayer

    Rippling isn’t in the Runlayer catalog yet, so an admin adds it by its MCP server URL.

    Adding a connector manually
  2. 2

    Connect OpenCode to Runlayer

    Users add the Runlayer Plugin to OpenCode by hand using Runlayer’s generic MCP steps. OpenCode reaches Rippling’s 1 tool through the Runlayer Plugin’s search and execute tools instead of listing each one.

    OpenCode setup guide
  3. 3

    Sign in to Rippling

    Sign in the way Rippling requires. Runlayer holds the credentials so they stay out of the client’s configuration.

  4. 4

    Use Rippling from OpenCode

    Rippling’s approved tools appear in OpenCode. Every call is checked against policy and recorded.

Tools

1 Rippling tools in OpenCode

Runlayer policy decides which of these OpenCode users can call.

  • Code

    Async () => {...};never async (codemode).

Control

What Runlayer can see and stop in OpenCode

Some controls apply to every client at the gateway. Others depend on what OpenCode exposes to Runlayer.

  • Gateway policy (available)

    Every Rippling call from OpenCode passes through Runlayer, where your policies can allow, alert, mask, or block it.

  • Audit trail (available)

    Each call is recorded with the user, OpenCode as the client, the tool, and the policy and scanner decisions.

  • Native enforcement adapter (not available)

    Runlayer has no device-side adapter for OpenCode yet, so control happens at the gateway.

Frequently asked questions

Connect more

Find another combination