Skip to main content

​
Overview

MCP Connectors let your team plug external Model Context Protocol (MCP) servers into Sight AI. Once connected, the agent can call provider tools in Agent chat and in custom automations — keyword research, backlink data, attribution metrics, and anything your custom MCP server exposes. Open Integrations (app.trysight.ai/integrations) and filter by Connectors, or scroll to the Connectors section on the hub. Cards show an MCP badge in the top-right corner.
Connectors are team-scoped, not site-scoped. One Ahrefs or Semrush connection is shared across every site on your team. Automations still run against a single site’s data — connector tools just supply external context.

​
Prebuilt connectors

Sight AI ships three first-party connectors. Each uses the provider’s official MCP endpoint.
ProviderWhat you getAuth
AhrefsBacklinks, keyword research, rankings, site auditsAPI key (MCP key)
SemrushKeyword analytics, domain overviews, competitive dataAPI key
CometlyMarketing attribution, ROAS, CAC, customer journey dataOAuth (browser redirect)

​
Ahrefs

1

Generate an MCP key

In Ahrefs: Account Settings → API Keys → Generate MCP key. Requires an Ahrefs Lite plan or higher.
2

Connect in Sight AI

Integrations → Connectors → Ahrefs → paste the key → Connect.
3

Manage tools

Click the connected card to open the connector detail page. Review tool permissions and click Refresh tools if Ahrefs adds new endpoints.
Ahrefs MCP documentation →

​
Semrush

1

Copy your API key

In Semrush: Profile → Subscription info → API units — copy your API key.
2

Connect in Sight AI

Integrations → Connectors → Semrush → paste the key → Connect.
Semrush MCP documentation →

​
Cometly

1

Find your Space ID

In Cometly: Space Settings → Space Details, or check the number at the bottom of the left navigation menu.
2

Start OAuth

Integrations → Connectors → Cometly → enter Space ID → Continue with Cometly.
3

Approve access

Complete the OAuth flow in your browser. You’ll return to Sight AI with the connector connected.
Cometly MCP documentation →

​
Custom connectors

Add any HTTPS Streamable HTTP MCP server your team runs or subscribes to:
  1. Integrations → Connectors → Add custom connector
  2. Provide a name, HTTPS MCP URL, and auth mode:
    • OAuth — browser redirect (same callback flow as Cometly)
    • API key — Bearer or raw header
    • None — public MCP server only
  3. Save and wait for the handshake to complete
Limit: 5 custom connectors per team.
Custom connector tools default to Ask first permission (see below). Prebuilt analytics connectors default to Always allow because they expose read-only data.

​
Connector detail page

Click any connected connector card to open its detail page (/integrations/connectors/[id]). From there you can:
  • Enable / disable the connector for your team
  • Refresh tools — re-fetch the tool list from the MCP server
  • Reconnect — re-authenticate after a key expires or OAuth is revoked
  • Disconnect — remove the connector and revoke stored credentials
  • Set per-tool permissions — control how each tool behaves in Agent chat

​
Tool permissions

Each tool on a connector has one of three permission levels:
LevelBehavior in Agent chatBehavior in Automations
Always allowRuns without askingRuns automatically when granted on the automation
Ask firstShows an Approve/Decline card before every callRuns automatically when granted (you opted in at automation creation)
Don’t allowTool is hidden from the agentTool is hidden from the automations picker
Defaults: Ahrefs, Semrush, and Cometly tools default to Always allow. Custom connector tools default to Ask first.
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 appear namespaced so they never collide with built-in Sight AI tools — e.g. ahrefs_*, semrush_*, cometly_*, or {your_slug}_* for custom connectors
  • The agent attributes external data in replies (e.g. “per Ahrefs”)
  • Permission levels control whether each call needs confirmation
Ask naturally: “What’s our domain rating and top referring domains per Ahrefs?” or “Pull Semrush keyword volume for ‘ai visibility software’.”

​
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)
  3. Check the namespaced 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.
Tools: grant the relevant ahrefs_* tools from the picker. See Automation tools reference for built-in tools and Custom automations 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

LimitValue
Custom connectors per team5
Tools per connector30
Total connector tools in agent80
Tool names are dynamic — they depend on what each MCP server 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

ActionWho
Connect / reconnect / disconnectTeam owner or admin
Change tool permissionsTeam owner or admin
View status and permissionsAny team member
Use connector tools in chatAny team member (when connector is enabled)

​
Troubleshooting

Open the connector detail page and click Reconnect or Refresh tools. Common causes:
  • Ahrefs: invalid or expired MCP key; plan below Lite
  • Semrush: invalid API key or exhausted API units
  • Cometly: wrong Space ID; OAuth not completed; token revoked in Cometly
  • Custom: server down, non-HTTPS URL, or auth mismatch
Stay signed in to Sight AI through the entire provider OAuth flow. The callback expires after 10 minutes — restart the connect flow if the tab sat idle too long.
  • Connector was disabled or disconnected — re-enable from the detail page
  • Tool was set to Don’t allow — adjust permissions on the detail page
  • OAuth token expired — reconnect the provider
allowed_tools may reference connector tool names that no longer exist (connector disconnected or tools refreshed). Re-edit the automation and re-select tools from the connector group in the picker.
Delete unused custom connectors before adding new ones. Maximum 5 custom connectors per team.