Bonfire Terminal vs @marsnme/mcp-gateway
@marsnme/mcp-gateway is an agent-framework MCP gateway that connects to any provider through an API key. Bonfire Terminal is not a gateway but a finished on-device agent: it runs locally, bills your provider key at cost with no markup, and arrives as a one-time perpetual license.
Bonfire Terminal vs @marsnme/mcp-gateway: the 16-factor comparison
| Rating factor | @marsnme/mcp-gateway | Bonfire Terminal |
|---|---|---|
| Category | AI Agent Framework | AI Terminal / Local Agent |
| Popularity | Not disclosed | Growing · indie |
| Hosting architecture | Not disclosed | On-Device Local |
| Licensing model | Not disclosed | One-Time Perpetual |
| Data / training policy | Not disclosed | Fully local — nothing leaves device |
| Offline capability | Not disclosed | 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 | 32 / 100 | 93 / 100 |
The sovereignty gap
Where @marsnme/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 @marsnme/mcp-gateway if…
Choose @marsnme/mcp-gateway if you are wiring MCP connections across providers and want a flexible any-provider gateway.
Choose Bonfire Terminal if…
Choose Bonfire Terminal if you want a complete on-device agent with provider choice and a perpetual license.
Bonfire Terminal vs @marsnme/mcp-gateway: FAQ
Is @marsnme/mcp-gateway private?
@marsnme/mcp-gateway has an unpublished hosting model, and gateways generally relay traffic through their infrastructure. Bonfire Terminal is local-first, so your requests stay on your device except for the explicit provider calls you choose to make.
Is Bonfire Terminal cheaper than @marsnme/mcp-gateway?
@marsnme/mcp-gateway does not publish pricing tiers. Bonfire Terminal is a one-time perpetual license, then your own LLM usage at cost with no markup, so ongoing spend is just metered tokens rather than gateway overhead.
Can Bonfire Terminal replace @marsnme/mcp-gateway?
If you want an agent that runs tasks, yes. Bonfire Terminal is a full on-device agent supporting any provider. @marsnme/mcp-gateway is specifically an MCP routing layer, so it differs if you only need connection brokering between tools and models.
What can Bonfire Terminal do that @marsnme/mcp-gateway can't?
Bonfire Terminal is a complete on-device agent with local Whisper, local media processing, and Telegram and WhatsApp bridges. @marsnme/mcp-gateway is a provider gateway without these; it brokers connections rather than running a full workflow.
How do I switch from @marsnme/mcp-gateway to Bonfire Terminal?
Install Bonfire Terminal and add your provider key directly, since Bonfire connects to models itself without a separate gateway. Everything runs on your device, so there is no routing service left to operate once you move over.
Does Bonfire Terminal work offline vs @marsnme/mcp-gateway?
@marsnme/mcp-gateway routes to remote providers and does not document offline use. Bonfire Terminal runs on-device with local models and Whisper, so core features work without internet where a gateway cannot.