Integration guide
apifare for Gemini CLI
Give Gemini CLI one prepaid key for every API it needs. There is no separate provider account or provider API key for eligible capabilities, and it all runs under hard caps and a kill switch.
1 · Get a key
Create an account at /start: email in, token out (shown once). Save the token somewhere safe.
2 · Add apifare to Gemini CLI
Add this to ~/.gemini/settings.json (all projects) or .gemini/settings.json in one project. If the file already has settings, merge the mcpServers entry in alongside them.
{
"mcpServers": {
"apifare": {
"command": "npx",
"args": ["-y", "apifare-mcp"],
"env": { "APIPAY_TOKEN": "<your-token>" }
}
}
}Replace <your-token> with your token. Restart Gemini CLI, then run gemini mcp list to check the server.
3 · Try it
Ask Gemini CLI to search the web for X, then to fetch a URL, then what's the weather in London. Every call is debited from your balance and lands on your signed, exportable audit chain.
4 · Stay in control
Set daily or monthly caps per agent, and keep the kill switch ready. Both are checked before a call is dispatched. When the balance runs out, your agent gets an HTTP 402 with a top-up link it can hand you; the error catalog lists every stop and what unblocks it.
What Gemini CLI can call
Everything on the key: search, filings, registries, weather, and ready-to-run tools, plus any provider key you vault yourself. Exact per-call prices are on /capabilities.
Config checked against Gemini CLI's MCP docs on 2026-09-12. Markdown version: /integrations/gemini-cli.md.
More integrations
Claude Code · Claude Desktop · Cursor · Windsurf · Zed · Cline · GitHub Copilot (VS Code) · OpenAI Codex CLI · Hermes Agent · Kimi CLI · Qwen Code · LibreChat
Model guides
Calling a model's API directly instead? Give it apifare tools with a plain tool loop: DeepSeek · Kimi · Qwen · OpenAI GPT · Gemini.