ngsrv vs LivePort
Both tools target AI coding agents that need a public URL for localhost. LivePort optimizes for zero-config; ngsrv optimizes for production-shaped tunnels you can commit, secure, and operate.
At a glance
| ngsrv | LivePort | |
|---|---|---|
| MCP server | @ngsrv/mcp | @liveport/mcp |
| Free trial without signup | 12h device trial | Zero-config connect |
| Interstitial on free | Skipped for agent tokens | None |
Declarative ngsrv.yml | First-class | Limited |
| Edge security policies | 1/type Free; 10/type Pro | Not focus |
| Custom domains | Free: 1; Pro: more | Varies |
| Dashboard & team billing | Yes | Minimal |
Where ngsrv wins
You want YAML in git, IP allowlists, rate limits, and WAF at the edge — not only a throwaway preview link.
You already use ngsrv for webhooks and client demos; the same toolchain works for MCP.
You need agent tokens with explicit TTL and dashboard audit (last_used), not only anonymous sessions.
Where LivePort wins
Absolute minimum friction for a one-off npx connect 3000 with no account story.
Migration
# Cursor ~/.cursor/mcp.json: npx @ngsrv/mcp@latest
# Then tunnel.start port=3000 in the editor
# Or CLI
ngsrv http 3000
See Cursor MCP docs.