Skip to main content
hc
Submit
4 compared

Messaging MCP servers compared

Messaging-platform MCP servers that let Claude read and post messages, compared on trust, setup, and safety.

Open in the interactive comparison tool
FieldSlack MCP Server for Claude

Official Slack remote MCP server that connects Claude and other MCP clients to Slack search, messages, channels, threads, canvases, reactions, users, and workspace context through OAuth-backed Streamable HTTP.

Open dossier 		Discord MCP Server for Claude

Discord bot integration for community management, moderation, and server automation

Open dossier 		Telegram MCP Server

Telethon-powered MCP server for connecting Claude to Telegram accounts, chats, messages, contacts, media, folders, groups, channels, profile settings, and read-only or full account workflows.

Open dossier 		WhatsApp MCP Server

Personal WhatsApp MCP server with a Go bridge and Python MCP server for searching contacts and chats, reading messages, sending messages, sending media, and downloading WhatsApp media.

Open dossier
Trust
Install riskReview firstLow riskReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Categorymcpmcpmcpmcp
Sourcesource-backedfirst-partysource-backedsource-backed
AuthorSlacksaseqchigwellLuke Harries
Added2026-06-042025-09-202026-06-062026-06-05
Platforms
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Claude CodeClaude Desktop
Source repo————
Safety notes✓Slack's official MCP server is a remote server at `https://mcp.slack.com/mcp` using Streamable HTTP. It is not an npm package or HeyClaude-hosted artifact. Slack documents that MCP clients must be backed by an approved Slack app identity, and only directory-published apps or internal apps may use MCP. Unlisted apps are not allowed for this flow. Workspace admins can approve and manage MCP client integrations. Do not bypass workspace approval, legal, security, or data-governance rules for AI access to Slack. The server can perform write actions when scopes allow it, including sending messages, drafting messages, creating channels or conversations, adding reactions, and creating or updating canvases. Read tools can expose public channels, private channels, DMs, multi-party DMs, files, canvases, user profiles, custom profile fields, user status, channel metadata, message history, and thread history depending on scopes. Do not connect Slack MCP alongside broad file, browser, shell, database, or ticketing MCP servers unless cross-tool data movement has been reviewed. Slack MCP tools are subject to Slack Web API rate limits by tool/action type. Avoid unbounded searches, channel-history sweeps, message-posting loops, and repeated canvas updates. Require human review before posting to real channels, messaging users, creating conversations, adding reactions in sensitive threads, or editing shared canvases.✓Use least-privilege bot permissions and test moderation or message-writing actions in a non-critical server first.✓Telegram MCP Server can read chats and messages, send, schedule, edit, delete, forward, and pin messages, mark chats read, create polls, press inline buttons, manage contacts, manage groups and channels, upload or download media, and update profile settings when write tools are exposed. A Telegram session string has the normal authority of the Telegram account inside the server process; read-only mode limits the MCP tool surface but does not reduce the underlying session authority. The upstream README warns that the PyPI `telegram-mcp` name is owned by a different project, so do not pass Telegram API credentials or session strings to that package. File-path tools are disabled until allowed roots are configured; keep upload and download roots narrow when enabling media or file operations. Require human approval before sending, editing, deleting, forwarding, pinning, reacting, inviting, banning, changing permissions, or updating profile and privacy settings. Use separate Telegram accounts for testing, monitor Telegram rate limits and platform rules, and keep proxies or multi-account routing explicit.✓WhatsApp MCP can search and read personal messages, contacts, chats, media metadata, and message context. Tools can send messages and files to individuals or groups; require human approval before every send action. Prompt injection in messages or media metadata can attempt to exfiltrate private chat data through the agent. Use only with accounts you control and understand the risks of linking third-party automation to WhatsApp. Re-authentication may be required when WhatsApp linked-device sessions expire.
Privacy notes✓Tool results can expose Slack messages, files, channel names, private channel metadata, DMs, thread context, canvases, user profiles, email addresses, custom profile fields, user statuses, emoji, and workspace history. OAuth user tokens and client secrets are sensitive credentials. Keep them out of prompts, screenshots, shared MCP configs, logs, shell history, issue comments, and repository files. Search results and message history can contain customer data, credentials, incident details, HR/legal discussions, security reports, unreleased product plans, support escalations, and other confidential workspace content. AI transcripts, MCP client logs, debug output, local caches, and downstream tools may retain Slack content outside Slack's own retention controls. Use test workspaces, limited channels, synthetic data, or narrow OAuth scopes for demos, screenshots, development, and AI-assisted troubleshooting. Review Slack, Salesforce, MCP client, AI-provider, and connected-tool retention policies before giving an assistant access to real workspace history or private conversations.✓Discord messages, channel names, user IDs, member metadata, and server configuration may be sent through model context.✓Telegram API IDs, API hashes, session strings, account labels, chat titles, usernames, phone-adjacent identifiers, messages, media, contacts, group membership, profile photos, user status, read receipts, drafts, and folder metadata can be exposed to the MCP client. Chat history and media can contain private conversations, personal data, business records, access links, invite links, documents, photos, voice notes, stickers, GIFs, and user-controlled prompt-injection text. The project includes output sanitization for user-controlled content, but sanitized Telegram content should still be treated as untrusted model input. Store session strings like passwords, keep them out of shell history and shared logs, and revoke sessions if they are exposed. Review MCP transcripts, downloaded media folders, Telegram session files, and proxy logs before sharing or retaining them.✓Personal and group messages, contacts, phone numbers, group identifiers, media metadata, downloaded media paths, attachments, and outgoing message drafts may be exposed to the MCP client and model. Message history is stored locally in SQLite databases under the bridge directory, and media can be downloaded locally on demand. Chat content may include other people's personal data, confidential business information, authentication codes, health data, financial data, or private media.
Prerequisites
  • Slack workspace with permission to connect MCP clients or request workspace-admin approval.
  • MCP-capable client that supports remote HTTP MCP and Slack's OAuth flow, such as Claude.ai, Claude Code, Cursor, Perplexity, or another compatible client.
  • Network access to `https://mcp.slack.com/mcp` using JSON-RPC 2.0 over Streamable HTTP.
  • Slack app identity or partner-client path that satisfies Slack's MCP app requirements.
  • Discord account with Developer Portal access (https://discord.com/developers/applications)
  • Discord bot application created in Discord Developer Portal
  • Discord bot token (obtained from Discord Developer Portal - Bot section)
  • Discord Guild ID (optional, for default server targeting - found in Discord server settings)
  • Python 3.10 or newer with `uv` available.
  • A trusted checkout of `https://github.com/chigwell/telegram-mcp`; do not use the unrelated PyPI package with the same distribution name.
  • Telegram API credentials from `my.telegram.org/apps`.
  • A Telegram session string or file-based session generated from the trusted checkout.
  • Go for the WhatsApp bridge.
  • Python and uv for the MCP server.
  • WhatsApp mobile app with permission to link a device via QR code.
  • FFmpeg if you want automatic conversion for playable WhatsApp voice messages.
Install
claude mcp add --transport http slack https://mcp.slack.com/mcp
npx -y @smithery/cli@latest install @SaseQ/discord-mcp --client claude && claude mcp list
uv --directory PATH_TO_TELEGRAM_MCP_CHECKOUT run main.py
git clone https://github.com/lharries/whatsapp-mcp.git && cd whatsapp-mcp/whatsapp-bridge && go run main.go
Config
{
  "mcpServers": {
    "slack": {
      "url": "https://mcp.slack.com/mcp",
      "type": "http"
    }
  }
}
Manual-only setup:
{
  "discord-mcp": {
    "env": {
      "DISCORD_TOKEN": "${DISCORD_TOKEN}",
      "DISCORD_GUILD_ID": "${DISCORD_GUILD_ID}"
    },
    "args": [
      "-jar",
      "/absolute/path/to/discord-mcp-0.0.1-SNAPSHOT.jar"
    ],
    "command": "java"
  }
}
Manual-only setup:
claude mcp add telegram-mcp --env TELEGRAM_API_ID=YOUR_TELEGRAM_API_ID --env TELEGRAM_API_HASH=YOUR_TELEGRAM_API_HASH --env TELEGRAM_SESSION_STRING=YOUR_TELEGRAM_SESSION_STRING --env TELEGRAM_EXPOSED_TOOLS=read-only -- uv --directory PATH_TO_TELEGRAM_MCP_CHECKOUT run main.py
{
  "mcpServers": {
    "whatsapp": {
      "command": "uv",
      "args": [
        "--directory",
        "PATH_TO_REPO/whatsapp-mcp-server",
        "run",
        "main.py"
      ]
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
More comparisons, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.