email-alert-mcp
Sends email alerts using the Resend API, allowing agents to notify humans via email with customizable severity, title, message, and context.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@email-alert-mcpSend an error alert: data pipeline failed with error code 503."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
alert-my-human
A lightweight MCP server that lets agents send multichannel alerts — useful for notifying a human when a scheduled job fails, data is missing, or something otherwise needs attention.
Supports email, Slack, Telegram, SMS, and generic webhooks. Enabled a channel by setting its env vars. Callers pick which configured channels to deliver to on each call.
Deploy
One-click deploy prompts only for AUTH_API_KEY (the one required var). Add whichever channel vars you want afterward in the Vercel dashboard (Project → Settings → Environment Variables) — see Setup below.
Related MCP server: Mail MCP Server
Tools
list_channels
Returns which channels are currently configured. No params. Call this before send_alert to know which channel names are valid.
send_alert
Param | Type | Required | Description |
| array of channel names | Yes | Which channels to deliver to (e.g. |
|
| No (default | Controls the color/emoji used in the alert. |
| string | Yes | Short headline for the alert. |
| string | Yes | Body of the alert. |
| object of string key/value pairs | No | Extra details rendered as a list (e.g. job name, error code). |
Channels are delivered independently, so one failing channel doesn't block the others — the response reports which channels sent and which failed. Each delivery is bounded by a 10s timeout and retried once on a transient failure (network error, timeout, HTTP 429, or 5xx).
Setup
Copy
.env.exampleto.envand fill in:AUTH_API_KEY— any random secret string; callers must send it asAuthorization: Bearer <key>.Then configure one or more channels (leave a channel's vars unset to disable it):
Email —
SENDING_EMAIL,RESEND_API_KEY(from resend.com),ALERT_EMAIL(one address, or several comma-separated).Slack —
SLACK_WEBHOOK_URL(an incoming webhook).Telegram —
TELEGRAM_BOT_TOKEN,TELEGRAM_CHAT_ID.SMS —
TWILIO_ACCOUNT_SID,TWILIO_AUTH_TOKEN,TWILIO_FROM_NUMBER,ALERT_PHONE_NUMBER(from twilio.com).Webhook —
WEBHOOK_URLS, comma-separated; each receives the alert as JSON.
pnpm installpnpm dev
Connecting an MCP client
Register the server with a static bearer token header, for example in Claude Code's mcpServers config:
{
"type": "http",
"url": "https://your-deployment.example.com/api/mcp",
"headers": {
"Authorization": "Bearer <AUTH_API_KEY>"
}
}Testing
Run npx @modelcontextprotocol/inspector@latest http://localhost:3000 undefined, then connect it to http://localhost:3000/api/mcp with an Authorization: Bearer <AUTH_API_KEY> header.
Roadmap
Phone call alerts
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/LMol-4/email-alert-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server