# MCP server

> Ask Claude, Cursor and other AI assistants about your AI visibility.

Canonical URL: https://gensiv.com/docs/mcp
Product: Gensiv — Become the brand AI recommends

---

The Gensiv MCP server lets AI assistants that support the [Model Context Protocol](https://modelcontextprotocol.io) read your Gensiv data. Once connected, you can ask questions such as:

* "How did our ChatGPT visibility change this month compared to last month?"
* "Which competitor gained the most share of voice in the last 30 days?"
* "Which domains do AI engines cite most for our prompts?"
* "Which prompts are we losing, and who wins them?"
* "Show me recent answers where Globex was recommended and we were not."

The server is read-only. It uses the same API keys, plan requirements and [rate limits](/docs/rate-limits) as the REST API.

## Server details [#server-details]

|                |                                        |
| -------------- | -------------------------------------- |
| URL            | `https://api.gensiv.com/v1/mcp`        |
| Transport      | Streamable HTTP                        |
| Authentication | `Authorization: Bearer <your API key>` |

Create a key in **Settings → API keys** first. See [Authentication](/docs/authentication).

## Connect a client [#connect-a-client]

<Tabs items="[&#x22;Claude Code&#x22;, &#x22;Claude Desktop&#x22;, &#x22;Cursor&#x22;, &#x22;VS Code&#x22;]">
  <Tab value="Claude Code">
    Run this in your terminal:

    ```bash
    claude mcp add --transport http gensiv https://api.gensiv.com/v1/mcp \
      --header "Authorization: Bearer $GENSIV_API_KEY"
    ```

    Then start Claude Code and run `/mcp` to check that `gensiv` is connected.
  </Tab>

  <Tab value="Claude Desktop">
    Claude Desktop connects to servers that need an API key through the `mcp-remote` bridge, which requires Node.js.

    Open **Settings → Developer → Edit Config** and add Gensiv to `claude_desktop_config.json`:

    ```json title="claude_desktop_config.json"
    {
      "mcpServers": {
        "gensiv": {
          "command": "npx",
          "args": [
            "-y",
            "mcp-remote",
            "https://api.gensiv.com/v1/mcp",
            "--header",
            "Authorization: Bearer ${GENSIV_API_KEY}"
          ],
          "env": {
            "GENSIV_API_KEY": "gsk_..."
          }
        }
      }
    }
    ```

    Restart Claude Desktop after saving the file.
  </Tab>

  <Tab value="Cursor">
    Add Gensiv to `~/.cursor/mcp.json`, or to `.cursor/mcp.json` in a project:

    ```json title="mcp.json"
    {
      "mcpServers": {
        "gensiv": {
          "url": "https://api.gensiv.com/v1/mcp",
          "headers": {
            "Authorization": "Bearer gsk_..."
          }
        }
      }
    }
    ```
  </Tab>

  <Tab value="VS Code">
    Add Gensiv to `.vscode/mcp.json`. VS Code asks for the key the first time the server starts and stores it securely:

    ```json title=".vscode/mcp.json"
    {
      "inputs": [
        {
          "type": "promptString",
          "id": "gensiv-api-key",
          "description": "Gensiv API key",
          "password": true
        }
      ],
      "servers": {
        "gensiv": {
          "type": "http",
          "url": "https://api.gensiv.com/v1/mcp",
          "headers": {
            "Authorization": "Bearer ${input:gensiv-api-key}"
          }
        }
      }
    }
    ```
  </Tab>
</Tabs>

<Callout type="warn">
  Config files store your key in plain text. Do not commit them to a shared repository.
</Callout>

## Tools [#tools]

| Tool                        | What it returns                                                                                                                                   |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------- |
| `list_brands`               | Brands in the workspace and the engines each is tracked on.                                                                                       |
| `list_engines`              | The AI engines Gensiv collects answers from.                                                                                                      |
| `list_competitors`          | Tracked competitors for a brand.                                                                                                                  |
| `list_prompts`              | Tracked prompts for a brand, with each prompt's topic, tags and funnel stage.                                                                     |
| `list_prompt_groups`        | The topics and tags used to group a brand's prompts.                                                                                              |
| `get_group_metrics`         | Visibility, position, sentiment and share of voice per topic, tag, funnel stage or branded segment.                                               |
| `get_metrics`               | Visibility, share of voice, average position and sentiment for a brand and its competitors.                                                       |
| `get_daily_metrics`         | The same metrics per day, for trends. Returns your brand only unless you ask for competitors, and combines engines unless you ask for a split.    |
| `get_ai_traffic`            | Visits, key events and revenue from AI assistants per day, from the brand's Google Analytics.                                                     |
| `get_prompt_metrics`        | Visibility, position, sentiment and the most-named competitors for each prompt, lowest visibility first.                                          |
| `list_cited_domains`        | The domains AI engines cite most for a brand's prompts.                                                                                           |
| `list_cited_urls`           | The pages AI engines cite most for a brand's prompts.                                                                                             |
| `list_responses`            | Individual AI answers with mentions, positions and citations. Can be filtered to answers that leave your brand out or name a specific competitor. |
| `list_alerts`               | Recent alerts: visibility drops, competitor overtakes and new sources citing a rival.                                                             |
| `list_reddit_opportunities` | Reddit threads AI engines cite and threads worth joining.                                                                                         |
| `list_action_plans`         | Prompts the brand is losing to competitors, with the action plan for each: sources to earn, pages to update and articles to write.                |
| `list_articles`             | AI-written articles for a brand, with status and word count.                                                                                      |
| `get_article`               | One article with its Markdown body, meta description, sources and JSON-LD.                                                                        |
| `get_credit_balance`        | AI writing credits left this month, purchased credits and the reset date.                                                                         |

Each tool returns the same fields as the matching REST endpoint. See [Metrics](/docs/metrics) for how the numbers are calculated.