mcptest.io

Remote MCP Inspector

Communication MCP servers

18 remote MCP servers in Communication: Slack, Intercom, Resend and 15 more. They most often cover email, customer support and messaging. 1 needs no credentials; 15 use OAuth 2.1, 1 takes a bearer token and 1 takes an API key. The catalog validator observed public inventories for 2 of 18: 182 tools, most often to get, create or delete.

Authentication
No authentication 1OAuth 2.1 15Bearer token 1API key 1
Transport
Streamable HTTP 18
Browser ready
0 of 18
Tool inventories
2 of 18 · 182 tools observed

Showing 18 of 18 Communication servers

Guides for Communication servers

  • OAuth for MCP explained

    Follow the MCP authorization sequence from a 401 challenge through resource and issuer discovery, PKCE and client registration, token exchange, and retry.

  • How to add a remote MCP server to Claude

    Step-by-step setup for remote MCP servers in claude.ai custom connectors, Claude Desktop and Claude Code, with the plan differences and the real failure modes for each.

  • Is MCP safe?

    What a connected MCP server can see and do, how tool poisoning and prompt injection work, what OAuth consent and tool approvals protect, and how to vet a server before you connect it.