Which communication and email MCP servers are cataloged?

7 communication and email MCP servers are cataloged, each with verified publisher, access, and spec-revision facts.

Which communication and email MCP servers support the current spec revision?

0 communication and email MCP servers have verified support for the current revision (2026-07-28). The rest are on earlier revisions or unverified.

Communication and Email MCP Servers

7 communication and email MCP servers are cataloged, 0 with verified current-spec support.

MCP servers that send or read messages: email platforms, chat and messaging services, notifications, and team communication tools.

AgentPhone - Spec Support Unverified
First-party AgentPhone server for its own telephony API, distributed as npm:agentphone-mcp and hosted by the vendor at https://mcp.agentphone.ai/mcp. Probed 2026-09-03: both server/discover at 2026-07-28 and a legacy initialize returned HTTP 401 {"error":"Missing Authorization header"}, which grounds the endpoint as live and bearer-gated but negotiates no revision, so spec support stays unknown. No documentation names a revision; the package depends on @modelcontextprotocol/sdk ^1.26.0. Identity drift worth noting: the registry name's trailing segment is "agentphone" while both the repository and the npm package are "agentphone-mcp", and the registry record pins 0.6.0 while npm ships 0.7.0.
email-mcp - Earlier Revision
Distributed as npm:@codefuturist/email-mcp. Resolved from the published package: @codefuturist/email-mcp 0.2.3 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
emailmd - Earlier Revision
Endpoint probe negotiated 2025-11-25; support for 2026-07-28 not confirmed.
Google Workspace MCP (aaronsb) - Spec Support Unverified
Distributed as npm:@aaronsb/google-workspace-mcp. Community: the publisher is the personal GitHub account aaronsb and the server fronts Google Workspace, which the publisher does not operate. Requires the user's own Google OAuth credentials. No MCP revision statement found (checked 2026-08-27).
mcp - Spec Support Unverified
Listed with a remote endpoint. Spec revision support not yet verified.
Microsoft 365 MCP Server - Earlier Revision
Distributed as npm:@softeria/ms-365-mcp-server. Resolved from the published package: @softeria/ms-365-mcp-server 0.145.1 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.
Telnyx MCP Server - Earlier Revision
Telnyx's MCP server (npm telnyx-mcp) fronts the Telnyx communications API, run locally via npx with Telnyx API credentials. It ships from the telnyx-node monorepo; the ranked registry row points at the SDK package (npm telnyx), not this server. No surface names a supported MCP revision. Resolved from the published package: telnyx-mcp 7.16.0 depends on @modelcontextprotocol/sdk@1.30.0, whose artifact implements 2025-11-25. This records what the artifact implements, not what a deployment negotiates.