Connect your AI client

export BRANDVISIBILITY_API_URL="https://api.brandvisibility.ai"
export BRANDVISIBILITY_MCP_URL="https://mcp.brandvisibility.ai/mcp"

The BrandVisibility MCP server uses Streamable HTTP. It offers six read-only tools for your reporting data. It does not execute SQL, browse arbitrary URLs, run scans, or change your account.

Connect with OAuth

In a client that supports remote MCP and OAuth, add the MCP endpoint shown above. Follow the sign-in window, choose an organisation and its teams, and approve read-only access. The client handles tokens and refreshes.

For Claude’s web connector flow, add a custom connector in Settings → Connectors and enter the MCP endpoint. Client menus can change; choose its remote HTTP/OAuth connection option.

Owners and admins can disconnect an approval from Settings → API keys → Connected AI clients in BrandVisibility.

Connect with an API key

For a client supporting custom headers, create a key under Settings → API keys. Supply:

Authorization: Bearer <your organisation API key>

Use the client’s secure input or environment-variable support. Do not paste a real key into a shared config file.

Claude Code

# Use the environment variables from the panel above.
claude mcp add --transport http brandvisibility "$BRANDVISIBILITY_MCP_URL" \
  --header "Authorization: Bearer $BRANDVISIBILITY_API_KEY" --scope user

Cursor

Configure a remote MCP server, using environment-variable interpolation supported by your client:

{
  "mcpServers": {
    "brandvisibility": {
      "url": "${env:BRANDVISIBILITY_MCP_URL}",
      "headers": { "Authorization": "Bearer ${env:BRANDVISIBILITY_API_KEY}" }
    }
  }
}

Set that variable in the environment used to launch the client. For clients with a secure credential prompt, prefer that prompt.

Check the connection

Ask the assistant to list the teams you can access. Then ask for rankings or citations for a returned team. An empty report is valid when that team has no matching data.

If authentication fails, check the environment, key expiry, plan access, and team restrictions. If the server URL changes, reconnect through OAuth so the approval is bound to the current server URL. An existing approval for a different resource URL cannot simply be reused.

The product MCP endpoint retrieves your authorised reporting data. This documentation site does not run a separate product MCP server.