Send email via HTTP or MCP
Send one email from Breyta's sender to up to 25 valid recipient email addresses. Run it manually, call it over HTTP, or connect it as an MCP tool.
Created by Chris Moen • Version 4 • 3 steps
What you get
- Send one email from Breyta's sender to up to 25 valid recipient email addresses. Run it manually, call it over HTTP, or connect it as an MCP tool.
Integrations
- sendgrid
- email-sender
- Email Sender
How it works
- 3 workflow steps run in Breyta to produce the app result.
Send email from Breyta
Send one email from Breyta's sender to up to 25 recipient email addresses. Use it manually, call it over HTTP, or connect it as an MCP tool from an agent.
What you get
- Up to 25 recipients per run
- Recipients can be any valid email addresses. They do not need to be Breyta users.
- A fixed Breyta sender:
Breyta <no-reply@breyta.ai> - Plain text email body, with optional HTML
- Optional reply-to address
- Optional sandbox mode for request validation without delivery
- A readable run result with recipients, subject, and status
Setup
No email provider API key is required. This app includes the email sending connection.
You need access to this paid Breyta app and the email addresses you want to send to.
Emails are sent from Breyta <no-reply@breyta.ai>. Add a reply-to email if replies should go to your own inbox.
Pricing
Choose the prepaid pack that matches how often you want to send:
- Starter: $4.99 for 1,000 successful runs
- Plus: $9.99 for 2,500 successful runs
- Bulk: $19.99 for 6,000 successful runs
Each run can send to up to 25 recipients. The first 10 successful runs are free trial runs.
Usage is counted per successful run. Failed, cancelled, timed-out, and terminated runs do not consume the run allowance.
Inputs
- To emails: one or more valid email addresses, separated by commas, semicolons, or new lines
- Optional recipient name, used only when sending to one recipient
- Optional reply-to email
- Subject
- Plain text body
- Optional HTML body
- Sandbox mode
- Optional request ID for your own logs
HTTP and MCP use
Use HTTP when you want to call the app from another service. Use MCP when you want an agent to send email as a tool call.
The MCP tool name is send_email.
Limits
The app sends from Breyta <no-reply@breyta.ai> and allows up to 25 recipients per run. Recipients can be any valid email addresses and do not need Breyta accounts. Recipients do not see the other recipients. Click and open tracking are disabled. Sandbox mode validates the request without delivering an email.
FAQ
What is the Send email via HTTP or MCP app?
This app lets you send individual emails to as many as 25 recipients at once, using Breyta's verified sender system. You can trigger the process manually from your dashboard, via a standard HTTP request, or by connecting it to a Model Context Protocol (MCP) tool.
Which services does the email automation use?
The app handles email delivery through integrated services like SendGrid. It functions as a pre-configured email sender, removing the need for you to manage your own mail server or complex API credentials.
How do I connect this app to my own tools?
You can run the app as a standalone tool or integrate it into your existing stack using the Model Context Protocol (MCP). Since it supports HTTP calls, you're able to trigger email notifications from any external code or workflow that can send a web request.
Is there a complicated setup process for this workflow?
Setup is simple because the core email steps are already configured. You only need to provide your recipient addresses and the message content, then choose whether you want to trigger it manually or through an automation protocol.