settings.json · scriptable · cron friendlyLead gen from the command line
One entry in Gemini CLI's settings.json and the terminal gets 34 Getlead tools. Search the database, verify addresses, launch campaigns and triage replies, in a session or on a schedule.
Read-only keys make scheduled runs safe · included with Pro and Ultra
Claude
ChatGPT
Cursor
Gemini+ any MCP clientinbox-triage.mdShare9 unread replies. 4 interested, 3 not now, 2 not a fit. Three are flagged as opportunities:
Interested, can you send pricing for a 12-seat team? We are comparing two vendors this week…
Not right now, budget resets in October. Worth a ping then, happy to look properly…
Read tools are safe unattended: quota checks, inbox pulls, stats and audits.
Output pipes into jq, git and whatever already runs your growth stack.
A read key for schedules, a write key for interactive sessions.
01 · Scheduled
Outbound that runs while you sleep.
A cron entry, a read-only key, and every weekday morning the inbox is already classified. No dashboard to open, no tab to remember.
- Read tools are safe to run unattended
- Write tools refused at the server for a read-only key
- Output written to a file you actually read
Weekday 08:00 run finished. Today's summary:
Getlead02 · Repeatable
The same prompt, a fresh list.
Run your list-building prompt monthly. The database is live, so each run returns contacts that were not there last time instead of the same stale export.
- Deterministic filters, fresh data
- Straight into a Getlead list
- Verified before anything sends
Saved to 'Berlin Dental, August'. Here is a sample:
Getlead
03 · Composable
Plays well with the rest of your stack.
Everything returns structured data on stdout, so it composes with the scripts, Makefiles and CI jobs you already run.
- Plain text in, structured data out
- No GUI dependency anywhere in the loop
- Deliverability audits you can gate a deploy on
All three checked. One needs attention:
GetleadBest uses
Where it earns its keep
Scheduled checks
A weekday cron that pulls unread replies and writes a triage table you read with your coffee.
Pipe into your tools
stdout composes with jq, git and the scripts that already run your growth stack.
Repeatable list building
Same prompt, run monthly, fresh contacts each time because the database is live.
Setup
Connected in under two minutes
Mint a read-only key
The right default for anything on a timer. Mint a second write key for interactive sessions.
Add the mcpServers block
~/.gemini/settings.json for user scope, .gemini/settings.json for one project. Use httpUrl, not url.
Verify with /mcp
Run gemini, type /mcp to list connected servers, then ask it to call get_account.
Copy-paste config and every edge case: the setup docs.
Guardrails come with it
Scoped keys, hourly ceilings on campaigns and replies, a full audit log, and lead text returned as untrusted data. An assistant with your mailbox needs limits that do not depend on the assistant behaving.
“My three SDRs share one license instead of three Apollo seats. 31 meetings last month and the data is cleaner.”
“Skeptical about the flat price, honestly. Landed my first client in 11 days and never looked at the competition again.”
“The niche filters are the secret. Tight list of 400 ops leaders, personalized opener, 6.4% reply rate on the first run.”
Pricing
Already inside Pro and Ultra
No MCP add-on, no per-call fee. Tool calls spend the allowances you already pay for.
FAQ
Before you connect
Where does the Gemini CLI config live?
User scope is ~/.gemini/settings.json and applies everywhere. Project scope is .gemini/settings.json in the working directory. Both take the same mcpServers block.
Why httpUrl and not url?
Gemini CLI uses httpUrl for streamable HTTP MCP servers and url for the older SSE transport. Getlead speaks streamable HTTP, so httpUrl is correct.
Can I run this unattended from cron?
Read tools, yes: quota checks, inbox pulls, campaign stats and deliverability audits are safe on a schedule. Use a read-only key so a scheduled run cannot send.
How do I keep the key out of the config file?
Gemini CLI expands environment variables in settings.json, so store the key in your shell profile or a secret manager and reference it. A key in a synced dotfile is a key you will eventually leak.
Do the tool calls count against my Gemini quota?
Tool calls consume Gemini tokens for the conversation and Getlead credits for the work. The two are independent.
Script your outbound
One settings.json entry, and lead gen becomes a command you can schedule.
Mint an API key