Wires
HTTP routes, real-time channels, MCP tools, and CLI wirings.
A wire is how the outside world reaches one of your functions — the doorway in. Every function that anything can call has at least one wire pointing at it. There are a few different kinds, but they all do the same job: connect something out there to your code.
Labeled diagram: one central "Your function" box with four arrows pointing in from labeled sources: an HTTP route (a web address), a realtime channel (a live connection), an MCP tool (an AI tool), and a CLI command. Title: "Wires are the ways the outside world reaches your code."
Annotated screenshot of the Wires panel listing configured wires grouped by type (HTTP, Realtime, MCP, CLI), callout: "See every public entry point to your app in one place."
The four kinds of wire
Most of the time you'll only think about the first one — a normal web address. The other three are there when you need them.
| Wire type | What it's for | Example |
|---|---|---|
| HTTP route | A normal web address people or apps visit | Your website calls /api/signup when someone registers |
| Real-time channel | A live, always-open connection (a WebSocket) | A chat or dashboard that updates the instant something changes |
| MCP tool | A tool an AI assistant is allowed to call | An AI agent looks up an order by calling your function directly |
| CLI wiring | A command run from a terminal | A teammate runs myapp import-users to load data |
Do I set these up myself?
Usually not. When you describe what you want in the builder — "let my site create orders," "make this available as a tool for an AI" — Pikku Studio Cloud sets up the right wire for you. Every wire is typed, meaning Pikku Studio Cloud knows exactly what data goes in and out, so the connection is checked and safe by default.
You don't wire things up by hand or worry about getting the plumbing right. You describe what should be reachable, and Pikku Studio Cloud creates the typed wire — you just see the result listed here.
Seeing every entry point
The Wires panel lists every way into your app, grouped by type. That's valuable on its own: it's a single, honest view of every public door into your backend, so nothing is reachable that you didn't intend.
Going deeper
If you (or a developer on your team) want the technical, code-level view of how wires are defined, that lives in the developer path. See the CLI reference and Pikku for developers.
Where to go next
- Functions — the code your wires connect to.
- Async — work triggered on a timetable or by events, not by a wire.
- Pikku for developers — the open-source framework underneath, for the technical view.