Rippling MCP Gateway
Connect Slack to the AI clients your company usesRippling MCP Gateway connects supported Model Context Protocol (MCP) clients—including Rippling AI, Cursor, Claude Code, and other compatible clients—to your Slack workspace. Administrators manage Slack authentication, user access, tool permissions, and audit activity in one place.How the Slack app worksA Rippling MCP Gateway admin installs the Slack app and configures who can use the connection and which Slack tools are available.
Authorized users then connect their own Slack identities.Access follows each user’s existing Slack permissions. The app cannot access channels, messages, files, canvases, or conversations that the connected user cannot access in Slack.From a supported MCP client, authorized users can:• Search accessible public channels, private channels, direct messages, group direct messages, files, and users
• Read channels, threads, files, canvases, profiles, channel membership, emojis, and reactions
• Send or schedule messages and create message drafts
• Create public channels, private channels, direct messages, and group direct messages
• Add reactions to messages
• Create and update canvasesMessages and actions performed through the app appear in Slack and are associated with the connected Slack identity.Authentication, policies, and auditingThe app uses OAuth to connect each Slack workspace and user. Rippling’s managed client credentials remain server-side. Each customer workspace receives a separate Slack authorization. Each connected user receives an authorization tied to their Slack identity.Every Slack MCP request passes through Rippling MCP Gateway. MCP Gateway evaluates the request against company-configured access and tool policies before sending it to Slack. Slack continues to enforce its workspace, channel, and user permissions.Administrators can control connector access and available Slack tools. MCP Gateway records tool-call activity for auditing and
troubleshooting.InstallationA Rippling admin installs the Slack app through the authenticated MCP Gateway admin experience. During installation, the admin selects their Slack workspace and approves the requested permissions. MCP Gateway associates that Slack authorization with the correct Rippling company and its auto-provisioned Slack connector.After installation, the admin configures connector access. Each authorized user connects their own Slack identity before using Slack MCP tools.AI-generated outputThis app can provide Slack content that a connected user can access to AI-powered MCP clients. Those clients may generate responses, summaries, and other output.AI-generated output may be incomplete or inaccurate. Review important information before relying on it or taking action. AI-generated output must not be the sole basis for legal, medical, employment, or other consequential decisions.Slack actions remain subject to the connected user’s Slack permissions and the policies configured in MCP Gateway.Requirements• An active Rippling MCP Gateway subscription
• Rippling permission to install or manage MCP connectors
• Slack workspace permission to approve or install apps
• Individual Slack authorization for each user
Authorized users then connect their own Slack identities.Access follows each user’s existing Slack permissions. The app cannot access channels, messages, files, canvases, or conversations that the connected user cannot access in Slack.From a supported MCP client, authorized users can:• Search accessible public channels, private channels, direct messages, group direct messages, files, and users
• Read channels, threads, files, canvases, profiles, channel membership, emojis, and reactions
• Send or schedule messages and create message drafts
• Create public channels, private channels, direct messages, and group direct messages
• Add reactions to messages
• Create and update canvasesMessages and actions performed through the app appear in Slack and are associated with the connected Slack identity.Authentication, policies, and auditingThe app uses OAuth to connect each Slack workspace and user. Rippling’s managed client credentials remain server-side. Each customer workspace receives a separate Slack authorization. Each connected user receives an authorization tied to their Slack identity.Every Slack MCP request passes through Rippling MCP Gateway. MCP Gateway evaluates the request against company-configured access and tool policies before sending it to Slack. Slack continues to enforce its workspace, channel, and user permissions.Administrators can control connector access and available Slack tools. MCP Gateway records tool-call activity for auditing and
troubleshooting.InstallationA Rippling admin installs the Slack app through the authenticated MCP Gateway admin experience. During installation, the admin selects their Slack workspace and approves the requested permissions. MCP Gateway associates that Slack authorization with the correct Rippling company and its auto-provisioned Slack connector.After installation, the admin configures connector access. Each authorized user connects their own Slack identity before using Slack MCP tools.AI-generated outputThis app can provide Slack content that a connected user can access to AI-powered MCP clients. Those clients may generate responses, summaries, and other output.AI-generated output may be incomplete or inaccurate. Review important information before relying on it or taking action. AI-generated output must not be the sole basis for legal, medical, employment, or other consequential decisions.Slack actions remain subject to the connected user’s Slack permissions and the policies configured in MCP Gateway.Requirements• An active Rippling MCP Gateway subscription
• Rippling permission to install or manage MCP connectors
• Slack workspace permission to approve or install apps
• Individual Slack authorization for each user
Rippling MCP Gateway will be able to view:
Rippling MCP Gateway will be able to do:
Review the details to better understand this app’s security practices. To learn more about assessing apps for your workspace visit our Help Center.
General
Developer
Rippling
Company headquarters location
United States
Terms of service
Privacy & data governance
Data retention policy
Rippling retains Slack OAuth tokens, connection metadata, and operational logs only as long as necessary to provide and secure the MCP Gateway. Slack content is processed on demand and is not retained beyond operational requirements.
Data archiving and removal policy
When an integration is disconnected or deletion is requested, Rippling revokes OAuth tokens and removes associated connection data from active systems. Residual backups expire according to established retention schedules. Legally required security or audit records may be retained with restricted access.
Data storage policy
Credentials and connection data are tenant-isolated, encrypted in transit and at rest, and accessible only to authorized services and personnel. Rippling does not sell Slack data or use it to train general-purpose AI models.
Data center location(s)
United States
App/service has sub-processors
no
App/service uses large language models (LLM)
yes
LLM model(s) used
OpenAI GPT models and Anthropic Claude models, including Anthropic models accessed through Amazon Bedrock. Rippling AI may select between approved models based on the use case, performance, output quality, latency, cost, and safety.
LLM retention settings
Rippling’s third-party LLM providers are configured for zero data retention or an equivalent limited-retention configuration. Prompts, inputs, and model outputs sent to those providers are not durably retained after processing and are not used to train
LLM data tenancy policy
Customer data is isolated by company and access is enforced using the authenticated user’s company context and existing Rippling permissions. Only data authorized for and required by the requesting user’s interaction is provided for model processing.
LLM data residency policy
Rippling AI model processing currently occurs in the United States. Third-party model providers process data under Rippling’s Data Processing Addendum and applicable subprocessor terms.Rippling AI is not currently supported in Rippling’s EU data center
Certifications & compliance
Data deletion request procedure
Users or workspace administrators can request deletion by disconnecting the Slack integration or contacting Rippling Support/Privacy. After verifying the request, Rippling revokes the Slack OAuth tokens and deletes the associated connection metadata, credentials, and any stored Slack-derived data from active systems. Slack content processed through the MCP Gateway is used only to fulfil the user’s request and is not retained beyond operational needs. Backup data expires according to Rippling’s retention schedule. Limited security or audit records may be retained where legally required, with restricted access. Completion is confirmed to the requester.
HIPAA compliant
yes
While this app may offer HIPAA compliance, Slack does not have a business associate agreement with any third-party application providers, including those in the Slack Marketplace, so you are responsible for validating the provider's compliance and executing an appropriate agreement before enabling.
Security
Date of latest pen test
2026-08-01
Executive summary is available to potential customers upon request
yes
Supports Single Sign On (SSO) with the following providers
Rippling, Okta
Supports Security Assertion Markup Language (SAML)
yes
Has a dedicated security team
yes
Contact for security issues
security@rippling.com
Has a vulnerability disclosure program
yes
Vulnerability disclosure program URL
Vulnerability disclosure program covers Slack app
yes
Has a bug bounty program
no
Requires third party authorization/connections
no
Third party services used by this app
Apps like Slack, etc
Uses token rotation
no