Gemini CLI HopeHire apify_webhook_api_linkedin_leads_webhook_apify_post

How to: Gemini CLI HopeHire apify_webhook_api_linkedin_leads_webhook_apify_post

client:Gemini CLI transport:streamable-http tool:apify_webhook_api_linkedin_leads_webhook_apify_post

Add HopeHire to Gemini CLI

01
Open ~/.gemini/settings.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "mcp": {
      "httpUrl": "https://hopehire.in/mcp"
    }
  }
}

02
Save the file and restart Gemini CLI.
03
Ask for something apify_webhook_api_linkedin_leads_webhook_apify_post does. Gemini CLI lists the server's tools on connect and calls apify_webhook_api_linkedin_leads_webhook_apify_post itself — you do not invoke it by name.
04
If nothing happens, check the server is running and that HopeHire's identifier in your config matches the one above exactly.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 14 November 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.

HopeHire MCP server