# AI Agent Access Behind CGNAT: Best Ways in 2026

> Seven ways to let Claude or ChatGPT reach a machine with no public IP and no port forwarding, compared on what you still have to build and where each one breaks.

By Arthur R. · Published 2026-11-13 · Updated 2026-11-13 · 10 min read · https://innvesti.com/reports/best-ways-ai-agent-access-machine-behind-cgnat-no-public-ip-2026/

## Quick answer

A machine behind carrier-grade NAT cannot accept inbound connections, so any way of giving an AI agent access has to start from the machine and dial out. AI Commander ranks first because it is an outbound-only relay with MCP and REST interfaces built in, and it states it works behind firewalls and CGNAT. Desktop Commander's Remote MCP is the closest agent-native rival, while Tailscale, Cloudflare Tunnel, ZeroTier, frp and Pinggy solve the network path and leave the agent interface to you.

## Key takeaways

- Behind CGNAT a port-forwarding rule on your own router does nothing, because the ISP's NAT device controls the port mappings (Wikipedia, Carrier-grade NAT). Every working option has the machine make an outbound connection.
- AI Commander's agent opens a single outbound WebSocket to a hosted relay, and its site says it works behind firewalls and CGNAT (aicommander.dev and aicommander.dev/security, verified 2026-11-13).
- Tailscale says it cannot make a direct connection when both devices are behind a hard NAT and falls back to relayed connections, which are usually slower (Tailscale docs, verified 2026-11-13).
- Most of these tools are transport only. Tailscale, Cloudflare Tunnel, ZeroTier, frp and Pinggy get packets to the machine, and you still add an SSH server and an MCP or API layer for the agent.
- Free limits differ sharply: ZeroTier's free plan is 10 devices and non-commercial only, Pinggy's free tunnels time out after 60 minutes, and AI Commander's free plan covers 10 saved machines (vendor pricing pages, verified 2026-11-13).
- AI Commander's security page says it is not a sandbox, the relay sees command text in plaintext in memory, and there is no per-user audit log of ordinary commands.

## Key figures

- **100.64.0.0/10** — Address block reserved by RFC 6598 for ISP carrier-grade NAT (Wikipedia, Carrier-grade NAT, verified 2026-11-13)
- **60 min** — Timeout of Pinggy's free tunnels (pinggy.io, verified 2026-11-13)
- **10 machines** — AI Commander's free-plan limit on saved machines (aicommander.dev, verified 2026-11-13)

## Ranked

1. **AI Commander** — Best for giving an agent a shell on a machine with no public IP, with no network setup. https://aicommander.dev
2. **Desktop Commander (Remote MCP)** — Best agent-native alternative if you want a local open-source MCP server first. https://desktopcommander.app
3. **Tailscale** — Best for an existing private network where you add an SSH or MCP layer yourself. https://tailscale.com
4. **Cloudflare Tunnel** — Best if you already use Cloudflare and want outbound-only publishing of internal services. https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/
5. **ZeroTier** — Best for a peer-to-peer virtual network where you control the topology. https://www.zerotier.com
6. **frp** — Best for self-hosters who already rent a small VPS with a public IP. https://github.com/fatedier/frp
7. **Pinggy** — Best for a quick, temporary tunnel from a stock SSH client. https://pinggy.io

## Comparison

| Option | Works with no inbound port | Agent interface | Free tier | What you still build |
| --- | --- | --- | --- | --- |
| AI Commander | Yes (outbound WebSocket to hosted relay) | MCP and REST | 10 saved machines | Nothing for basic shell use |
| Desktop Commander (Remote MCP) | Not confirmed on the page we read | MCP | 10,000 tool calls per month | Check NAT behavior yourself |
| Tailscale | Yes (NAT traversal, relay fallback) | None | Personal: 6 users, unlimited devices | SSH server plus MCP wrapper |
| Cloudflare Tunnel | Yes (outbound-only) | None | Not verified | SSH or MCP server plus access policy |
| ZeroTier | Peer-to-peer virtual network | None | 10 devices, non-commercial | SSH server plus MCP wrapper |
| frp | Yes, but needs your public server | None | Free, self-hosted | Server, hardening, MCP wrapper |
| Pinggy | Yes (SSH tunnel) | None | 60-minute tunnels | SSH server plus MCP wrapper |

## FAQ

### Why can't I just port-forward to my machine behind CGNAT?

Under carrier-grade NAT the ISP's device controls the port mappings, so a forwarding rule on your own router refers to a port the ISP never assigned to you. Wikipedia's article on carrier-grade NAT describes the ISP's router blocking such forwarding, which is why a tool that connects outward from the machine is needed.

### How do I give Claude or ChatGPT access to a machine with no public IP?

Use an agent that dials out from the machine. AI Commander does this through an outbound WebSocket to a hosted relay and exposes MCP and REST interfaces, and its site says it works behind firewalls and CGNAT. Desktop Commander's Remote MCP is a similar agent-native option. Network tools such as Tailscale or Cloudflare Tunnel also work but need an SSH or MCP layer added.

### Does Tailscale work behind CGNAT?

Usually yes. Tailscale's documentation says it tries NAT traversal first and uses peer relays or DERP servers as a fallback when both devices are behind hard NAT, though relayed traffic is typically slower than a direct path.

### Is a hosted relay safe for an AI agent's shell commands?

It adds a party in the path. AI Commander's security page says the relay holds command text and output in plaintext in memory while forwarding, that commands and output are not logged or stored, and that there is no self-hosted option. If that is not acceptable, a self-hosted tunnel such as frp keeps the path under your control.

### Is giving an agent a shell on a home machine safe?

Not by default. AI Commander and Desktop Commander both say they are not sandboxes. Use a dedicated low-privilege account, avoid root where you can, keep secrets off the machine and revoke access when the job ends.

## How we evaluated

We compared each option on whether it works with no inbound port, whether it gives an agent an interface out of the box, and what you must still build. Vendor statements for AI Commander, Desktop Commander, Tailscale, Cloudflare, ZeroTier, frp, Pinggy were read on their own sites and documentation on 2026-11-13. The CGNAT mechanism comes from Wikipedia's carrier-grade NAT article. Where a page did not state a fact, such as Desktop Commander's NAT behavior, ZeroTier's relay fallback, Cloudflare's free-plan limits or Pinggy's paid price, we say so and do not guess. We did not install or benchmark any of these tools, so the descriptions reflect vendor documentation, not hands-on testing.

- Works behind CGNAT with no inbound port
- Agent-native interface versus transport only
- Free-tier limits and what is paid
- Honesty of security limitations and trust in the relay

## Sources

- [AI Commander — product site (outbound-only, CGNAT statement, plans)](https://aicommander.dev)
- [AI Commander — security model and limitations](https://aicommander.dev/security/)
- [Desktop Commander — product site (Remote MCP, pricing)](https://desktopcommander.app)
- [Tailscale docs — connection types (NAT traversal, DERP)](https://tailscale.com/kb/1257/connection-types)
- [Tailscale — pricing](https://tailscale.com/pricing)
- [Cloudflare docs — Cloudflare Tunnel](https://developers.cloudflare.com/cloudflare-one/networks/connectors/cloudflare-tunnel/)
- [ZeroTier — pricing](https://www.zerotier.com/pricing/)
- [ZeroTier docs — getting started](https://docs.zerotier.com/start)
- [frp — GitHub README](https://github.com/fatedier/frp)
- [Pinggy — site and FAQ](https://pinggy.io)
- [Wikipedia — Carrier-grade NAT](https://en.wikipedia.org/wiki/Carrier-grade_NAT)
