Connect external tools to Rep so it can take action across your stack — without leaving Clarify.
Rep can use tools from connected apps the same way it uses Clarify's own data. Once you connect Linear, for example, Rep can look up issues, create tickets, and update statuses from within a Rep conversation. Connectors work alongside Rep's built-in Clarify tools, not instead of them.
Available connectors
The catalog covers popular sales, support, and productivity tools — Linear, Notion, Stripe, Apollo, Intercom, Outreach, and more — and each tile shows what Rep can do with it. The catalog grows regularly, so open Connectors in the left sidebar for the current list.
Need to connect something that isn't in the catalog? You can add any MCP server as a custom connector. See Add a custom connector below.
Connect a catalog connector
Each person on your team connects their own account. Catalog connectors use OAuth — no credentials are shared across users.
In Clarify, go to Connectors in the left sidebar
Click the connector you want to add, then click Connect
Go through the OAuth flow
Once connected, Rep can use that connector's tools in all your conversations
To disconnect, go back to Connectors, find the connector, click the three-dot menu, and choose Disconnect.
Add a custom connector
You can connect any MCP server that isn't in the catalog. Only workspace admins can add custom connectors.
What you'll need: the MCP server URL (from the service's documentation), plus either an OAuth app (client ID and secret) or an API key.
Server requirements: the MCP server must be publicly reachable, use the Streamable HTTP transport, and follow the MCP spec.
ℹ️ This requires an MCP server, not a standard REST webhook endpoint.
Using Dynamic OAuth (default)
In Clarify, go to Connectors and click Add custom connector
Enter the service name and the MCP server URL
Click Add
Using a Static OAuth app
In the service's developer console, create a new OAuth app
Set the redirect URI to
https://api.clarify.ai/mcp/oauth/callbackCopy the client ID and client secret
In Clarify, go to Connectors and click Add custom connector
Enter the server URL, select Static OAuth, paste the client ID and secret, then click Add
ℹ️ The OAuth app only needs to be created once per workspace, but each team member still has to authorize their own account before they can use the connector.
Using an API key
Generate an API key from the service's settings
In Clarify, go to Connectors and click Add custom connector
Enter the server URL, select API key, paste the key, and click Add
For API key connectors, each member brings their own API key.
Connector and tool permissions
From Connectors you can:
Toggle any connector on or off
Configure which tools Rep is allowed to use, for Rep's built-in tools or any connector
You can also toggle connectors on or off from the tools menu in any Rep conversation, without going to settings.
Manage connectors from chat
You can manage your MCP connectors without leaving a Rep conversation. Ask Rep to list your connectors, add a new one, rename one, or remove one and it handles the action inline.
Connecting a new server: When a connector you need isn’t set up, Rep shows an in-chat connect card. Complete the OAuth flow in the same window and you’re returned directly to the conversation — Rep picks up where it left off.
Reconnecting an expired connector: If credentials have expired, Rep shows a reconnect prompt in the tools menu. Click to re-authorize without leaving the chat.
What Rep can do from chat:
List all configured connectors and their connection status
Add a new connector (OAuth or API key)
Rename a connector
Remove a connector (with a confirmation dialog)
Good to know
Catalog connectors are per-user. Each person on your team connects their own account. A teammate connecting Linear doesn't affect your connection.
Custom connectors require an admin. Only workspace admins can add or remove them. Members can use connectors that are already set up.
Rep may ask before taking action. For tools that create or update records, Rep may ask for your confirmation before proceeding.
Connectors work everywhere Rep does. Both in-app (island bar and sidebar) and in the Rep Slack app.
Troubleshooting
Connector isn't showing up after I added it
Refresh the page. If it still doesn't appear, disconnect and reconnect from Connectors.
Rep says a tool failed
Check that your account is still authorized at Connectors and reconnect if needed. After reconnecting, also make sure the connector's tools are toggled on — go to Connectors, find the connector, and enable its tools. You can also toggle them from the tools menu inside any Rep conversation.
I can't add a new connector
Only workspace admins can add custom connectors. Ask your workspace admin to add it.
OAuth connection failed
Confirm the redirect URI in your OAuth app's developer console is set to https://api.clarify.ai/mcp/oauth/callback exactly.
FAQ
What's the difference between the Clarify MCP connector and Rep connectors?
The Clarify MCP connector lets external AI tools (like Claude) read and update your Clarify data. Rep connectors do the opposite — they let Rep access your external tools like Linear, Notion, and Stripe.
Do I need a specific plan to use Rep connectors?
No. Rep connectors are available to every workspace on every plan.
Can I use Rep connectors from the Slack integration?
Yes. Connectors work in the Rep Slack app the same way they do in Clarify.
What data does Rep access when I connect a tool?
Rep only fetches data from connected tools when it needs to answer a question — it doesn't continuously sync or store data in the background. The specific permissions Rep is requesting are shown during the OAuth connection flow, so you can review the scopes before authorizing.
Can I see what tools Rep is using during a conversation?
Yes. Rep shows the tool calls it's making inline in the chat, so you can see what it's doing as it works.
Can I limit which tools Rep uses from a connected service?
Yes. At Connectors, you can configure tool permissions per connector.
What happens to my conversations if I disconnect a connector?
New conversations won't have access to that connector's tools. Existing conversations that referenced tools from that connector may show errors if continued.
Can I connect my own MCP server — not just ones in the catalog?
Yes. Workspace admins can connect any MCP server using Dynamic OAuth, Static OAuth, or an API key. The server must be publicly reachable, use the Streamable HTTP transport, and follow the MCP spec.
Is there a limit on how many connectors I can add?
No — there's no limit on catalog connections per user or custom connectors per workspace.