The MCP Gateway is where you manage MCP connectors for Rippling AI and third-party AI clients. It controls which MCP tools and data sources those clients can reach, and which people and groups can use them.
When the gateway is configured, MCP traffic flows through it. Each tool call is allowed or denied based on the access an admin assigned.
MCP connectors
An MCP connector links Rippling AI or a third-party AI client to an MCP provider. After a connector is installed, employees can add it to an AI client from My IT > MCP connectors.
For example, a Gmail connector lets people use Gmail from Claude, ChatGPT, or Rippling AI.
Connector types
The gateway supports two kinds of connectors:
- Built-in connectors from the connector catalog
- Custom connectors for an MCP server your organization provides
Authentication
Built-in connectors use one of these methods:
- Rippling’s OAuth app, with no extra OAuth app for the admin to create
- An OAuth app the admin creates with the MCP provider
- An API key or personal access token (PAT)
Custom connectors use the authentication modes the server supports. Available options depend on the connector and the provider.
Auto-installed connectors
Some catalog connectors install automatically and start with an Everyone access assignment. Admins can change or remove that assignment. Each person still connects the connector from My IT > MCP connectors.
Access
Access is granted or revoked with assignment rules on each connector. A connector can have more than one rule, and each rule can allow a different set of tools. See Grant access.
Who can manage connectors
The MCP Gateway has three permission levels. Manage them from MCP Gateway > Permissions.
- MCP Gateway admins can manage every connector and assign access. This role is set in the Permissions app.
- Add connector lets someone install connectors from the catalog. The installer becomes an admin of each connector they add.
- View or manage all connectors lets someone view or manage current and future connectors. This role cannot assign access.
AI clients
These clients can use connectors set up in the MCP Gateway:
- Rippling AI (no client configuration required)
- Cursor
- VS Code
- Claude Desktop
- Claude Code
- Windsurf
- Goose
- Codex CLI
- ChatGPT (web)
- ChatGPT Desktop (Codex)
- Microsoft Copilot Studio
- Gumloop
- Raycast
- Warp
- Gemini CLI
- TypeScript SDK
- Python SDK
Rippling AI can use a connector after it is connected as a plugin.
For any other client, follow the in-product steps and paste the MCP configuration snippet into that client’s configuration file.
Rippling MCP
The Rippling MCP lets an external AI client read Rippling data and take actions in Rippling. Set it up like any other connector. Tool calls return data only when the company has a Rippling AI trial or an active Rippling AI subscription.
See Overview of the Rippling MCP.