Bonfire Terminal vs @kirha/mcp-gateway
@kirha/mcp-gateway is a cloud-hosted AI Agent Framework acting as an MCP gateway for any provider, with undisclosed licensing and no offline capability. Bonfire Terminal keeps the gateway on your machine: an on-device agent, nothing leaving the device, your own LLM key at cost, and a transparent one-time perpetual license.
Bonfire Terminal vs @kirha/mcp-gateway: the 16-factor comparison
| Rating factor | @kirha/mcp-gateway | Bonfire Terminal |
|---|---|---|
| Category | AI Agent Framework | AI Terminal / Local Agent |
| Popularity | Not disclosed | Growing · indie |
| Hosting architecture | Cloud-Hosted | On-Device Local |
| Licensing model | Not disclosed | One-Time Perpetual |
| Data / training policy | Not disclosed | Fully local — nothing leaves device |
| Offline capability | No | Yes |
| Pricing tier range | Not disclosed | One-time license |
| Execution unit cost | Not disclosed | Unlimited Local Compute |
| API-key markup | Not disclosed | No — BYO key at cost |
| Supported LLM providers | Any | OpenAI; Anthropic; Google; Local; Any |
| Auth / permission types | API Key | API Key; Local/None |
| Phone / messaging bridges | None | Telegram; WhatsApp |
| Speech recognition engine | None | Whisper (local) |
| Local media processing | No | Yes |
| Sovereign score | 28 / 100 | 93 / 100 |
The sovereignty gap
Where @kirha/mcp-gateway lands on each weighted pillar (its bar) — the red marker is Bonfire's score. Auto-derived from the 16 factors above.
Which should you choose?
Choose @kirha/mcp-gateway if…
Choose @kirha/mcp-gateway if you want a cloud MCP gateway framework connecting to any provider and don't need on-device execution.
Choose Bonfire Terminal if…
Choose Bonfire Terminal if you want an on-device agent with your own key at cost, transparent perpetual licensing, and full local privacy.
Bonfire Terminal vs @kirha/mcp-gateway: FAQ
Is @kirha/mcp-gateway private?
@kirha/mcp-gateway is cloud-hosted with an unstated training policy, so traffic through the gateway runs on its servers. Bonfire Terminal runs on-device, so your data never leaves your machine or trains a vendor's model.
Is Bonfire Terminal cheaper than @kirha/mcp-gateway?
@kirha/mcp-gateway's licensing and pricing are undisclosed. Bonfire Terminal is transparent: a one-time perpetual license plus your own LLM key at provider cost with no markup, so total lifetime cost is predictable.
Can Bonfire Terminal replace @kirha/mcp-gateway?
For agent tasks across providers, Bonfire Terminal offers an on-device alternative. If you specifically need @kirha/mcp-gateway's cloud MCP-gateway routing architecture, confirm Bonfire's local agent model meets your integration needs before switching.
What can Bonfire Terminal do that @kirha/mcp-gateway can't?
Bonfire Terminal runs offline on-device, and adds local Whisper speech, local media processing, and Telegram and WhatsApp bridges, using your own LLM key at cost, none of which @kirha/mcp-gateway's cloud gateway framework provides.
How do I switch from @kirha/mcp-gateway to Bonfire Terminal?
Install Bonfire Terminal and reuse your LLM key, since both support any provider. Rebuild your agent workflows as local Bonfire tasks; since Bonfire runs on-device, migration is re-expressing logic rather than exporting from the cloud gateway.
Does Bonfire Terminal work offline vs @kirha/mcp-gateway?
@kirha/mcp-gateway has no offline capability and depends on its cloud. Bonfire Terminal is local-first, so its agent, local Whisper, and media processing run on your device offline, with only remote LLM calls requiring a connection.