Porch
Porch gives AI agents a public URL that catches webhooks, OAuth redirects, job callbacks and approval clicks.
Porch is a remote MCP server that hands agents a public URL on demand. Anything on the internet can send requests to it; the agent waits for them, reads them, and passes them on. There's no account to create and nothing to install.
Agents usually run on laptops, in sandboxes or in CI, where nothing outside can reach them. A webhook provider can't call localhost, an OAuth provider can't redirect to a sandbox, and a teammate can't click a button inside a terminal. Porch is the address they can all reach.
Stripe · GitHub · a person ──HTTP──▶ https://porch.okibi.ai/i/Xk3…/stripe
│ recorded
your agent ◀──MCP── create_inbox · wait_for_request · get_requestWhat agents use it for#
| Use case | How it works |
|---|---|
| Webhooks | Register the inbox URL with Stripe, GitHub, Slack or Twilio, then wait for the event. |
| OAuth redirects | Use the inbox as the redirect URI; the code and state arrive parsed. |
| Job callbacks | Give a long-running job the URL and block until it calls back, instead of polling. |
| Approvals | Send a person a page with your question and one button per answer, and get their choice back. |
| Local testing | Re-send a captured webhook to a dev server on localhost, byte for byte. |
How it works#
- The agent calls
create_inboxand gets a URL plus a secret inbox key. - It hands the URL to a service or a person. Any path under the URL and any HTTP method is accepted.
- It calls
wait_for_request, which returns as soon as something arrives, with the method, headers, query and body. - Inboxes clean up after themselves: each request is kept for up to 4 hours, and the inbox itself lives for up to 7 days.
The URL lets anyone send; only the key lets an agent read. Concepts explains the model in detail.