Connect a server
The setup flow, identity choices, and how tool selection works.
Slack
Search and read channels; deliver reports and alerts.
Intercom
Read conversations, contacts, companies, and Help Center articles.
Notion
Search the workspace; read and write pages and databases.
Salesforce
Query accounts, cases, and custom objects with SOQL.
Snowflake
Run governed SQL against your warehouse.
Databricks
Query Unity Catalog through Databricks SQL.
Custom server
Point at any MCP server URL, including your own internal ones.
What this changes
An agent that can only read Rippit answers questions about conversations. An agent that can also reach your other systems answers questions that span them, and then does something with the answer.- Bring in the context that isn’t in the ticket. Rippit says 300 customers hit a checkout failure. Salesforce or Snowflake says which of them are enterprise accounts and what they are worth.
- Ground the analysis in what you have already written. Match rising contact drivers against your Notion or Help Center coverage to find the gap.
- Deliver the result where people are. Post the weekly escalation summary into a Slack channel instead of leaving it in a tab nobody opens.
- Run it unattended. Turn work you proved out in chat into an Agent App that runs hourly, daily, or weekly with nobody watching. Agent Apps use the same connections as chat, and every run is recorded.
Setting one up
Connections live under Connections → MCP Servers in Rippit, and creating one takes a Full Admin. A connection is made once and is then available to agent runs; individual users do not each authorize it. Two things are worth knowing before you start, both covered in full on Connect a server:- Connections start read-only. Only the tools a server declares read-only are enabled. Turning on anything that writes is deliberate and per tool.
- Scope decides who can use it. A connection can be yours alone or shared with your organization, and only shared connections are available to Agent Apps.