Rippit

com.rippitPublished by rippit.comOfficial publisherv1.0.0Updated Oct 24, 2026

Official Rippit MCP server: analyze and enrich your customer support conversations and data

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Official Rippit remote MCP server that lets an assistant analyze and enrich customer support conversations and data.

What you can do
Rippit is an official remote MCP server reached over streamable HTTP at a hosted endpoint. According to its registry description, it lets an assistant analyze and enrich customer support conversations and data. No individual tools are listed in the supplied manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to work with customer support conversations and related customer data, for example reviewing or enriching support interactions. It is a hosted service, so it suits users who already use Rippit or want its support-data capabilities without running anything locally.
Requirements
A remote MCP client that supports streamable HTTP, pointed at the hosted Rippit endpoint. OAuth authentication is required; no environment variables or headers are declared. Network access to the endpoint is needed, and a Rippit account is implied by the OAuth requirement.
Before you install
The server is hosted by a third party, so support conversation data and related customer data are sent to Rippit for processing. OAuth grants access to your Rippit account, so review the scopes requested during authorization. No tools are listed, so what the assistant can read or change is not documented here.

Installation

In SourceWeft

  1. Open Rippit in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.rippit%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "rippit": {
      "type": "http",
      "url": "https://mcp.rippit.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 14, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.