get_v2_top_engines — similarweb MCP Tool Read-only
get_v2_top_engines
(get v2 top engines) is one of 20 tools on the
similarweb
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_v2_top_engines from your client
- Claude Code similarweb get_v2_top_engines run in your project directory
- Claude Desktop similarweb get_v2_top_engines ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor similarweb get_v2_top_engines ~/.cursor/mcp.json
- VS Code similarweb get_v2_top_engines .vscode/mcp.json
- Zed similarweb get_v2_top_engines ~/.config/zed/settings.json
- Windsurf similarweb get_v2_top_engines ~/.codeium/windsurf/mcp_config.json
- Cline similarweb get_v2_top_engines ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI similarweb get_v2_top_engines ~/.gemini/settings.json
- Grok similarweb get_v2_top_engines .mcp.json (in your project root)
- ChatGPT similarweb get_v2_top_engines Settings → Connectors → Advanced → Developer mode
- Claude.ai similarweb get_v2_top_engines Settings → Connectors → Add custom connector
- LangChain similarweb get_v2_top_engines pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http similarweb https://mcp.jojapi.com/similarwebOther tools on this server
- get_v3_autocomplete
- get_v2_filter_options
- get_v3_marketshare
- get_v2_serp_seismometer
- get_v2_website_analytics
- get_v3_website_analytics
- get_v2_website_competitors
- get_v3_top_websites
- get_v2_top_websites
- get_v3_top_apps
- get_v2_play_store_top_apps
- get_v2_play_store_app_details
- get_v2_app_store_top_apps
- get_v2_app_store_app_details
- get_v2_app_analytics_google_play
- get_v2_app_analytics_app_store
- get_v2_top_browsers
- get_v2_top_platforms
- get_v2_company_details
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.