
Outbox
io.github.fieldcurePublished by GitHub account fieldcurev2.1.3Updated Oct 24, 2026
Multi-channel messaging MCP server for Slack, Telegram, Email, KakaoTalk, and Discord.
Overview
Lets an assistant send messages through Slack, Telegram, email, KakaoTalk, and Discord from one set of tools.
- What you can do
- Outbox is a local MCP server that unifies several messaging channels behind four tools: list_channels, add_channel, send_message, and remove_channel. send_message abstracts over Slack Web API, Telegram Client API, SMTP (Gmail, Naver, custom), Microsoft Graph, KakaoTalk REST, and Discord webhooks. Channel setup can run through a CLI with browser OAuth flows, and OAuth tokens are refreshed across runs.
- When to use it
- Use it when an assistant should send notifications or messages to people across more than one platform without installing a separate MCP server per channel. It is especially relevant for Korean users who need KakaoTalk, or for consolidating Slack, email, and Discord sending into one tool.
- Requirements
- Runs locally as a .NET tool (FieldCure.Mcp.Outbox) over stdio; requires .NET 8.0 Runtime or later on Windows, Linux, or macOS. Channel credentials are supplied per channel, either as environment variables named OUTBOX_ _ or through interactive MCP elicitation. Microsoft and KakaoTalk setup need a local browser for OAuth.
Installation
In SourceWeft
- Open Outbox in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
FieldCure MCP Outbox Server
A multi-channel messaging Model Context Protocol (MCP) server that sends messages through Slack, Telegram, Email (Gmail, Naver, Microsoft Graph API), KakaoTalk, and Discord. Built with C# and the official MCP C# SDK.
Features
- Multiple messaging channels — Slack, Telegram, Email (Gmail, Naver, Microsoft Graph API), KakaoTalk, Discord
- 4 MCP tools —
list_channels,add_channel,send_message,remove_channel - Cross-platform credential flow — runtime secrets can come from env vars or MCP elicitation; OAuth tokens are stored separately for refresh lifecycle
- CLI channel setup — interactive console for browser/OAuth flows where applicable
- SMTP presets — Gmail, Naver with one-command setup
- Microsoft Graph API — OAuth 2.0 browser flow for Outlook / M365 email with automatic token refresh
- KakaoTalk OAuth — localhost callback flow with automatic token refresh
- Telegram Client API — send to Saved Messages via WTelegramClient
- Stdio transport — standard MCP subprocess model via JSON-RPC over stdin/stdout
Why Outbox?
Existing MCP servers are channel-specific — one for Slack, another for Gmail, yet another for Telegram. Each requires separate installation, configuration, and the LLM must know which tool to call for each channel.
Outbox takes a different approach:
- One tool, multiple channels —
send_messageabstracts away channel differences. The LLM doesn't need to know Slack API vs SMTP vs Kakao REST. - Credential isolation — OAuth refresh tokens live in
tokens.jsonwith current-user-only file permissions; MCP tool flows can resolve secrets at runtime via env vars or elicitation. - Single install —
dotnet tool install -ggives you 4 channels. No need to install and configure separate servers per channel. - KakaoTalk support — Currently the only MCP server with KakaoTalk messaging, essential for Korean users.
Installation
dotnet tool (recommended)
After installation, the fieldcure-mcp-outbox command is available globally.
From source
Requirements
- .NET 8.0 Runtime or later
- Cross-platform (Windows, Linux, macOS)
Configuration
Claude Desktop
Add to claude_desktop_config.json:
VS Code (Copilot)
Add to .vscode/mcp.json:
From source (without dotnet tool)
Tools
Channels
OAuth tokens for Microsoft/KakaoTalk are stored in tokens.json so the server can refresh them across runs (current-user-only file permissions — Windows ACL / Unix 0600).
Static secrets (Slack bot tokens, Discord webhook URLs, SMTP passwords, etc.) resolve at send time in this order: in-memory cache → env var OUTBOX_{CHANNEL_ID}_{FIELD} → plaintext in channels.json → MCP elicitation. The CLI add_channel flow writes directly into channels.json for a zero-configuration local experience. This is an intentional local-trust choice with the same same-user boundary as tokens.json, documented in ADR-001 Principle 2. For shared hosts, CI, or headless deployments, set the env vars explicitly and leave channels.json secret fields empty.
Static Secret Environment Variables
When a channel requires a static secret at send time, Outbox looks for an environment variable named:
Examples:
OUTBOX_MICROSOFT_1_CLIENT_SECRETOUTBOX_KAKAOTALK_1_API_KEYOUTBOX_KAKAOTALK_1_CLIENT_SECRETOUTBOX_SMTP_GMAIL_1_PASSWORD
If the variable is unset and the MCP client supports elicitation, Outbox prompts for it interactively and caches it for the current session.
CLI Commands
Data Storage
tokens.json is stored in plain JSON and protected by filesystem permissions:
- Windows: ACL restricted to the current user
- Linux/macOS: mode
0600
This protects against other local users on the same machine, but not against compromise of the same OS user account.
Project Structure
Development
See Also
Part of the AssistStudio ecosystem.
License
Source: README.md at commit 595d983
Tools
0Version history
1- v2.1.3LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts