aeo_batch_audit — mcp MCP Tool
aeo_batch_audit
(aeo batch audit) is one of 36 tools on the
mcp
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call aeo_batch_audit from your client
- Claude Code mcp aeo_batch_audit run in your project directory
- Claude Desktop mcp aeo_batch_audit ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor mcp aeo_batch_audit ~/.cursor/mcp.json
- VS Code mcp aeo_batch_audit .vscode/mcp.json
- Zed mcp aeo_batch_audit ~/.config/zed/settings.json
- Windsurf mcp aeo_batch_audit ~/.codeium/windsurf/mcp_config.json
- Cline mcp aeo_batch_audit ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI mcp aeo_batch_audit ~/.gemini/settings.json
- Grok mcp aeo_batch_audit .mcp.json (in your project root)
- ChatGPT mcp aeo_batch_audit Settings → Connectors → Advanced → Developer mode
- Claude.ai mcp aeo_batch_audit Settings → Connectors → Add custom connector
- LangChain mcp aeo_batch_audit pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://everlange.com/api/mcp
Other tools on this server
- aeo_list_sites
- aeo_audit
- aeo_audit_status
- aeo_report
- aeo_improvements
- aeo_generate
- aeo_apply
- aeo_citations
- aeo_proof
- aeo_monitor
- ads_list_accounts
- ads_performance
- ads_search_terms
- ads_change_history
- ads_quality_breakdown
- ads_landing_pages
- ads_geo_performance
- ads_asset_performance
- ads_campaign_criteria
- ads_geo_target_search
- ads_audiences
- ads_device_performance
- ads_set_bid_modifier
- ads_add_location
- ads_remove_criterion
- ads_attach_audience
- ads_keywords
- ads_audit
- ads_add_negative_keywords
- ads_pause_keyword
- ads_update_budget
- ads_campaign_status
- ads_list_ads
- ads_ad_status
- ads_add_keywords
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.