# Set up an MCP connector

> Install and add MCP connectors to MCP Gateway so your organization can manage access to supported MCP connectors in Rippling.

Install a connector from the catalog, or add a custom MCP server. After it is installed, grant access so people in your organization can use it.

Built-in connectors can authorize with Rippling’s OAuth app, a custom OAuth app, or a personal access token (PAT) or API key. Some register automatically. Others need an app or credential from an admin. See [Overview of the MCP Gateway](https://developer.rippling.com/documentation/rippling-platform/mcp-gateway/overview).

* * *

## Requirements

-   You are an **MCP Gateway admin**, or you have permission to manage connectors.

* * *

## Built-in connectors

1.  From the sidebar, go to **IT** > **MCP Gateway**.
2.  Click **Add connector**.
3.  Select a connector.
4.  Choose an authorization method. The options depend on the connector:
    -   Rippling OAuth connector (recommended)
    -   Custom OAuth app
    -   Personal access token (PAT) or API key
5.  For Rippling OAuth, or when the connector registers an OAuth app for you, click **Connect** and authorize the account.
6.  For a custom OAuth app, API key, or PAT, click **Continue** and enter the credentials. Use the provider’s documentation to create the OAuth app or token.

The connector status changes to **Installed**.

* * *

## Custom connectors

Use a custom connector when the MCP server is not in the catalog.

1.  From the sidebar, go to **IT** > **MCP Gateway**.
2.  Click **Add connector**.
3.  Select **Custom MCP connector**.
4.  Paste the server endpoint into **Connector URL**. Remote URLs usually end with `/mcp`, `/mcp/sse`, or `/sse`.
5.  Review the details Rippling reads from that URL. The fields depend on the authentication mode.
6.  To change a detail, click **Edit**. If the server supports more than one mode, choose one. Click **Save**, then **Add and install**.

The URL is locked after the connector is created. To use a different URL, create a new connector.

* * *

## Grant access

An installed connector stays unavailable until an access assignment includes the people who should use it.

1.  Open **IT** > **MCP Gateway** and select the connector.
2.  Open **Access assignments**, then choose **Assign group** or **Assign individual**.
3.  Choose who gets access. Group assignments use Supergroups, which stay current as attributes such as department, location, and employment status change.
4.  Click **Next**, choose the tools those people can use, and click **Assign**.

A connector can have more than one assignment, each with a different set of tools. If someone belongs to two groups, the assignment with the lowest priority number applies. An individual assignment overrides group assignments.

To assign tools on the Rippling MCP and connect an AI client, see [Set up the Rippling MCP](https://developer.rippling.com/documentation/rippling-platform/rippling-mcp/setup).

* * *

## See also

-   [Overview of the MCP Gateway](https://developer.rippling.com/documentation/rippling-platform/mcp-gateway/overview)
-   [List an MCP server in the Rippling AI directory](https://developer.rippling.com/documentation/rippling-platform/mcp-gateway/rai-directory)
-   [Overview of the Rippling MCP](https://developer.rippling.com/documentation/rippling-platform/rippling-mcp/overview)
-   [Rippling MCP tools](https://developer.rippling.com/documentation/rippling-platform/rippling-mcp/tools)
-   [MCP troubleshooting & FAQs](https://developer.rippling.com/documentation/rippling-platform/rippling-mcp/troubleshooting)

Source: https://developer.rippling.com/documentation/rippling-platform/mcp-gateway/setup

> For the complete documentation index, see [llms.txt](https://developer.rippling.com/llms.txt). Public pages have a Markdown version at the same URL with .md added.