# ammo.tools > Capture email and webhooks from staging and test environments. Point your SMTP and webhook URLs here; traffic is caught and never reaches real users. Inspect messages, payloads, headers, and attachments. Fetch captures through the API or MCP for test assertions. ## What it is - [Email capture](https://app.ammo.tools/api/docs/email/): Point staging SMTP at smtp.ammo.tools:587; messages are caught and never delivered onward - [Webhook capture](https://app.ammo.tools/api/docs/webhooks/): Send webhooks to https://ammo.tools/in//; inspect method, headers, body; replay or forward to localhost - [API access](https://app.ammo.tools/api/docs/): Fetch captured messages and webhooks from tests; filter by recipient, sender, subject, method, path, time; poll with wait - [MCP server](https://app.ammo.tools/api/docs/mcp/): Local stdio server lets coding agents read captures with read-only tools - [Localhost forwarding](https://app.ammo.tools/api/docs/webhooks/): CLI client forwards captured webhooks to a local development server ## Getting started for agents - [Create an account](https://app.ammo.tools/accounts/signup/) or [sign in](https://app.ammo.tools/accounts/login/) - Create a project to get an SMTP inbox and a webhook capture URL - Generate an API key on the project's API keys page; each key is scoped to one environment - Use Bearer authentication: `Authorization: Bearer ak_live_...` - [MCP setup](https://app.ammo.tools/api/docs/mcp/): download ammo-mcp.py, configure with env vars AMMO_TOOLS_API_KEY and AMMO_TOOLS_API_BASE_URL (https://app.ammo.tools/api/v1) - MCP tools: get_identity, list_inboxes, list_messages, get_message, get_message_links, get_message_codes, get_message_checks, compare_messages, list_endpoints, list_requests, get_request ## Docs - [Setup guides](https://app.ammo.tools/api/docs/): API overview, email and webhook setup - [Email setup guide](https://app.ammo.tools/api/docs/email/): SMTP configuration, capture inspection, CI tests - [Webhook setup guide](https://app.ammo.tools/api/docs/webhooks/): HTTP capture, payload inspection, localhost forwarding - [MCP setup guide](https://app.ammo.tools/api/docs/mcp/): Configure the local MCP server for coding agents ## Pricing - [Pricing](https://ammo.tools/pricing/): Free, Solo, and Team plans - Free: 1 day retention, 1 project, 1 inbox, 1 endpoint, 50 messages/inbox, 100 requests/endpoint, message size 5 MB, request body 256 KB, 1 API key, 1 member - Solo: 14 days retention, 3 projects, 5 inboxes, 5 endpoints, 1000 messages/inbox, 2000 requests/endpoint, message size 15 MB, request body 1 MB, 5 API keys, 3 members - Team: 30 days retention, unlimited projects, 25 inboxes, 25 endpoints, 5000 messages/inbox, 10000 requests/endpoint, message size 25 MB, request body 1 MB, unlimited API keys, unlimited members ## Limits - 600 requests/minute per API key - 1200 requests/minute per workspace - Up to 4 concurrent waits, max 30s each ## Guides - [Catch staging emails](https://app.ammo.tools/guides/catch-staging-emails/): Prevent staging and test emails from reaching real users. Configure your SMTP to route all email to ammo.tools for inspection. - [Test password reset emails](https://app.ammo.tools/guides/test-password-reset-emails/): Verify password reset flows in automated tests. Capture reset emails and extract tokens through the API. - [Test webhooks locally](https://app.ammo.tools/guides/test-webhooks-locally/): Forward captured webhooks to your local development server. Debug payment, notification and integration webhooks. - [Fetch verification codes in tests](https://app.ammo.tools/guides/fetch-verification-codes-in-tests/): Extract OTP and verification codes from captured emails using the API. Automate MFA and confirmation flows in your test suite. - [Email testing for code agents](https://app.ammo.tools/guides/email-testing-for-code-agents/): Let AI coding agents verify email sending. Read captured messages through MCP tools without browser access. - [Preview HTML emails on mobile](https://app.ammo.tools/guides/preview-html-emails-on-mobile/): Share captured emails with designers and testers. Preview HTML rendering on any device without sending to real addresses. - [Check emails for spam content](https://app.ammo.tools/guides/check-emails-for-spam-content/): Scan captured emails for spam triggers before production. Identify deliverability issues with automated content analysis. - [Simulate SMTP failures](https://app.ammo.tools/guides/simulate-smtp-failures/): Test how your application handles SMTP errors. Simulate temporary and permanent delivery failures for resilience testing. ## Support - [info@ammo.solutions](mailto:info@ammo.solutions): General inquiries - [security@ammo.solutions](mailto:security@ammo.solutions): Security issues - [Terms](https://ammo.tools/terms/): Terms and conditions - [Privacy](https://ammo.tools/privacy/): Privacy statement ## Optional - [Full documentation](https://app.ammo.tools/llms-full.txt): Complete inline documentation including agent instructions and API reference