pinggy-tunnel
Pinggy Tunnel creates instant public URLs for local services using SSH reverse tunnels, with no daemon installation needed. Free tier offers 60-minute tunnels with random subdomains; Pro tier ($3/mo) adds persistent URLs and longer session times. Supports HTTP, HTTPS, TCP, and TLS tunneling with optional access controls like basic auth, bearer tokens, IP whitelisting, and CORS.
Pinggy Tunnel exposes your local service to the internet via SSH without installing any software.
AI-generated summary based on this skill's SKILL.md
Install
NousResearch/hermes-agent/pinggy-tunnel · repository language: Python
git clone https://github.com/NousResearch/hermes-agent
cp -r hermes-agent/optional-skills/devops/pinggy-tunnel ~/.claude/skills/pinggy-tunnelnpx skillfed install NousResearch/hermes-agent/pinggy-tunnelFrequently asked questions
AI-generated answers based on this skill's SKILL.md and metadata
How do I expose localhost to the internet with pinggy-tunnel?
Pinggy Tunnel creates instant public URLs for local services using SSH reverse tunnels, with no daemon installation needed. Run a single SSH command pointing to your local port, and Pinggy generates a public URL. The free tier provides 60-minute tunnels with random subdomains; Pro tier ($3/mo) adds persistent URLs and longer session times.
Can pinggy-tunnel receive webhook callbacks on my local machine?
Yes. Pinggy Tunnel is designed to receive webhook callbacks on a local development machine. When you create a tunnel to your local HTTP server, external services can POST to the public URL Pinggy generates, and those requests are forwarded directly to your local endpoint—no need to deploy to production first.
What's the easiest way to share a dev server with remote users?
Pinggy Tunnel lets you share a local dev server or demo with remote users by generating a public URL instantly. Simply tunnel your local port via SSH, then share the public link. Teammates can access your running app without you needing to deploy or configure complex infrastructure.
Does pinggy-tunnel support tunneling local LLM endpoints?
Pinggy Tunnel supports tunneling local LLM, MCP, or HTTP endpoints without installing daemons. Use a single SSH command to expose your local LLM or MCP server to the internet. The tunnel forwards all traffic transparently, making your local endpoint accessible to remote clients or services.
How can I secure my pinggy-tunnel with authentication?
Pinggy Tunnel offers optional access controls including basic auth, bearer tokens, IP whitelisting, and CORS configuration. These features help gate public tunnel access with authentication or IP restrictions, ensuring only authorized users or services can reach your local endpoint.
What license does pinggy-tunnel use?
Pinggy Tunnel is released under the MIT license, allowing free use, modification, and distribution in both open-source and commercial projects with minimal restrictions.
SKILL.md
rendered from the published skill — quoted content, verbatim
Pinggy Tunnel Skill
Expose a local service (dev server, webhook receiver, MCP endpoint, demo) to the public internet using a Pinggy SSH reverse tunnel. No daemon to install — the user's stock SSH client connects to a.pinggy.io:443 and Pinggy hands back a public HTTP/HTTPS URL.
Free tier: 60-minute tunnels, random subdomain, no signup. Pro tier ($3/mo) is an opt-in with a token.
When to Use
- User asks to "expose this locally", "share my dev server", "make this URL public", "tunnel port N", "get a public URL for a webhook"
- Need to receive a webhook callback during a local task (Stripe, GitHub, Discord, AgentMail)
- Sharing a one-off HTTP demo (MCP server, Ollama/vLLM endpoint, dashboard) with a remote party
- The host has SSH but no
cloudflared/ngrokbinary, and installing one would be overkill
If the host already has cloudflared configured, prefer the
(truncated - see the full file via the links below)
Read as markdown · JSON record · Browse the source repository
File tree — 1 file
optional-skills/devops/pinggy-tunnel/SKILL.md