WhatsApp MCP Server MCP Server Pricing 2026

The Slack MCP server (built by Ivan Korotovsky) connects AI assistants like Claude, Cursor, and Windsurf directly to Slack workspaces, enabling conversational access to your team communication channels without requiring workspace admin approval for a bot install. Its standout feature is a "no permission" stealth mode — it authenticates using your own personal Slack session tokens (xoxc/xoxd, or a stored browser session) rather than requiring a Slack App with OAuth scopes, so it works even in locked-down workspaces where you cannot create bots. It also supports full OAuth Bot Token auth and Enterprise/GovSlack deployments for teams that prefer a conventional app install. Tools exposed include reading channel and DM/group-DM history with smart pagination, searching messages across the workspace, posting messages and thread replies, listing channels and users, and adding reactions. Common use cases include automating standups by posting summaries directly to team channels, searching past Slack conversations to surface decisions or context, monitoring specific channels for keywords or alerts, and drafting replies to thread discussions — all from natural-language prompts. Supports both Stdio and SSE transports plus proxy configuration for corporate networks. Install with: `npx slack-mcp-server@latest --transport stdio`. A separate official-style integration exists from Zencoder (@zencoderai/slack-mcp-server) for teams that prefer standard Bot Token OAuth over session-token auth. Compatible with Claude Desktop, Cursor, VS Code, Windsurf, and Cline.

Twilio's official MCP server, built by the Twilio Alpha team and published as @twilio-alpha/mcp, exposes the entirety of Twilio's public API surface to AI assistants over the Model Context Protocol. Rather than hand-writing tool wrappers, the server auto-generates MCP tools directly from Twilio's OpenAPI specs, so it stays in sync with new Twilio products (Voice, Messaging/SMS, Verify, Lookup, Conversations, and more) as they ship. Because a full API surface can blow past an LLM's context window, the server supports --services and --tags flags to scope which Twilio products are loaded into a given session, keeping tool lists small and relevant. Authentication uses a Twilio Account SID paired with an API Key/Secret pair (created in the Twilio Console), passed as a single credential string at launch rather than long-lived account credentials. The monorepo also ships a companion openapi-mcp-server package that can turn any OpenAPI spec into an MCP server using the same generator, useful for teams building on top of Twilio's partner or vertical APIs. Twilio's security guidance explicitly recommends against running community MCP servers alongside the official one to reduce the risk of a compromised third-party tool touching production SMS, voice, or verification workflows tied to real phone numbers and customer data.

Send emails and manage email templates with SendGrid.

The Resend MCP Server is Resend's official Model Context Protocol integration, letting AI assistants send and receive transactional email, manage contacts, broadcasts, and domains directly from Claude, Cursor, or any MCP-compatible client. Resend offers two ways to connect: a fully hosted remote server at mcp.resend.com (Streamable HTTP, no local install, OAuth login on first connect) that works well for Claude web/desktop and Cursor, or the same open-source code run locally via `npx resend-mcp` (published to npm as `resend-mcp`) using stdio or HTTP transport for CI, headless agents, or self-hosted setups. Authentication is either OAuth (hosted mode, browser-based) or a Resend API key passed as a Bearer token — handy for servers where a browser login isn't possible. Setup is documented for Claude Code, Claude Desktop/web, Cursor, Windsurf, Codex, and GitHub Copilot in VS Code. Typical use: ask Claude to "send a welcome email to this new signup using our verified domain" or "list contacts added to the newsletter audience this week," and the MCP server routes the request through your existing Resend account — no custom SMTP or REST integration code required. With 546+ GitHub stars, it's one of the most widely adopted first-party MCP servers in the email/transactional-messaging category.

The Discord MCP Server (SaseQ/discord-mcp) is a Java-based Model Context Protocol integration built on JDA (Java Discord API) that turns a Discord bot into a set of tools AI assistants can call directly. It lets Claude, Cursor, and other MCP clients read and send channel messages, manage threads, create and moderate channels and categories, manage roles and permissions, look up server (guild) members, and pull message history — enabling AI-driven community moderation, automated announcements, and Discord-native workflows without hand-writing bot code. The recommended install is Docker: set DISCORD_TOKEN (from a bot registered in the Discord Developer Portal) and an optional DISCORD_GUILD_ID as environment variables, then run the saseq/discord-mcp:latest image with SPRING_PROFILES_ACTIVE=http, which exposes the MCP endpoint at http://localhost:8085/mcp for remote/HTTP-transport clients. A Docker Compose path and a stdio-transport mode are also documented for local, per-client setups like Claude Desktop. Because it wraps JDA (Spring Boot underneath), it handles Discord's gateway/rate-limit quirks for you rather than requiring a hand-rolled REST client. This is the most-starred dedicated Discord MCP implementation; other community servers like v-3/discordmcp and hanweg/mcp-discord cover similar ground with lighter Node/Python stacks if a non-JVM runtime is preferred.

A Telegram MCP server that connects Claude, Cursor, and other MCP-compatible clients directly to a Telegram user account via the Telethon library, exposing 80+ tools grouped into accounts, chats/groups, messages, contacts, media, profile/privacy, and folders/drafts. It supports multi-account setups (list accounts and route tool calls by label), full group and channel administration (create/join/leave, invites, bans, admin roles, slow mode, topics), rich messaging (send, schedule, edit, delete, forward, pin, reply, search, polls, reactions, inline button inspection and press), contact management (add/remove/block/import/export), and media handling (files, voice notes, stickers, GIFs, downloads/uploads). All tool results containing Telegram user-controlled content are sanitized before being returned as structured JSON, and a device-identity feature lets the session appear as a distinct, labeled client rather than a generic script. Authentication uses a Telegram API ID/hash from my.telegram.org plus a generated session string — no bot token required, since this operates as a full user account. A `TELEGRAM_EXPOSED_TOOLS=read-only` mode is available to restrict the MCP surface to read-only tools when write access is not needed. The project explicitly warns against installing the unrelated `telegram-mcp` package from PyPI, which is owned by a different, unaffiliated project — always install from source via `uv sync`.