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.

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.

The Connectors page has two sections. Team connectors are set up once for the whole workspace, such as Zoom. Personal connectors are connected by each teammate with their own account, and that includes every catalog and custom connector.

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.

Each person on your team connects their own account. Catalog connectors use OAuth - no credentials are shared across users.

To disconnect, go back to Connectors, find the connector, click the three-dot menu, and choose Disconnect. Below a divider, the same menu can also show Remove for workspace, which removes the connector for everyone in the workspace, not just you.

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, or Rep can look it up), plus either an OAuth app (client ID and secret) or an API key.

Server requirements: the MCP server must be publicly reachable and follow the MCP spec. Servers that use the older SSE transport connect too.

The button on the card depends on how the server signs in. The same button is also on the connector's own page under Personal in Connectors, for finishing later.

For API key connectors, each member brings their own API key.

From Connectors you can:

You can also toggle connectors on or off from the tools menu in any Rep conversation, without going to settings.

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. Clarify also notifies you when one of your connections expires, in the app, by email and in Slack. If an agent needs a connection that has expired, it asks for it to be reconnected; when the connection belongs to a teammate, the agent's owner is told who needs to reconnect it.

What Rep can do from chat:

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 on a connector I set up with my own OAuth app

Confirm the redirect URI in your OAuth app's developer console is set to https://api.clarify.ai/mcp/oauth/callback exactly. This only applies to Static OAuth. Connectors that connect in one click have no redirect URI for you to set.

"This MCP server rejected client registration"

The other service declined Clarify's request to connect, and the rest of the message is that service's own explanation. For a catalog connector there's nothing to change in your account or in the service's settings, so contact support and include the full message. For a custom connector, ask Rep to add it with an API key or your own OAuth app instead, if the service offers one.

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.

Agents use the same connectors. Once a connector is set up, you add its tools to an agent from that agent's Tools section - there's nothing separate to connect. An agent uses the connection belonging to whoever owns it, so connect the service as the person who owns the agent.

One difference matters if the agent is meant to run on its own. Tools that write or change data start out set to Ask permission, which means the agent pauses and notifies you rather than acting. That's what you want while you're still building trust in an agent, but an agent running unattended on a schedule or a webhook will sit and wait. Set those tools to Always allow once you're confident in it. See Agents for the full picture.

Not a catalog or custom connector, no. Email and calendar sync has its own tiles - Google and Microsoft, under Personal on the Connectors page - and it supports Google and Microsoft accounts only. See Accounts for how to set it up.

The catalog and custom connectors on this page do a different job: they give Rep tool access to a service so it can act there when you ask. Adding a mail provider as a custom connector lets Rep call that provider's API during a conversation, but it does not import your mail into Clarify and won't keep your contacts and deals updated from your mailbox. If your mail is on a provider we don't support for sync, the workaround is a Google or Microsoft account that receives the same mail.

Not on its own. Most connectors, including every custom connector, give Rep and your agents tools to use when you ask. They don't copy that tool's data onto your people, companies or deals, and nothing runs in the background.

A few tiles on the Connectors page are syncs rather than tools, such as your email and calendar accounts and HubSpot. Those keep data flowing into Clarify once they're set up, and each has its own article.

A tool connector can: look things up in the connected tool during a conversation, take an action there on your behalf, and write to a Clarify record when you ask Rep or an agent to.

A tool connector doesn't: update your records from the connected tool by itself, or log email opens, replies or call outcomes onto a person automatically.

To get another tool's activity onto your records automatically, use Zapier or the Clarify API. In Zapier, Find Person looks a person up by email, Create Comment adds a comment to a record, and Update Record updates an existing record.

No. Rep connectors are available to every workspace on every plan.

Yes. Connectors work in the Rep Slack app the same way they do in Clarify.

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.

While Rep works, a status line shows what it is working on. When it finishes, the chat shows Rep's answer rather than each step it took. To control which tools Rep can use, see the next question.

Yes. At Connectors, you can configure tool permissions per 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.

Yes. Workspace admins can connect any MCP server using Dynamic OAuth, Static OAuth, or an API key. The server must be publicly reachable and follow the MCP spec. Both Streamable HTTP and the older SSE transport work.

No - there's no limit on catalog connections per user or custom connectors per workspace.