optimize_site — AEO Scanner MCP Prompt
optimize_site
is one of 1 prompt on the
AEO Scanner
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke optimize_site from your client
- Claude Code AEO Scanner Prompt/optimize_site run in your project directory
- Claude Desktop AEO Scanner Prompt/optimize_site ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor AEO Scanner Prompt/optimize_site ~/.cursor/mcp.json
- VS Code AEO Scanner Prompt/optimize_site .vscode/mcp.json
- Zed AEO Scanner Prompt/optimize_site ~/.config/zed/settings.json
- Windsurf AEO Scanner Prompt/optimize_site ~/.codeium/windsurf/mcp_config.json
- Cline AEO Scanner Prompt/optimize_site ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI AEO Scanner Prompt/optimize_site ~/.gemini/settings.json
- Grok AEO Scanner Prompt/optimize_site .mcp.json (in your project root)
- ChatGPT AEO Scanner Prompt/optimize_site Settings → Connectors → Advanced → Developer mode
- Claude.ai AEO Scanner Prompt/optimize_site Settings → Connectors → Add custom connector
- LangChain AEO Scanner Prompt/optimize_site pip install langchain-mcp-adapters
AEO Scanner also offers 1 resource — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 24 September 2026.
A listing does not declare its prompts, so asking is the only way to know them, and this
is what the server actually offers rather than what its listing claims. Names only are
stored; connect the server for each prompt's arguments.