> ## Documentation Index
> Fetch the complete documentation index at: https://docs.asksightline.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP connector

> Ask Claude, Cursor, Gemini or Grok about your AI visibility, answered from your Sightline data.

> [!NOTE]
>
> The MCP connection is on the Growth plan.

Sightline has a remote MCP server, so AI tools can answer questions from your Sightline data. Once it's connected, try asking:

* "How visible are we in AI answers this month, and who's beating us?"
* "What changed in the last two weeks?"
* "Which recommendations should we do first?"

## Server address

```text theme={null}
https://app.asksightline.com/mcp
```

There's no API key to copy. Your AI tool asks you to sign in with your Sightline account and approve the connection. It then sees only the brands your account can see.

You'll also find this address, with steps for each tool, under **Connect AI tools** in the Sightline sidebar.

## Connect your tool

> [tab] Claude
>
> **Claude web and desktop apps**
>
> 1. Open **Customize → Connectors**, click **+** and choose **Add custom connector**.
> 2. Name it **Sightline** and paste the server address as the **Remote MCP server URL**. Leave the OAuth client ID and secret empty.
> 3. Click **Add**, sign in with your Sightline account and click **Allow**.
> 4. In a chat, turn the connector on from the tools menu in the message box.
>
> On Team and Enterprise plans, an owner adds it once under **Organization settings → Connectors** (Add → Custom → Web), with individual sign-in left on. Each person then connects with their own account.
>
> **Claude Code**
>
> ```bash theme={null}
> claude mcp add --transport http sightline https://app.asksightline.com/mcp
> ```
>
> Then run `/mcp` in Claude Code, pick **sightline** and sign in. Add `--scope user` to have it in every project.

> [tab] Cursor
>
> 1. Open `~/.cursor/mcp.json` (every project) or `.cursor/mcp.json` in a project, and add the server. If the file already has servers, add just the `sightline` entry inside `mcpServers`.
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "sightline": {
>       "url": "https://app.asksightline.com/mcp",
>       "auth": { "scopes": ["mcp"] }
>     }
>   }
> }
> ```
>
> 2. Save. In Cursor's MCP list, click **Connect** (or **Needs login**) next to sightline, sign in and click **Allow**.
> 3. It shows as connected with its tools listed. Ask in Agent chat.
>
> Keep the `auth` block: it stops Cursor asking for scopes this server doesn't issue. If sign-in hangs, open the server's settings in Cursor and reload it.

> [tab] Gemini
>
> **Gemini CLI**
>
> ```bash theme={null}
> gemini mcp add --transport http sightline https://app.asksightline.com/mcp
> ```
>
> Or add it to `~/.gemini/settings.json` yourself:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "sightline": { "httpUrl": "https://app.asksightline.com/mcp" }
>   }
> }
> ```
>
> Then run `/mcp auth sightline` in Gemini CLI, sign in and click **Allow**.
>
> **Antigravity**
>
> In the agent panel, open **… → MCP Servers → Manage MCP Servers → View raw config** and add:
>
> ```json theme={null}
> {
>   "mcpServers": {
>     "sightline": { "serverUrl": "https://app.asksightline.com/mcp" }
>   }
> }
> ```
>
> Save, then sign in when asked. Antigravity needs `serverUrl`, not `url`. If it reports "Unauthorized" right after signing in, run the server through `npx -y mcp-remote https://app.asksightline.com/mcp` as a command instead.

> [tab] Grok
>
> 1. On [grok.com](https://grok.com/connectors), open **Connectors**, click **New Connector** and choose **Custom**.
> 2. Name it **Sightline** and paste the server address as the **MCP Server URL**. Leave any OAuth client ID and secret empty.
> 3. Click **Add**, sign in with your Sightline account and click **Allow**.
> 4. In a chat, turn the connector on from the tools menu.
>
> Custom connectors may need a paid Grok plan.

## What a connected tool can do

| Tools | Who | What |
| - | - | - |
| `list_clients`, `get_client`, `get_visibility`, `get_competitors`, `get_citation_sources`, `list_questions`, `list_answers`, `get_answer`, `list_recommendations`, `get_recommendation`, `list_signals`, `get_agent_traffic`, `get_site_health`, `get_ai_referrals` | Everyone | Read the same numbers as the dashboard, with the same definitions |
| `update_recommendation_status`, `add_questions`, `set_question_active` | Admins | Mark recommendations, and add or pause questions |

A connected tool can't start checks, write content or publish to your website. Those stay in the Sightline app.

## Staying connected

Access tokens last an hour and your tool refreshes them automatically, so a connection stays signed in as long as it's used at least every 60 days.

To disconnect a tool, open **Connect AI tools** in Sightline and click **Disconnect** next to it under **Connected apps**. It's signed out right away.


## Related topics

- [WordPress plugin](https://docs.asksightline.com/integrations/wordpress-plugin.md)
- [Plans](https://docs.asksightline.com/plans.md)


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.