MCP & IDE agents
Call Piloterr from Gemini CLI with httpUrl
Gemini CLI stores MCP servers in settings.json under mcpServers. Use httpUrl (not url) for mcp.piloterr.com, plus headers for x-api-key, or run gemini mcp add --transport http.
- settings.json key is httpUrl, a common footgun if you paste Cursor JSON
- Optional: gemini mcp add --transport http and -H for the API key
- Google’s CLI plus the full Piloterr hosted tool list
- Good fit when the agent already uses Gemini models and Google Search habits
At a glance
httpUrl
settings.json
CLI
gemini mcp add
190+
library tools
HTTP
streamable
Why connect Gemini CLI
httpUrl is not url
Cursor and many MCP snippets use url. Gemini CLI expects httpUrl. Paste-carelessly and the server never connects.
Two install paths
Edit ~/.gemini/settings.json, or run gemini mcp add --transport http with -H x-api-key.
Gemini still needs a bypass for hard targets
Gemini’s own search is not a WAF bypass. Point the CLI at Piloterr when the page is behind bot checks.
Health vs handshake
Use /health in a browser to see tool count. Use the CLI for the MCP root. Do not expect a HTML app at the slash URL.
Gemini CLI + Piloterr patterns
Google CLI workflows, not an OpenAI or Anthropic copy.
SERP then deep fetch
Let Gemini plan queries, then force Piloterr Google or crawl tools for the pages that block datacenter IPs.
Maps and local data
Pair Gemini’s reasoning with Piloterr local or business endpoints when you need structured fields, not a screenshot.
settings.json in dotfiles
Commit a redacted snippet in your dotfiles repo. Keep the real key in the local file only.
Transport flag discipline
Always --transport http for the hosted server. stdio is only for a custom local subset.
Gemini CLI vs Gemini on the web
| Approach | DIY | Piloterr |
|---|---|---|
| gemini.google.com | No MCP HTTP server | settings.json httpUrl |
| Cursor JSON paste | url key is wrong here | Rename to httpUrl |
| Built-in Google fetch | Soft-blocked on many shops | Library + unlock tools |
| Custom Python MCP | You run a process | Hosted, 190+ tools |
Connect Gemini CLI
Step 1
Create an API key
From the Piloterr dashboard. You will put it in headers or -H.
Create an API keyStep 2
Add httpUrl in settings.json
Under mcpServers.piloterr set httpUrl to https://mcp.piloterr.com/ and headers.x-api-key.
Step 3
Or use gemini mcp add
gemini mcp add --transport http with the same URL and -H "x-api-key: YOUR_KEY".
Step 4
Reload and test
Restart Gemini CLI. Ask it to crawl a URL or list MCP tools. Use /health if the count is zero.
Workflow recipes
News brief with Google News tool
Gemini outlines sections; Piloterr fills articles and locations you actually requested.
Store locator enrichment
Gemini plans the countries; library finder endpoints return structured stores.
Shopping SERP then product JSON
Search tool first, product tool second, no headless Chrome on your laptop.
Docs crawl for a Gemini gem
You draft the gem instructions; Gemini CLI pulls the live help center through the crawler.
Gemini CLI vs other MCP clients
Scenario
Your default agent is Gemini CLI
Recommendation: This page, httpUrl
Scenario
You use Cursor day to day
Recommendation: Cursor .mcp.json
Scenario
You use Claude Code
Recommendation: claude mcp add
Scenario
You want a desktop agent with memory
Recommendation: Hermes Agent
Gemini CLI config
httpUrl is required. A url field copied from Cursor will not bind.
{
"mcpServers": {
"piloterr": {
"httpUrl": "https://mcp.piloterr.com/",
"headers": {
"x-api-key": "your-x-api-key"
}
}
}
}See also
MCP
Claude Code
Cursor
Hermes AgentTransparent credit pricing
Pay only for successful requests. Start with +500 credits, then scale with plans from $49/mo.
Premium
$49/mo
18,000 credits
Premium+
$99/mo
40,000 credits
Startup
$249/mo
110,000 credits
Ready to get started?
Your web scraping API is one click away. Start with +500 credits, no infrastructure to set up, no proxies to manage, and no credit card required.
- +500 credits
- No credit card required
- All endpoints included