audit_geo — GEO Audit (AI Search Visibility) MCP Tool
audit_geo
(audit geo) is one of 2 tools on the
GEO Audit (AI Search Visibility)
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call audit_geo from your client
- Claude Code GEO Audit (AI Search Visibility) audit_geo run in your project directory
- Claude Desktop GEO Audit (AI Search Visibility) audit_geo ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor GEO Audit (AI Search Visibility) audit_geo ~/.cursor/mcp.json
- VS Code GEO Audit (AI Search Visibility) audit_geo .vscode/mcp.json
- Zed GEO Audit (AI Search Visibility) audit_geo ~/.config/zed/settings.json
- Windsurf GEO Audit (AI Search Visibility) audit_geo ~/.codeium/windsurf/mcp_config.json
- Cline GEO Audit (AI Search Visibility) audit_geo ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI GEO Audit (AI Search Visibility) audit_geo ~/.gemini/settings.json
- Grok GEO Audit (AI Search Visibility) audit_geo .mcp.json (in your project root)
- ChatGPT GEO Audit (AI Search Visibility) audit_geo Settings → Connectors → Advanced → Developer mode
- Claude.ai GEO Audit (AI Search Visibility) audit_geo Settings → Connectors → Add custom connector
- LangChain GEO Audit (AI Search Visibility) audit_geo pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http geo-audit https://geo-al6bxcngia-ue.a.run.app/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 16 October 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.