Ansvisor Docs

Ansvisor ships a Model Context Protocol server at https://app.ansvisor.com/api/mcp (or your own host if you self-host) so AI assistants can query your brand visibility data through natural-language conversation. No npm package, no local process — just a URL and an API key.

Generate an API key

Open your Ansvisor dashboard → Settings → API Keys
Click New key, give it a memorable name (e.g. Claude — laptop)
Copy the token. It’s shown once — store it in your password manager

The dialog that shows the key also has a ready-to-paste setup for each client below, with the key filled in. The snippets on this page read the key from an environment variable instead, so it stays out of your config files:

export ANSVISOR_TOKEN=ans_...

Every client connects to the same URL with the same header: Authorization: Bearer <your key>. There is no OAuth sign-in.

Connect your client

Claude Code

claude mcp add --transport http ansvisor https://app.ansvisor.com/api/mcp \
  --header "Authorization: Bearer ${ANSVISOR_TOKEN}"

Claude Desktop

Claude Desktop adds remote servers as custom connectors. The claude_desktop_config.json file only starts local servers, so a url entry there is ignored.

Open Settings → Connectors and choose Add custom connector
Name it Ansvisor and enter https://app.ansvisor.com/api/mcp as the URL
Under authentication choose No sign in
Under Request headers, add Authorization with the value Bearer ans_...

On Team and Enterprise plans, an owner adds the connector under Organization settings → Connectors first.

Codex CLI

codex mcp add ansvisor --url https://app.ansvisor.com/api/mcp \
  --bearer-token-env-var ANSVISOR_TOKEN

Or add it to ~/.codex/config.toml:

[mcp_servers.ansvisor]
url = "https://app.ansvisor.com/api/mcp"
bearer_token_env_var = "ANSVISOR_TOKEN"

Cursor

Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):

{
  "mcpServers": {
    "ansvisor": {
      "url": "https://app.ansvisor.com/api/mcp",
      "headers": { "Authorization": "Bearer ${env:ANSVISOR_TOKEN}" }
    }
  }
}

VS Code

Add to .vscode/mcp.json, or run MCP: Open User Configuration from the Command Palette to add it for every workspace. VS Code asks for the key the first time it connects:

{
  "inputs": [
    {
      "type": "promptString",
      "id": "ansvisor-token",
      "description": "Ansvisor API key",
      "password": true
    }
  ],
  "servers": {
    "ansvisor": {
      "type": "http",
      "url": "https://app.ansvisor.com/api/mcp",
      "headers": { "Authorization": "Bearer ${input:ansvisor-token}" }
    }
  }
}

Windsurf

In the Cascade panel, open … → Open MCP config file and add:

{
  "mcpServers": {
    "ansvisor": {
      "serverUrl": "https://app.ansvisor.com/api/mcp",
      "headers": { "Authorization": "Bearer ${env:ANSVISOR_TOKEN}" }
    }
  }
}

Gemini CLI

gemini mcp add --transport http \
  --header "Authorization: Bearer ${ANSVISOR_TOKEN}" \
  ansvisor https://app.ansvisor.com/api/mcp

This writes the server to ~/.gemini/settings.json with httpUrl. Use httpUrl, not url, if you edit the file by hand: url means the older SSE transport.

Hermes Agent

Add to ~/.hermes/config.yaml. Hermes reads ANSVISOR_TOKEN from your environment or from ~/.hermes/.env:

mcp_servers:
  ansvisor:
    url: "https://app.ansvisor.com/api/mcp"
    headers:
      Authorization: "Bearer ${ANSVISOR_TOKEN}"

OpenClaw

Add to ~/.openclaw/openclaw.json:

{
  "mcp": {
    "servers": {
      "ansvisor": {
        "url": "https://app.ansvisor.com/api/mcp",
        "transport": "streamable-http",
        "headers": { "Authorization": "Bearer ${ANSVISOR_TOKEN}" }
      }
    }
  }
}

Then check the connection with openclaw mcp probe ansvisor.

Zed

Add to your Zed settings.json. Zed does not expand environment variables here, so the key goes in directly:

{
  "context_servers": {
    "ansvisor": {
      "url": "https://app.ansvisor.com/api/mcp",
      "headers": { "Authorization": "Bearer ans_..." }
    }
  }
}

Other clients

Any client that supports remote MCP servers over Streamable HTTP works with the URL and the Authorization header above. If yours can only start local (stdio) servers, bridge it with mcp-remote:

{
  "mcpServers": {
    "ansvisor": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://app.ansvisor.com/api/mcp",
        "--header", "Authorization:${AUTH_HEADER}",
        "--transport", "http-only"
      ],
      "env": { "AUTH_HEADER": "Bearer ans_..." }
    }
  }
}

Keep Authorization:${AUTH_HEADER} without a space, with the Bearer ... value in env: some clients do not escape spaces inside args.

Check the connection

Ask your client “List my Ansvisor brands”. It should call the list_brands tool and show your brands. If it reports a 401, the header is missing or the key was revoked.

Self-host? Point at your own instance

The MCP endpoint lives at /api/mcp on whatever host runs the Ansvisor web app. If you self-host at ansvisor.mycompany.internal, use that base URL instead.

Available tools

Tool	What it does
`list_brands`	List brands the authenticated user can access.
`get_visibility_summary`	Aggregate visibility score, mentions, citations, top competitors for a brand over an optional date range / model / region.
`list_topics`	List the topics on a brand with a prompt count per topic. Use for coverage audits (empty / over-concentrated topics).
`list_prompts`	List the prompts tracked on a brand, optionally filtered by topic, active status, or capped via `limit`. Returns the prompt text, topic, platforms, models, regions, and active flag.
`list_actions`	List a brand’s Action Center actions with category, kind, impact, status, outcome, assignee, due date and task progress. Filter by status or category.
`get_action`	One action in full: payload, triggering signals, task list (with each task’s `mode` and `permission`) and event trail.
`list_signals`	Detected signals for a brand with their previous, current and change values. Filter by status or kind.
`list_action_history`	Closed actions with their outcome and the before/after values the validation sweep measured.
`update_task_status`	Mark a task in_progress, completed, skipped (with a reason) or failed. Records progress; it never carries the task out.

More tools land regularly — check the project roadmap.

Try it

Ask your client things like:

“List my Ansvisor brands.”
“What’s my visibility score on ChatGPT for the last 7 days?”
“Are my topics balanced?” / “Which topic has the most prompts?”
“Show me the prompts in my pricing topic.”
“Who are my top 5 competitors by mention count this month?”

The model picks the right tool, fills in the brand id and filters, and answers in plain English using the returned data.

Revoking access

If a key leaks or you stop using a client, open Settings → API Keys and click the trash icon. Clients using that key lose access immediately.

Transport

The server speaks the MCP Streamable HTTP transport in stateless mode — every request is self-contained, no session state is kept between calls. This makes it work cleanly behind any HTTP load balancer and on serverless runtimes.

​Generate an API key

​Connect your client

​Claude Code

​Claude Desktop

​Codex CLI

​Cursor

​VS Code

​Windsurf

​Gemini CLI

​Hermes Agent

​OpenClaw

​Zed

​Other clients

​Check the connection

​Self-host? Point at your own instance

​Available tools

​Try it

​Revoking access

​Transport