Outbox

io.github.fieldcure由 GitHub 账号 fieldcure 发布v2.1.3更新于 Oct 24, 2026

Multi-channel messaging MCP server for Slack, Telegram, Email, KakaoTalk, and Discord.

已验证STDIO仅桌面效率与工作流沟通与协作

概览

AI 生成的概览

让助手通过一套工具向 Slack、Telegram、电子邮件、KakaoTalk 和 Discord 发送消息。

可以做什么
Outbox 是一个本地 MCP 服务器,用四个工具统一多个消息渠道:list_channels、add_channel、send_message 和 remove_channel。send_message 屏蔽了 Slack Web API、Telegram 客户端 API、SMTP(Gmail、Naver、自定义)、Microsoft Graph、KakaoTalk REST 和 Discord webhook 之间的差异。渠道可通过 CLI 配合浏览器 OAuth 流程配置,OAuth 令牌可跨运行刷新。
适用场景
当助手需要跨多个平台向人发送通知或消息,又不想为每个渠道单独安装 MCP 服务器时使用。尤其适合需要 KakaoTalk 的韩国用户,或希望把 Slack、邮件和 Discord 发送合并到一个工具的场景。
运行要求
以 .NET 工具(FieldCure.Mcp.Outbox)通过 stdio 在本地运行;需要 Windows、Linux 或 macOS 上的 .NET 8.0 Runtime 或更高版本。各渠道凭据通过名为 OUTBOX_ _ 的环境变量提供,或通过 MCP 交互式征询获取。Microsoft 和 KakaoTalk 配置需要本地浏览器完成 OAuth。
安装前请注意
send_message 和 remove_channel 需要确认,但发送消息属于对外操作。静态密钥可能以明文写入 channels.json,OAuth 令牌写入 tokens.json,仅靠同一用户文件权限保护;在共享主机或 CI 上应显式设置 OUTBOX_ _ 环境变量,并让 channels.json 的密钥字段留空。remove_channel 会删除已存储的凭据。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Outbox,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

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

来源:README.md,提交 595d983

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v2.1.3最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分