We and selected third parties use cookies or similar technologies for technical purposes and, with your consent, to analyze how the site is used.

You can freely give, refuse or withdraw your consent at any time.

BotSee

MCP server by BotSee

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

OAuth sign-in (You sign in with the vendor the first time you connect)Streamable HTTP

Connect to BotSee

BotSee needs sign-in. Connect with its own URL:

https://botsee.io/mcp

Your client opens BotSee’s sign-in the first time you use it. The token stays between your client and BotSee.

Share this server

Opens this page, with the URL and setup steps.

mcp.tc/i/botsee

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 you 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

Tools

BotSee lists its tools only after you sign in, so we can’t show them here. Your client lists them once you’re connected.

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

Set up

Every client connects to botsee.io, and BotSee asks you to sign in the first time. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport http botsee https://botsee.io/mcp
  1. 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:
https://botsee.io/mcp
  1. 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:
  1. Check that the URL reads https://botsee.io/mcp and click Add.
  2. 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

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

mcp.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

Or from a terminal:

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
{
  "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
{
  "mcpServers": {
    "botsee": {
      "serverUrl": "https://botsee.io/mcp"
    }
  }
}
  1. 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

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

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

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

Gemini CLI

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.

{
  "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.

Embed

Show BotSee in a README or on your site. Each embed links to this page, uses the server’s own URL, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![BotSee on mcp.tc](https://mcp.tc/i/botsee/badge.svg)](https://mcp.tc/i/botsee)
HTML
<a href="https://mcp.tc/i/botsee"><img src="https://mcp.tc/i/botsee/badge.svg" alt="BotSee on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/botsee.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/botsee" title="BotSee on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, the server’s own URL, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/botsee.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the BotSee card to your site.

Markdown
Add the mcp.tc card for BotSee, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/botsee.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="botsee"><a href="https://mcp.tc/i/botsee">BotSee on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![BotSee on mcp.tc](https://mcp.tc/i/botsee/badge.svg)](https://mcp.tc/i/botsee)
```

Reference: https://mcp.tc/embed

Change history

Its tools are behind a sign-in, so we can’t read them. Edits by its owner show up here.

Follow BotSee and we’ll email you when something changes.

Nothing recorded yet. Edits by the server’s owner will show up here.

FAQ

Can I paste mcp.tc/i/botsee into my MCP client?

No. mcp.tc links are pages, not server addresses. Connect with https://botsee.io/mcp, so your client talks to BotSee directly. The sign-in token only works there anyway. The quick link is for sharing: it opens this page, with setup steps for every client.

Does BotSee need an API key or a sign-in?

Yes, you need a BotSee account. The first time your client connects, it opens BotSee’s sign-in page. The token goes straight to the server’s own URL, never through mcp.tc.

Is BotSee a remote or a local server?

Remote. BotSee hosts it at https://botsee.io/mcp, and it speaks Streamable HTTP. There’s nothing to install.

What can BotSee do?

You can audit a site's AI visibility score across multiple AI providers, compare brand share of voice against competitors and see which queries and sources the brand is missing from.

Which clients can use it?

Any client that supports remote MCP servers: Claude Code, Claude Desktop, claude.ai, ChatGPT, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. The setup steps cover each one.

Does mcp.tc track changes to BotSee?

Partly. BotSee’s tools are behind a sign-in, so its History tab shows only edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read BotSee’s own metadata (its MCP handshake, tool list and public pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with BotSee. This page was built from BotSee’s public metadata, last checked on 18 Nov 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.