Managing Connectors
This page is a light overview for workspace owners and admins who want to understand how connectors are managed across an organization. If you're an everyday user, you don't need anything here — start with the Connectors overview instead.
How the catalogue is curated
The list of connectors your team sees — Notion, Gmail, and any others — comes from a central catalogue that Rephlo maintains. Each entry defines the connector's name, description, icon, which plan tier it requires, and whether it's live, coming soon, or hidden. The desktop app fetches this catalogue automatically and keeps it up to date, so members always see the current set without doing anything.
You don't edit this catalogue yourself. Curating it (adding new connectors, marking one as coming soon, or retiring one) is handled by Rephlo. If you'd like a connector added or have a request for your organization, contact support and we'll help.
What admins can control
Connector availability is tied to plans and tiers. Which connectors your members can actually use depends on your organization's plan:
- Some connectors require a minimum tier (for example, Notion is available on Starter and above).
- Members on a plan that doesn't meet a connector's tier requirement will see it listed but won't be able to connect it.
To change what's available to your team, manage your plan in your workspace settings, or view plans and pricing. For seat counts, roles, and member access, see Teams and organizations — those settings live in your workspace and, for larger changes, are best handled with support.
Custom servers for your team
If your organization runs its own MCP server, members can connect it as a custom server using a bearer token. Custom servers are configured per-device in the desktop app and are not part of the shared catalogue — each member adds the server and token on their own machine. If you'd like a private connector distributed to your whole team rather than configured individually, reach out to support to discuss options.
A note on privacy and security
Connectors are built to keep credentials on the member's device:
- Authorization tokens and bearer tokens are stored encrypted on each member's machine, never on Rephlo's servers.
- Tool results are held in memory during a chat session and are not persisted to Rephlo's backend.
- A local audit log records connector activity (connect, disconnect, refresh, tool name, duration, status) without ever logging tool arguments or content.
Getting help
For anything beyond the basics here — adding a connector for your organization, distributing a private server, or questions about tier availability — please contact support. Enterprise customers can also reach their account contact directly.