compare_competitor_visibility — AEO Visibility MCP Tool
compare_competitor_visibility
(compare competitor visibility) is one of 5 tools on the
AEO Visibility
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call compare_competitor_visibility from your client
- Claude Code AEO Visibility compare_competitor_visibility run in your project directory
- Claude Desktop AEO Visibility compare_competitor_visibility ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AEO Visibility compare_competitor_visibility ~/.cursor/mcp.json
- VS Code AEO Visibility compare_competitor_visibility .vscode/mcp.json
- Zed AEO Visibility compare_competitor_visibility ~/.config/zed/settings.json
- Windsurf AEO Visibility compare_competitor_visibility ~/.codeium/windsurf/mcp_config.json
- Cline AEO Visibility compare_competitor_visibility ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AEO Visibility compare_competitor_visibility ~/.gemini/settings.json
- Grok AEO Visibility compare_competitor_visibility .mcp.json (in your project root)
- ChatGPT AEO Visibility compare_competitor_visibility Settings → Connectors → Advanced → Developer mode
- Claude.ai AEO Visibility compare_competitor_visibility Settings → Connectors → Add custom connector
- LangChain AEO Visibility compare_competitor_visibility pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http aeo-visibility https://aeo.advancelabs.dev/api/mcp/ai-visibility/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.