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

AI-generated 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.
Before you install
send_message and remove_channel require confirmation, but sending messages is an outward-facing action. Static secrets may be written in plaintext to channels.json, and OAuth tokens to tokens.json, protected only by same-user file permissions; on shared hosts or CI, set the OUTBOX_ _ environment variables and leave channels.json secret fields empty. remove_channel deletes stored credentials.

Installation

In SourceWeft

  1. Open Outbox in the dashboard and add it to a workspace.
  2. 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

[NuGet] [License: MIT]

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_message abstracts 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.json with current-user-only file permissions; MCP tool flows can resolve secrets at runtime via env vars or elicitation.
  • Single install — dotnet tool install -g gives 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)

bash
dotnet tool install -g FieldCure.Mcp.Outbox

After installation, the fieldcure-mcp-outbox command is available globally.

From source

bash
git clone https://github.com/fieldcure/fieldcure-mcp-outbox.gitcd fieldcure-mcp-outboxdotnet build

Requirements

Configuration

Claude Desktop

Add to claude_desktop_config.json:

json
{  "mcpServers": {    "outbox": {      "command": "fieldcure-mcp-outbox"    }  }}

VS Code (Copilot)

Add to .vscode/mcp.json:

json
{  "servers": {    "outbox": {      "command": "fieldcure-mcp-outbox"    }  }}

From source (without dotnet tool)

json
{  "mcpServers": {    "outbox": {      "command": "dotnet",      "args": [        "run",        "--project", "C:\\path\\to\\fieldcure-mcp-outbox\\src\\FieldCure.Mcp.Outbox"      ]    }  }}

Tools

ToolDescriptionConfirmation
list_channelsList all configured messaging channels—
add_channelAdd a new channel (MCP elicitation for all channel types; Microsoft/KakaoTalk require a local browser on the MCP host)—
send_messageSend a message through a configured channelRequired
remove_channelRemove a channel and its stored credentialsRequired

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.

ChannelProtocolSetup
SlackWeb API (chat.postMessage)Guide
TelegramClient API (WTelegramClient)Guide
GmailSMTPGuide
NaverSMTPGuide
MicrosoftGraph API (/me/sendMail)Guide
KakaoTalkKakao REST APIGuide
DiscordWebhook APIGuide
Custom SMTPUser-definedGuide

Static Secret Environment Variables

When a channel requires a static secret at send time, Outbox looks for an environment variable named:

text
OUTBOX_<CHANNEL_ID>_<FIELD>

Examples:

  • OUTBOX_MICROSOFT_1_CLIENT_SECRET
  • OUTBOX_KAKAOTALK_1_API_KEY
  • OUTBOX_KAKAOTALK_1_CLIENT_SECRET
  • OUTBOX_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

bash
fieldcure-mcp-outbox                      # Start MCP server (stdio)fieldcure-mcp-outbox add slack            # Add Slack channelfieldcure-mcp-outbox add telegram         # Add Telegram channelfieldcure-mcp-outbox add gmail            # Add Gmail SMTP channelfieldcure-mcp-outbox add naver            # Add Naver SMTP channelfieldcure-mcp-outbox add smtp             # Add custom SMTP channelfieldcure-mcp-outbox add microsoft        # Add Microsoft (Outlook/M365) channelfieldcure-mcp-outbox add kakaotalk        # Add KakaoTalk channelfieldcure-mcp-outbox add discord          # Add Discord channelfieldcure-mcp-outbox list                 # List configured channelsfieldcure-mcp-outbox remove <id>          # Remove a channel

Data Storage

DataLocation
Channel metadata%LOCALAPPDATA%\FieldCure\Mcp.Outbox\channels.json
OAuth tokens%LOCALAPPDATA%\FieldCure\Mcp.Outbox\tokens.json
Telegram sessions%LOCALAPPDATA%\FieldCure\Mcp.Outbox\sessions\

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

src/FieldCure.Mcp.Outbox/├── Program.cs                  # Entry point: MCP server vs CLI branching├── Channels/│   ├── IChannel.cs             # Channel interface + SendRequest/SendResult│   ├── ChannelFactory.cs       # Channel instantiation by type│   ├── SlackChannel.cs         # Slack Web API│   ├── TelegramChannel.cs      # WTelegramClient│   ├── SmtpChannel.cs          # MailKit SMTP│   ├── MicrosoftChannel.cs     # Microsoft Graph API│   ├── KakaoTalkChannel.cs     # Kakao REST API│   └── DiscordChannel.cs       # Discord Webhook API├── Tools/│   ├── ListChannelsTool.cs     # list_channels│   ├── AddChannelTool.cs       # add_channel (elicitation + browser OAuth for Kakao/Microsoft)│   ├── RemoveChannelTool.cs    # remove_channel│   └── SendMessageTool.cs      # send_message├── Interaction/│   ├── IElicitGate.cs          # Minimal MCP elicitation surface for tests│   └── McpServerElicitGate.cs  # Production adapter around McpServer├── OAuth/│   └── BrowserOAuthFlow.cs     # Localhost callback + Process.Start + elicit race (MCP and CLI entry points)├── Credentials/│   └── OutboxSecretResolver.cs # cache → env → channels.json → elicitation├── Setup/│   ├── SetupRunner.cs          # CLI router (diagnostic path)│   ├── ConsoleHelper.cs        # Masked input, prompts│   ├── SlackSetup.cs│   ├── TelegramSetup.cs│   ├── SmtpSetup.cs│   ├── MicrosoftSetup.cs│   ├── KakaoTalkSetup.cs│   └── DiscordSetup.cs└── Configuration/    ├── ChannelStore.cs         # channels.json persistence (metadata + static-secret fallback)    ├── OAuthTokenStore.cs      # tokens.json persistence (OAuth access/refresh, user-only file perms)    └── SmtpPresets.cs          # SMTP preset definitions

Development

bash
# Builddotnet build
# Testdotnet test
# Pack as dotnet tooldotnet pack src/FieldCure.Mcp.Outbox -c Release

See Also

Part of the AssistStudio ecosystem.

License

MIT

Source: README.md at commit 595d983

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  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