Enterprise DNA
M MCP Servers Developer low

pipepie/pipepie

by Various

Self-hosted encrypted tunnel for webhooks, AI pipelines, and local development. End-to-end Noise encryption, pipeline tracing, web dashboard, MCP server for AI tools.

P

MCP

pipepie/pipepie

Added 1 June 2026

#ai-pipeline #cli #developer-tools #devtools #encryption #golang #mcp #mcp-server

Overview

Pipepie is a self-hosted encrypted tunnel for webhooks, AI pipelines, and local development. It uses end-to-end Noise encryption, provides pipeline tracing and a web dashboard, and includes an MCP server for AI tool integration.

Best for

Best for
Developers who need a secure, self-hosted tunnel for webhooks or AI pipelines with observability

Use cases

  • Expose local webhook endpoints securely to the internet
  • Route and trace AI pipeline data between services
  • Connect local development servers to remote AI tools via MCP

Notes

Pipepie is a self-hosted encrypted tunnel for webhooks, AI pipelines, and local development. It uses end-to-end Noise encryption, provides pipeline tracing and a web dashboard, and includes an MCP server for AI tool integration.

7 stars on GitHub. Last updated 2026-04-02. Licensed AGPL-3.0.

Use cases

  • Expose local webhook endpoints securely to the internet
  • Route and trace AI pipeline data between services
  • Connect local development servers to remote AI tools via MCP

Pros

  • End-to-end encryption with Noise protocol for secure tunneling
  • Built-in pipeline tracing and web dashboard for monitoring
  • Self-hosted, giving full control over data and infrastructure

Cons

  • Small community and limited documentation due to early stage
  • Requires self-hosting and maintenance of the tunnel server
  • Go runtime dependency may add overhead for simple use cases

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.

Pros

  • End-to-end encryption with Noise protocol for secure tunneling
  • Built-in pipeline tracing and web dashboard for monitoring
  • Self-hosted, giving full control over data and infrastructure

Cons

  • Small community and limited documentation due to early stage
  • Requires self-hosting and maintenance of the tunnel server
  • Go runtime dependency may add overhead for simple use cases