For AI agents: an index of this documentation is at https://developer.rippling.com/llms.txt. Public pages have a Markdown version at the same URL with .md added.

Skip to main content
Developer Resources
guide

List an MCP server in the Rippling AI directory

List your company's MCP server in the Rippling AI directory so eligible Rippling customers can discover and connect to it with Rippling AI.

Use with AI:Rippling AI ChatGPT Claude Cursor

Access to the Developer Program is gated behind a closed beta.

Rippling lists official, production-ready remote MCP servers. The company that owns the connected product and its APIs must host and operate the server.

After approval, the server can appear as a plugin in Rippling AI and in the MCP Gateway catalog in IT or My IT. A customer can find, connect, or use it only when their Rippling products, administrator policies, and user permissions allow it.

What you can submit​

Use MCP Submissions to request a listing.

SubmissionEligibleRequirement
Your company's vendor-hosted remote MCP server for your own product and APIsYesYour company must own and operate the product, the APIs, and the MCP server.
A local or stdio MCP serverNoRippling supports remote servers that use Streamable HTTP. Rippling does not install or host local servers.
An unofficial MCP server for another company's product or APIsNoOnly the company that owns the underlying product and APIs may publish its MCP server.
A server hosted by each customer or end userNoThe publisher must operate the remote service.
A remote server that does not support Streamable HTTPNoStreamable HTTP support is required.
Plugins, skills, or bundlesNoThis process lists a remote MCP server only.

Requirements​

  • A Rippling Developer account and Developer Sandbox. If you do not have an account, join the waitlist for the Rippling Developer Program. After Rippling approves the account, activate it and open the Developer Sandbox.
  • A production remote MCP endpoint that your company hosts and operates, with Streamable HTTP enabled.
  • A working authentication flow.
  • A successful connection from your Developer Sandbox, and the Rippling MCP Gateway URL from that connection.
  • A display name, one-sentence description, category, and logo.
  • Your company's legal name, website, documentation, support contact, and privacy policy.
  • A primary contact who can answer technical and review questions.
  • Testing instructions that contain no credentials, secrets, or customer data.
  • Confirmation that your company owns and operates the product and APIs the server uses.

Connect and test your server​

Connect the production server in your Developer Sandbox before you submit it.

  1. In the Developer Sandbox, go to IT > MCP Gateway and click Add connector. Create a custom connector. See Set up an MCP connector.
  2. Complete the connector’s authentication flow.
  3. Open the connector, go to Access assignments, and assign yourself. Choose the tools to allow, then select Assign. A connector cannot be used until someone is allowed to use it.
  4. Confirm that Rippling can discover the server’s tools.
  5. Test representative read operations and, if the server supports them, write operations.
  6. Confirm that errors tell the user how to fix the problem and do not expose secrets or sensitive data.
  7. Copy the Rippling Gateway URL.

The Rippling Gateway URL is temporarily unavailable in the sandbox. Contact your Rippling account manager if you are preparing an MCP submission.

Add the listing details​

In your Developer account, open MCP Submissions and create a listing.

  • Display name: Use the product or service name customers already recognize.
  • Slug: Rippling generates the slug from the display name. Review it before you continue.
  • Logo: Upload a PNG, JPEG, or SVG. Use a square image with a transparent background. SVG is preferred. Otherwise, use a PNG of at least 128 × 128 pixels. Crop extra whitespace so the mark stays legible on light and dark backgrounds.
  • Description: One sentence on what customers can do after they connect. Lead with the outcome.
  • Category: Choose the category closest to the product’s primary purpose.

Example description:

“Search projects, create issues, and keep engineering work up to date from your AI workflows.”

Publisher​

Provide current details for the company that operates the server:

  • Full legal company name, including any DBA name
  • Company website
  • Public documentation URL for the MCP server or the connected product
  • Support email address or support URL
  • Privacy policy URL
  • Primary contact name and work email address

The website, documentation, support information, privacy policy, and authentication screens should identify the same company. The primary contact should be able to coordinate testing and respond when Rippling requests changes.

Server configuration​

  • Production remote server URL: The endpoint for the server your company hosts and operates.
  • Access type: Whether the tools are read-only, write-only, or read-write.
  • Authentication method: OAuth 2.1, or an API key or personal access token.
  • Transport: Confirm that the server supports Streamable HTTP.

For OAuth 2.1, be ready to describe the authorization and token endpoints, client registration, required scopes, redirect behavior, and any setup prerequisites. For an API key or personal access token, explain where a customer creates it, which permissions it needs, and how they rotate or revoke it.

Do not enter a client secret, API key, personal access token, test-user password, or customer data in the form.

Ownership and review​

  1. Paste the Rippling Gateway URL from the sandbox connection you tested.
  2. Confirm that your company owns and operates the product and the APIs the server uses.
  3. Add short testing instructions: prerequisites, the safest tools to try, example inputs, and the expected result. Call out tools that create, update, send, or delete data.
  4. Review the listing and submit it.

Instructions must be reproducible without credentials or customer data. If testing needs special access, explain how Rippling can request it from your primary contact. Do not put access details in the form.

Next steps​

Rippling reviews the server, publisher information, authentication flow, tool behavior, testing instructions, and listing content. Submission does not guarantee approval or publication.

Due to heavy demand, reviews typically take two weeks. Timing depends on the server, the authentication flow, and how complete the submission is. Rippling does not promise a fixed review timeline.

If Rippling requests changes, update the submission, test the server again in your Developer Sandbox, and resubmit. Keep the production endpoint and the test connection available while the submission is in review.

A complete submission with reproducible test instructions is less likely to need follow-up.

After approval, eligible customers can find the server in:

  • Plugins in Rippling AI
  • The MCP Gateway catalog in IT or My IT

Customers choose whether to connect, then complete the server’s authentication flow. The listing leaves administrator policies and each user’s existing permissions in place.

Keep the listing current​

You operate the remote server and keep its documentation, support contact, privacy policy, authentication flow, and listing content up to date.

Respond to review comments in MCP Submissions. To change or withdraw a published listing, contact Rippling support with the listing name, slug, requested change, and primary contact. Do not create a second submission for a listing that already exists.

Before you change the endpoint, authentication, ownership, or tool permissions in a way that affects customers, coordinate with Rippling. Test the change in your Developer Sandbox so existing connections keep working.

See also​

In this article: