Skip to main content
Rippit does not need to have heard of your server. If it speaks MCP over Streamable HTTP at an HTTPS URL, you can connect it. This covers vendor servers Rippit has no built-in entry for, and internal servers your own team runs.

​
What to enter

OAuth redirects you to the server to authorize, and works when the server supports either dynamic client registration or client ID metadata documents. Most modern hosted servers do. Bearer token sends a token you paste as an Authorization header. It is stored encrypted and is not shown again after you connect. None is for open servers that need no credentials. There is no scope choice, since there is no identity to share.

​
What the server must support

  • HTTPS. Plain HTTP is rejected.
  • Streamable HTTP transport. SSE is deprecated in MCP and is not supported.
  • A reachable public address. Rippit connects from its own infrastructure, so a server on a private network or behind a VPN is not reachable. Servers on private address ranges are blocked.
  • A tools/list response. Rippit reads the tool list at connect time to build the selection.

​
Identity and scope

OAuth and bearer-token connections offer the same choice as any other connector: only you, or everyone in your organization. Both run on the credential you supplied, so an organization-wide connection shares your access with everyone, including scheduled runs. For an internal server, a service credential scoped to what the agent should reach is usually cleaner than a personal one.

​
Tools

Whatever the server exposes. Rippit reads the list and enables the tools the server declares read-only, then you adjust with Manage tools. Servers vary in how carefully they annotate their tools. If a server marks nothing read-only, your default selection will be empty and you will need to pick tools by hand. If it marks everything read-only, check the list yourself before trusting the default.