AI Brand Visibility Tracker vs GEO MCP

A side-by-side look at the AI Brand Visibility Tracker and GEO MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

A
AI Brand Visibility TrackerMarketing
Check if ChatGPT, Perplexity & Gemini mention or cite a brand. Share of voice + GEO/AEO tracking.37FairAuth: not declared
GEO MCP logoGEO MCPMarketing · Remote HTTP/SSEGoogle Ads, Meta Ads, SEO, GEO & GA4 MCP by Ryze AI - audits, reports, keywords, Search Console.49FairAuth: oauth 2.0

Verdict: choose AI Brand Visibility Tracker for marketing work; choose GEO MCP for marketing over a hosted endpoint. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

A
Choose AI Brand Visibility Tracker when

  • You need dedicated capabilities in the Marketing domain.
Explore AI Brand Visibility Tracker

GEO MCP logoChoose GEO MCP when

  • You need dedicated capabilities in the Marketing domain.
  • You prefer a remote HTTP/SSE transport.
  • Its auth model fits you: OAuth 2.0.
Explore GEO MCP

Feature & specification comparison

Rows where the two servers differ are marked.

Spec
A
AI Brand Visibility Tracker
GEO MCP logoGEO MCP
CategoryMarketingMarketing
Quality signal37/100 · Fair49/100 · Fair
Install commandNot confirmed yetConfirmed
Transport—Remote HTTP/SSE
AuthNot declaredOAuth 2.0
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars—5,655
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
ToolsNot listedNot listed

Tools & capabilities

AI Brand Visibility Tracker tools

No tool names declared yet. Check the project README from the listing page.

GEO MCP tools

No tool names declared yet. Check the project README from the listing page.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

AI Brand Visibility Tracker

No confirmed install command for AI Brand Visibility Tracker yet — follow the setup steps linked from its listing page rather than a guessed package name.

GEO MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "google-ads-meta-ads-seo-geo-mcp": {
      "url": "https://connector.get-ryze.ai/mcp"
    }
  }
}

Frequently asked questions

AI Brand Visibility Tracker is categorized under Marketing and uses an install path we have not confirmed yet. GEO MCP belongs to Marketing and uses a remote HTTP/SSE transport. Pick AI Brand Visibility Tracker for marketing work and GEO MCP for marketing.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. AI Brand Visibility Tracker has no confirmed install command yet — follow its own setup instructions.

AI Brand Visibility Tracker has no declared pricing — check the project's own site. GEO MCP has no declared pricing — check the project's own site. Auth: oauth 2.0. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add ai-brand-visibility-tracker and google-ads-meta-ads-seo-geo-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, AI Brand Visibility Tracker has a quality signal of 37/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. GEO MCP has 49/100 (Fair) with 1 views, 0 installs and 5,655 GitHub stars.