# BotSee MCP server

> Measure brand mentions, citations and competitor share of voice across ChatGPT, Claude, Perplexity and Gemini.

- Listing: https://mcp.tc/i/botsee
- Connect: use the server's own URL `https://botsee.io/mcp` (OAuth sign-in at the server); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: OAuth sign-in
- Category: [Marketing & SEO](https://mcp.tc/c/marketing-seo)
- Vendor: BotSee
- Homepage: <https://botsee.io/>

## About

BotSee runs AI visibility audits for a website or brand. It tests queries across ChatGPT, Claude, Perplexity and Gemini, reports where the brand is mentioned or missing, compares share of voice against competitors, and gives recommendations and draft content to close visibility gaps.

It runs as a hosted remote endpoint at https://botsee.io/mcp, added as a custom connector in Claude or ChatGPT. On first use you sign in or create a BotSee account. Analysis and content generation use paid tokens.

## What it can do

- Audit a site's AI visibility score across multiple AI providers
- Compare brand share of voice against competitors
- See which queries and sources the brand is missing from
- Get recommendations to improve AI visibility
- Generate content aimed at visibility gaps

## Example prompts

- "Audit the AI visibility of yoursite.com"
- "How does our brand compare against competitors in AI answers?"
- "What are your recommendations to improve AI visibility?"
- "Write content that can improve my site's AI visibility"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http botsee https://botsee.io/mcp
```

2. Start Claude Code, type `/mcp`, pick **botsee** and choose **Authenticate**. A browser window opens for the BotSee sign-in.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **BotSee** and paste this URL:

```url
https://botsee.io/mcp
```

3. Click **Add**, then **Connect**, and sign in when BotSee asks.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=BotSee&connectorUrl=https%3A%2F%2Fbotsee.io%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://botsee.io/mcp` and click **Add**.

3. Click **Connect** and sign in when BotSee asks.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://botsee.io/mcp` as the server URL, then for authentication choose **OAuth**. ChatGPT sends you to BotSee to sign in.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=botsee&config=eyJ1cmwiOiJodHRwczovL2JvdHNlZS5pby9tY3AifQ%3D%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "botsee": {
      "url": "https://botsee.io/mcp"
    }
  }
}
```

Cursor shows **Needs authentication** next to the server. Click the button beside it to sign in.

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=botsee&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fbotsee.io%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"botsee","type":"http","url":"https://botsee.io/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "botsee": {
      "type": "http",
      "url": "https://botsee.io/mcp"
    }
  }
}
```

VS Code asks you to sign in the first time the server starts.

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "botsee": {
      "serverUrl": "https://botsee.io/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade and sign in when asked.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add botsee --url https://botsee.io/mcp
codex mcp login botsee
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.botsee]
url = "https://botsee.io/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http botsee https://botsee.io/mcp
```

Then, inside Gemini CLI, run `/mcp auth botsee` to sign in.

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "botsee": {
      "type": "http",
      "url": "https://botsee.io/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://botsee.io/mcp`.

## Details

- Last checked: 2026-11-18 (reachable, asks for credentials)
- Listed: 2026-10-24
- Updated: 2026-10-24

---
Source: https://mcp.tc/i/botsee (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
