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