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