Outbox
Wire one MCP server so your agent can send messages across Slack, Telegram, email, KakaoTalk, and Discord from build and ops workflows.
Overview
io.github.fieldcure/outbox is a MCP server for the Build phase that sends outbound messages through Slack, Telegram, email, KakaoTalk, and Discord.
What is this MCP server?
- Single MCP surface for Slack, Telegram, Email, KakaoTalk, and Discord
- FieldCure.Mcp.Outbox v2.1.3 NuGet package with stdio transport
- Suited for alerts, deploy notifications, and support pings from agents
- dnx runtime hint for .NET MCP hosts
- Repository: github.com/fieldcure/fieldcure-mcp-outbox
- Server version 2.1.3
- 5 messaging channels: Slack, Telegram, Email, KakaoTalk, Discord
- Transport: stdio via FieldCure.Mcp.Outbox on NuGet
What problem does it solve?
Your agent or automation needs to notify people on different chat and email channels, but wiring five APIs separately is slow and brittle.
Who is it for?
Solo builders who want agent-driven alerts and customer pings across major messengers from a single MCP integration.
Skip if: Teams that only need inbound webhooks or a dedicated marketing ESP with no agent involvement.
What do I get? / Deliverables
After install, one MCP server lets the agent trigger outbound messages on the channels you configure.
- Unified MCP tools for sending on configured channels
- Operational outbox server linked in agent MCP config
Recommended MCP Servers
Journey fit
Outbound messaging integrations are configured while you connect product and agent stacks, before you lean on those channels for launch distribution. integrations covers multi-channel notification and messaging hooks agents call through MCP rather than one-off scripts per provider.
How it compares
Multi-channel outbound MCP bridge, not an SEO or analytics skill.
Common Questions / FAQ
Who is io.github.fieldcure/outbox for?
Builders using MCP agents who need to push notifications or messages to Slack, Telegram, email, KakaoTalk, or Discord from one server.
When should I use io.github.fieldcure/outbox?
Use it while integrating your product or agent workflows when outbound alerts or replies must hit real user channels.
How do I add io.github.fieldcure/outbox to my agent?
Add the FieldCure.Mcp.Outbox NuGet package, configure stdio in your MCP client, and supply each channel’s tokens or SMTP settings per provider docs.