> ## Documentation Index > Fetch the complete documentation index at: https://docs.trysight.ai/llms.txt > Use this file to discover all available pages before exploring further. # MCP Connectors > Connect SEO tools, analytics, CRMs, and more so Sight AI Agent and Automations can pull live data from the apps your team already uses. ## Overview **MCP Connectors** let your team plug external data sources into Sight AI. Once connected, the agent can use provider tools in **Agent chat** and in **custom automations** — keyword research, SERP data, attribution metrics, CRM records, support conversations, and more. Open **Integrations** ([app.trysight.ai/integrations](https://app.trysight.ai/integrations)) and filter by **Connectors**, or scroll to the **Connectors** section on the hub. Each card shows an **MCP** badge in the top-right corner. > [!NOTE] > > Connectors are **team-scoped**, not site-scoped. One connection per provider is shared across every site on your team. Automations still run against a single site's data — connector tools supply external context. > [!NOTE] > > **Connectors are a Pro and Advanced feature.** Starter plans don't include MCP connectors — upgrade to Pro to connect external data sources. If a team downgrades, existing connections stay listed but become unavailable to the agent until the team is back on Pro or higher. > [!WARNING] > > **HubSpot has two integrations.** The [HubSpot CMS integration](https://docs.trysight.ai/integrations/hubspot.md) publishes articles to your HubSpot blog. The **HubSpot connector** (below) gives the agent access to CRM data — contacts, companies, deals, and marketing records. They are separate connections. ## Available connectors Sight AI ships prebuilt connectors for the providers below. Each uses the provider's official connection method. ### SEO & web data | Connector | What you get | How to connect | | - | - | - | | **Ahrefs** | Backlinks, keyword research, rankings, site audits | API key | | **Semrush** | Keyword analytics, domain overviews, competitive data | API key | | **SearchAPI** | Live Google, Bing, and other search-engine SERP data | API key | | **Firecrawl** | Scrape, crawl, map, search, and extract web content | API key | | **Exa** | Neural web search and content discovery | No key required | | **Apify** | Run web scrapers and data Actors (SERP, social, reviews, etc.) | API token | | **Parallel** | Agent-grade web search and research | Sign in (OAuth) | ### Analytics & attribution | Connector | What you get | How to connect | | - | - | - | | **Cometly** | Marketing attribution, ROAS, CAC, customer journey data | Sign in (OAuth) | | **PostHog** | Product analytics, insights, feature flags, experiments | Sign in (OAuth) | ### Content & assets | Connector | What you get | How to connect | | - | - | - | | **Notion** | Read, search, create, and update pages and databases | Sign in (OAuth) | | **Canva** | Generate and fetch on-brand designs and visuals | Sign in (OAuth) | | **Cloudinary** | Manage, transform, and search media assets | Sign in (OAuth) | ### CRM & revenue | Connector | What you get | How to connect | | - | - | - | | **HubSpot** | CRM contacts, companies, deals, and marketing data | Sign in (OAuth) | | **Stripe** | Customers, subscriptions, invoices, and revenue data | Sign in (OAuth) | | **Intercom** | Conversations, contacts, and support insights | Sign in (OAuth) | | **Attio** | Records, lists, and CRM data | Sign in (OAuth) | | **Close** | Leads, opportunities, and sales activity | API key | ### Automation | Connector | What you get | How to connect | | - | - | - | | **Zapier** | Trigger actions across apps via your configured Zapier MCP tools | API key | | **Composio** | Connect to hundreds of SaaS tools through Composio (Rube) | Sign in (OAuth) | ### Project & error tracking | Connector | What you get | How to connect | | - | - | - | | **Sentry** | Issues, errors, and performance data | Sign in (OAuth) | | **Linear** | Issues, projects, and cycles | Sign in (OAuth) | ## How to connect **1. Open Integrations** Go to **Integrations** and select the **Connectors** category (or scroll to the Connectors section). **2. Choose a connector** Click the provider card you want to connect. **3. Authenticate** Follow the prompt on screen: * **Sign in (OAuth)** — click **Continue with \[Provider]** and approve access in your browser. You'll return to Sight AI when done. * **API key / credentials** — paste the key or credentials from your provider account, then click **Connect**. * **Cometly** — sign in, then on Cometly's approval screen choose which Spaces to share and a default Space. * **Exa** — click **Connect**; no key is required. **4. Review tools** After a successful connection, open the connector detail page to review available tools and set permissions. > [!TIP] > > Only **team owners and admins** can connect, reconnect, or disconnect connectors. Any team member can use connected tools in Agent chat when the connector is enabled. ### Other ways to connect * **From Agent chat** — click the **+** in the chat composer to search providers and connect one in-context, without leaving the conversation. * **During setup** — the Setup hub's **Connectors** card introduces connectors for new sites and links you to the Integrations hub. ### Where to get API keys > [accordion] Ahrefs > > In Ahrefs: **Account Settings → API Keys → Generate MCP key**. Requires an **Ahrefs Lite plan or higher**. > > [Ahrefs MCP documentation →](https://docs.ahrefs.com/en/mcp/docs/introduction) > [accordion] Semrush > > In Semrush: **Profile → Subscription info → API units** — copy your API key. > > [Semrush MCP documentation →](https://developer.semrush.com/api/introduction/semrush-mcp/) > [accordion] SearchAPI > > In SearchAPI: **Dashboard → API Key**. > > [SearchAPI documentation →](https://www.searchapi.io/docs/mcp) > [accordion] Firecrawl > > In Firecrawl: **API Keys** at [firecrawl.dev](https://firecrawl.dev). > > [Firecrawl MCP documentation →](https://docs.firecrawl.dev/mcp-server) > [accordion] Apify > > In Apify: **Console → Settings → Integrations → API tokens**. > > [Apify MCP documentation →](https://mcp.apify.com) > [accordion] Close > > In Close: **Settings → API Keys**. > > [Close MCP documentation →](https://help.close.com/docs/mcp-server) > [accordion] Zapier > > Create a Zapier MCP server at [mcp.zapier.com](https://mcp.zapier.com), choose the actions to expose, and copy the API key. > > [Zapier MCP documentation →](https://mcp.zapier.com) > [accordion] Cometly > > No Space ID is needed. After you sign in, Cometly's approval screen asks which Spaces to share (one, several, or all of them) and which one is the default. The agent works in the default Space unless you name another; ask it to list your Spaces to switch. Connections made before this change keep working, and reconnecting moves them to the new flow. > > [Cometly MCP documentation →](https://docs.cometly.com/mcp/overview) > [accordion] PostHog (EU cloud) > > The prebuilt PostHog connector connects to the **US cloud**. If your PostHog project is on the EU cloud, add your EU endpoint as a [custom connector](#custom-connectors) instead. ## Custom connectors Add any supported HTTPS MCP server your team runs or subscribes to: 1. Integrations → **Connectors** → **Add custom connector** 2. Provide a **name**, **HTTPS MCP URL**, and authentication: * **OAuth** — browser sign-in (same flow as prebuilt OAuth connectors) * **API key** — paste a key from your provider * **None** — public MCP server only 3. Save and wait for the connection to complete **Limit:** 5 custom connectors per team. > [!TIP] > > Custom connector tools default to **Ask first** permission (see below). Read-only data connectors (Ahrefs, Semrush, and similar) default to **Always allow**. ## Connector detail page Click any connected connector card to open its detail page. From there you can: * **Enable / disable** the connector for your team * **Refresh tools** — update the tool list from the provider * **Reconnect** — re-authenticate after a key expires or access is revoked * **Disconnect** — remove the connector and delete stored credentials * **Set per-tool permissions** — control how each tool behaves in Agent chat ## Connection health & disconnects Sight AI monitors every connected connector automatically (about once an hour). If a connection breaks — an expired token, a revoked grant, or a provider outage — it's handled for you: * **Expired or revoked access** is flagged immediately; other transient failures are flagged after a second consecutive failed check (to avoid noise from a momentary blip). * **Team owners and admins get an email** identifying the connector that needs attention. * **Automations that depend on the broken connector are paused automatically** (with a per-automation email) so scheduled runs don't fail silently. They're ready to re-enable once you reconnect. * **Reconnecting** (Integrations → the connector → **Reconnect**) clears the alert, refreshes the tool list, and re-arms monitoring. ## Tool permissions Each tool on a connector has one of three permission levels: | Level | Behavior in Agent chat | Behavior in Automations | | - | - | - | | **Always allow** | Runs without asking | Runs automatically when granted on the automation | | **Ask first** | Shows an Approve/Decline card before every call | Runs automatically when granted (you opted in at automation creation) | | **Don't allow** | Tool is hidden from the agent | Tool is hidden from the automations picker | **Defaults:** * **Always allow** — read-only SEO and research connectors (Ahrefs, Semrush, SearchAPI, Firecrawl, Exa, Parallel, Cometly) * **Ask first** — connectors that can read or write live business data (CRM, billing, support, project tracking, automation platforms, Notion, PostHog, Apify, and all custom connectors) > [!WARNING] > > In **scheduled automations**, any connector tool you grant runs with **auto-confirm** — there is no second approval prompt during the run. Only grant connector tools your automation instructions actually need. ## Using connectors in Agent chat When a connector is enabled and connected: * Tools are grouped by provider so they never collide with built-in Sight AI tools * The agent attributes external data in replies (e.g. "per Ahrefs" or "per HubSpot") * Permission levels control whether each call needs confirmation > [!NOTE] > > Connector tools are also available to the **[Slack](https://docs.trysight.ai/integrations/slack.md)** agent, so your team can pull connector data straight from a Slack channel or DM. **Example prompts:** * *"What's our domain rating and top referring domains per Ahrefs?"* * *"Pull Semrush keyword volume for 'ai visibility software'."* * *"Search Exa for recent articles about programmatic SEO."* * *"How many open deals do we have in HubSpot this quarter?"* ## Using connectors in Automations Connector tools are available in the **custom automation** tool picker: 1. Create or edit a **Custom** automation 2. In **Allowed tools**, expand the connector group (e.g. **Ahrefs connector**, **HubSpot connector**) 3. Check the tools you want (tools set to **Don't allow** are hidden) 4. Write instructions that tell the automation when to call each tool **Example weekly competitive digest:** ``` Pull Ahrefs domain rating for our site and our top 3 competitors. Summarize backlink growth vs last month in 5 bullets. ``` See [Automation tools reference](https://docs.trysight.ai/automations/automation-tools.md) for built-in tools and [Custom automations](https://docs.trysight.ai/automations/custom-automations.md) for execution limits. ## Free Domain Rating (no connector required) Sight AI also uses Ahrefs' **free public Domain Rating API** — no MCP key needed: * Your site's DR is cached and injected into agent context automatically * The built-in `getDomainRating` tool returns DR for your site or any competitor domain * Attribution: **"Domain Rating by Ahrefs"** This is separate from the Ahrefs MCP connector, which requires a paid MCP key and exposes the full Ahrefs tool suite. ## Limits | Limit | Value | | - | - | | Custom connectors per team | 5 | | Tools per connector | 30 | | Total connector tools in agent | 80 | Tool names depend on what each provider exposes after connection. Use the connector detail page or the automations tool picker to see the live list for your team. ## Who can manage connectors | Action | Who | | - | - | | Connect / reconnect / disconnect | Team owner or admin | | Change tool permissions | Team owner or admin | | View status and permissions | Any team member | | Use connector tools in chat | Any team member (when connector is enabled) | ## Troubleshooting > [accordion] Connector shows 'Needs attention' or error status > > Open the connector detail page and click **Reconnect** or **Refresh tools**. Common causes: > > * **API key connectors** — invalid, expired, or revoked key; plan or quota limits on the provider side > * **OAuth connectors** — sign-in not completed; access revoked in the provider's settings > * **Cometly** — your access to the shared Space was revoked, or you were removed from it > * **Custom** — server unavailable or authentication mismatch > [accordion] Sign-in flow failed or timed out > > Stay signed in to Sight AI through the entire provider sign-in flow. If the browser tab sat idle too long, restart the connect flow from Integrations. > [accordion] Agent says connector unavailable > > * Connector was disabled or disconnected — re-enable from the detail page > * Tool was set to **Don't allow** — adjust permissions on the detail page > * Access expired — reconnect the provider > [accordion] Automation has 'no valid tools configured' > > The automation may reference connector tools that no longer exist (connector disconnected or tools refreshed). Re-edit the automation and re-select tools from the connector group in the picker. > [accordion] Custom connector quota exceeded > > Delete unused custom connectors before adding new ones. Maximum **5 custom** connectors per team. > [accordion] HubSpot connector vs HubSpot CMS > > If you want to **publish articles** to HubSpot, use the [HubSpot CMS integration](https://docs.trysight.ai/integrations/hubspot.md). The **HubSpot connector** is for CRM and marketing data inside Agent chat and automations — not article publishing. ## Related * [Custom automations](https://docs.trysight.ai/automations/custom-automations.md) — grant connector tools on scheduled workflows * [Automation tools reference](https://docs.trysight.ai/automations/automation-tools.md) — full built-in tool catalog * [HubSpot CMS integration](https://docs.trysight.ai/integrations/hubspot.md) — publish articles to HubSpot (separate from the HubSpot connector) * [Sight AI MCP (outbound)](https://docs.trysight.ai/developers/mcp-setup.md) — connect Cursor or Claude Desktop *to* Sight AI (different from external connectors) This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.