get_engine_visibility — grounded aeo MCP Tool Read-only
get_engine_visibility
(get engine visibility) is one of 15 tools on the
grounded aeo
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_engine_visibility from your client
- Claude Code grounded aeo get_engine_visibility run in your project directory
- Claude Desktop grounded aeo get_engine_visibility ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor grounded aeo get_engine_visibility ~/.cursor/mcp.json
- VS Code grounded aeo get_engine_visibility .vscode/mcp.json
- Zed grounded aeo get_engine_visibility ~/.config/zed/settings.json
- Windsurf grounded aeo get_engine_visibility ~/.codeium/windsurf/mcp_config.json
- Cline grounded aeo get_engine_visibility ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI grounded aeo get_engine_visibility ~/.gemini/settings.json
- Grok grounded aeo get_engine_visibility .mcp.json (in your project root)
- ChatGPT grounded aeo get_engine_visibility Settings → Connectors → Advanced → Developer mode
- Claude.ai grounded aeo get_engine_visibility Settings → Connectors → Add custom connector
- LangChain grounded aeo get_engine_visibility pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http grounded-aeo https://groundedaeo.com/api/mcpOther tools on this server
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.