Integration guide
apifare for Cline
Give Cline 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 Cline
In the Cline panel, click the MCP Servers icon, open the Configure tab, and click Configure MCP Servers. Add this under mcpServers.
{
"mcpServers": {
"apifare": {
"command": "npx",
"args": ["-y", "apifare-mcp"],
"env": { "APIPAY_TOKEN": "<your-token>" },
"disabled": false,
"autoApprove": []
}
}
}Replace <your-token> with your token. Save the file: Cline connects to the server and lists its tools.
3 · Try it
Ask Cline 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 Cline 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 Cline's MCP docs on 2026-09-12. Markdown version: /integrations/cline.md.
More integrations
Claude Code · Claude Desktop · Cursor · Windsurf · Zed · GitHub Copilot (VS Code) · OpenAI Codex CLI · Gemini 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.