Communication. Researched Jun 7, 2026

MCP servers for communication.

We researched 3 communication MCP servers. Every single one requires an API key or OAuth token. We could not independently test them. Below is what we found, honestly disclosed.

Why these are "untested"

Slack requires a bot token. Discord requires a bot token. Gmail requires an App Password. We do not have test accounts for these services. If you do, you can run our benchmark scripts yourself. They are open source.

Last researched: Jun 7, 2026

What we found

Untested
UntestedKey Required 🔑

Nexus MCP

santoshakil
Free
Pricing

Pure Rust MCP server (~4MB binary) with 48 tools across Telegram, Gmail, WhatsApp, Slack, and Discord. No MCP SDK dependencies.

Pros
  • +Single binary, no Node.js dependencies
  • +48 tools across 5 communication channels
  • +Pure Rust — fast and memory-safe
Cons
  • Requires bot tokens for Slack/Discord
  • Gmail requires App Password
  • Self-hosted binary — no npx install
Best for:Cross-platform messaging, email automation, notifications
Install config
// Requires bot tokens / App Passwords
{"mcpServers": {"nexus": {"command": "./nexus", "args": [], "env": {"SLACK_BOT_TOKEN": "xoxb-...", "GMAIL_APP_PASSWORD": "..."}}}}
Untested
UntestedKey Required 🔑

Neo MCP

heydryft
Free
Pricing

206+ tools across 16 integrations including Slack, Gmail, Discord, WhatsApp, LinkedIn, Twitter/X. Uses Chrome extension for browser session auth — no API keys needed for many services.

Pros
  • +206+ tools — most comprehensive communication MCP
  • +Chrome extension extracts auth from browser sessions
  • +No API keys for many services
Cons
  • Requires Chrome extension installation
  • JavaScript/TypeScript — heavier than Rust
  • Multi-profile setup can be complex
Best for:Social media automation, email, chat, calendar integration
Install config
// Install Chrome extension first
{"mcpServers": {"neo": {"command": "npx", "args": ["-y", "neo-mcp@latest"]}}}
UntestedOfficial
UntestedKey Required 🔑

Slack Official MCP

Slack
Free
Pricing

Official remote MCP server from Slack. OAuth-based connection without custom bot app. Search channels, read threads, post messages.

Pros
  • +Official first-party server
  • +OAuth — no bot token management
  • +Remote MCP — no local process
Cons
  • Requires Slack OAuth approval
  • Limited to workspace permissions
  • Remote-only — no offline use
Best for:Slack automation, support triage, team notifications
Install config
// Remote MCP via OAuth
{"mcpServers": {"slack": {"url": "https://mcp.slack.com"}}}
Help us test

Have API keys?

If you have Slack, Discord, or Gmail API access, you can run our benchmark scripts and submit results. The test suite is open source and takes ~2 minutes per server.

Run tests on GitHub
Related categories