pinggy-tunnel

Creates a public URL for a local HTTP service via a Pinggy SSH reverse tunnel.

1|Updated May 16, 2026
One-click install
npx skills add https://github.com/devMoez/titan --skill pinggy-tunnel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pinggy-tunnel
Source: https://github.com/devMoez/titan/tree/main/optional-skills/devops/pinggy-tunnel
Command: npx skills add https://github.com/devMoez/titan --skill pinggy-tunnel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of making a local service reachable from the public internet without installing extra tunneling software.

Core Features & Use Cases

  • Zero-install SSH reverse tunneling: Uses the user's stock SSH client to connect to Pinggy and returns a public HTTP/HTTPS URL.
  • Access control for public endpoints: Supports username-based Basic auth, bearer-token gating, IP whitelisting, and header controls like CORS and HTTPS redirects.
  • Use cases: Share a one-off webhook endpoint during local development, expose an MCP HTTP transport server for remote clients, or demo a local app (e.g., dev server, API, dashboard) to teammates.

Quick Start

Ask the agent to expose your local web server at 127.0.0.1:8000 using a Pinggy SSH reverse tunnel and return the HTTPS URL you can share externally.

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 server to the public internet for webhooks?

Exposing localhost to the public internet for webhooks is done by establishing an SSH reverse tunnel to the Pinggy host, which returns a shareable HTTPS URL pointing to your local service.

Can I add access control to a public URL created with an SSH reverse tunnel?

Yes, access control for a public SSH reverse tunnel URL can be applied via SSH username keywords, enabling Basic auth, bearer-token gating, IP whitelisting, and header controls like CORS.

Do I need to install extra tunneling software to get a public URL for my local API?

No extra tunneling software is needed to get a public URL for your local API, as the Skill uses your stock SSH client to connect to Pinggy and generate the public HTTPS link.

How do I expose an MCP HTTP transport server to remote clients during development?

You can expose an MCP HTTP transport server to remote clients by running an SSH reverse tunnel that maps the Pinggy public URL to your local 127.0.0.1 origin port.

What is the best way to share a local dev server temporarily without deploying it?

The best way to share a local dev server temporarily without deployment is using a zero-install SSH reverse tunnel, which generates a temporary public pinggy.link URL for external access.

Does Pinggy SSH tunneling work with any local port for temporary sharing?

Pinggy SSH tunneling works with any reachable local 127.0.0.1 port, making it suitable for temporary sharing of dev servers, local LLM endpoints, and API dashboards during demos.