Claude Desktop AEO Scanner fix_site
How to: Claude Desktop AEO Scanner fix_site
Add AEO Scanner to Claude Desktop
-
01
Open ~/Library/Application Support/Claude/claude_desktop_config.json and merge this in. Keep any servers already there.
{
"mcpServers": {
"aeo-scanner": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://aeo-mcp.convrgent.ai/mcp"
]
}
}
}
-
02
Save the file and restart Claude Desktop.
-
03
Ask for something fix_site does. Claude Desktop lists the server's tools on connect and calls fix_site itself — you do not invoke it by name.
-
04
If nothing happens, check the server is running and that AEO Scanner's identifier in your config matches the one above exactly.
Claude Desktop has no remote transport in its config file, so this bridges through mcp-remote. Restart the app after saving. Claude Desktop docs
Set these first
AEO Scanner will not start until these are set, so fix_site never becomes available.
-
AEO_API_KEY
Same tool, other clients
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.