A reference config covering every core Air Pipe concept - the five input sources, interpolation forms, assertions, run conditions, transforms, and metrics - against public APIs (no database or managed variables needed). Not a production pack: use it as a learning reference and to seed a RAG chatbot with authoritative Air Pipe syntax.
Forwards GitHub events (push, pull request, issues) to a Discord channel as formatted embeds. No database required — it's a pure HTTP passthrough. Set up in under 5 minutes with two free accounts.
Turn your Postgres data into secure MCP tools any AI client (Claude Desktop, Claude Code, Cursor) can call. Two-tier auth: one shared token for yourself, or per-user tenant-scoped tokens for your customers - minted via an HS256 exchange or verified directly against your OIDC provider's JWKS (Auth0, Clerk, Cognito). Every tool reuses the same in-config token checks as a normal Air Pipe route. Tool discovery (tools/list) is gated behind the same per-user token via list_authorizer, so unauthenticated clients cannot enumerate your tools or their input schemas (engine >= 1.7.0).
The smallest useful MCP server: two tools over one Postgres table, guarded by a single shared token, in one config file. Point Claude Desktop, Claude Code, Cursor or any MCP client at your database with no SDK, no Node project and nothing to host. An Air Pipe interface is an HTTP route; add an mcp block and the same interface is also an MCP tool, secured by the same in-config token check. Tool discovery (tools/list) is gated by that same token via list_authorizer, so an unauthenticated client cannot even enumerate your tools or their input schemas. Includes a seed endpoint that creates the table and sample data in one curl.
A production-shaped CRUD API over MySQL — users, posts, and comments, with optional JWT validation. Works with MySQL 8.x, MariaDB 10.5+, and PlanetScale. No ORM, no boilerplate: point Air Pipe at your MySQL connection string and you have an API.
A production-shaped CRUD API over Postgres with three resource types (users, posts, comments) and optional JWT validation. No external services required — just a Postgres database. Deploy and start making requests in under 10 minutes.
Two ways to send transactional email from one Air Pipe route, with an identical { to, subject, html } body: the native email action over SMTP (STARTTLS, works with any mail server) or the Resend HTTP API. Pick the file for your provider; user values are JSON-escaped so quotes and newlines can't break the payload.
A production-shaped CRUD API over SQLite — users, posts, and comments, with optional JWT validation. Zero setup: no database server to provision, just a portable single-file .db. The zero-config, file-based member of the REST API Starter family. Self-hosted only — the SQLite driver runs in-process, so this pack is for your own AirPipe instance (local-first, edge, prototypes).
A zero-dependency webhook capture tool. Point any webhook sender at `/webhooks/log` and the full request — body, headers, and query params — is stored in your Postgres database. Replay stored events to your local dev server without re-triggering the original source. Useful for debugging Stripe, GitHub, Shopify, or any other webhook-based integration. Captures headers like `X-Stripe-Signature`, `X-GitHub-Event`, and `X-Hub-Signature-256` alongside the body so you have everything needed to replay or verify the original request.