Launch · 2 min read

We're opening up ammo.tools

We're opening up ammo.tools: catch staging email and webhooks without hitting real users.

We've been catching our own staging email and webhooks with a small internal tool. It worked. So we're opening it up.

ammo.tools is that tool, now a product. Point your staging SMTP and webhook URLs at it. Messages and requests land in one place. Captured email is never relayed to the people in the To field. Webhooks stay put unless you forward them or replay a request yourself.

Inbox: captured staging email (example data)
Inbox: captured staging email (example data)

Why we built it

Staging kept almost sending real mail and almost firing real webhooks. We wanted one place to see what an environment would have sent: HTML and text, headers, attachments, payload bodies, without risking a customer inbox or a live integration.

We built that for ourselves. Same problem shows up for anyone with mail flows, payment callbacks, or notifications. Opening ammo.tools means those teams can use it too.

What you get

Create a project and get an SMTP inbox and a webhook capture URL. Staging talks to those instead of production mailboxes or provider endpoints. Preview messages at desktop and mobile widths, inspect headers and attachments, compare two messages, and check content for common spam triggers. Simulate temporary or permanent SMTP failures for a short window when you need to see how your app handles them.

For automation: an API to fetch captures from tests, an MCP server so coding agents can read messages and requests without a browser, and a CLI that forwards captured webhooks to localhost while you debug.

Plans: Free to start, Solo and Team when you need more room and longer history. Same product on every plan; paid tiers buy capacity. Details on ammo.tools.

Webhook capture: JSON payload and headers (example data)
Webhook capture: JSON payload and headers (example data)

Who it's for

Developers and small teams who ship apps with email or webhooks and want staging and tests sandboxed. Password resets, verification codes, payment callbacks, and checking that a message looks right before go-live. If you use coding agents, the MCP path lets an agent assert on captures the same way a test suite would.

Hosted in Europe

Captures are stored in the EU. Hosted in Europe. Expired captures are deleted according to your plan's retention.

Try it

Start free at ammo.tools. No card for the free plan. Questions: info@ammo.solutions.

Need something built? Get in touch.

AMMO is a small software studio in the Netherlands. We build and run client systems and our own tools.

AMMO Solutions

Made in the Netherlands

AMMO products

© 2026 AMMO Solutions Kloosterdijk 6, 1141 PJ Monnickendam, Netherlands KvK 68679750 VAT NL001694241B13