pinggy-tunnel

Expose local services publicly via Pinggy SSH reverse tunnels over port 443.

Updated Apr 9, 2026
One-click install
npx skills add https://github.com/MarbleSodas/Mavis --skill pinggy-tunnel-marblesodas
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pinggy-tunnel
Source: https://github.com/MarbleSodas/Mavis/tree/main/optional-skills/devops/pinggy-tunnel
Command: npx skills add https://github.com/MarbleSodas/Mavis --skill pinggy-tunnel-marblesodas

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Pinggy Tunnel solves the problem of making a locally running service reachable from the public internet without installing extra tunneling software.

Core Features & Use Cases

  • Zero-install SSH reverse tunnels: Share HTTP/HTTPS, and optionally TCP/TLS services, using only your system’s stock ssh client.
  • Public URL for webhooks and demos: Quickly generate a shareable Pinggy URL so external systems can call back during a local task.
  • Built-in access control options: Protect the tunnel using username keyword gates for Basic auth, bearer tokens, IP allowlists, and CORS/HTTPS behaviors.
  • Debugging support: Optionally mirror inbound traffic for local inspection.
  • Common use cases: Exposing dev servers, receiving webhook callbacks (e.g., Stripe/GitHub/Discord), publishing an HTTP-based MCP endpoint, or sharing a one-off LLM endpoint (Ollama/vLLM/llama.cpp).

Quick Start

Ask your AI to start a Pinggy SSH reverse tunnel from your machine to a local service on 127.0.0.1:8000, then parse and return the generated pinggy.link URL while keeping the tunnel running until you stop it.

Frequently Asked Questions about pinggy-tunnel

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I expose a localhost dev server to the public internet?

You can expose a localhost dev server to the public internet by creating an SSH reverse tunnel over port 443, which generates a shareable public URL without requiring extra tunneling software.

How do I get a public URL for receiving webhook callbacks locally?

To get a public URL for webhook callbacks, establish an SSH reverse tunnel to your local service, producing a temporary public link that external systems like Stripe or GitHub can call back.

Do I need to install tunneling software to share my local HTTP endpoint?

No, you do not need to install tunneling software to share your local HTTP endpoint; the tunnel runs using your system's stock SSH client to create a public URL.

Can I add access control to an SSH reverse tunnel?

Yes, you can add access control to an SSH reverse tunnel by encoding username keyword gates in the SSH username to enforce Basic auth, bearer tokens, and IP allowlists.

What local services can I share over SSH without installing extra software?

You can share webhooks, dev servers, HTTP-based MCP endpoints, and browser-accessible demos over SSH, generating a temporary public URL for external access without extra software.