Hosted MCP server/Communication

CommSync MCP server

Provider setup path

CommSync gives an agent one inbox for business SMS and email across phone lines and mailboxes. It supports searching, reading, contact and label management, thread triage, and sending SMS or email from allowed lines. OAuth 2.1 with PKCE and discovery is the primary authentication path; API keys that start with csk_ are the alternative for scripts and servers. The MCP route is POST /api/mcp on your CommSync API origin, and the provider does not publish a fixed server.commsync.ai host.

OAuth 2.1 (PKCE with discovery) or API key (Bearer csk_...) Server not checked yet Reviewed 2026-11-16
About

Where it fits

Business teams triaging SMS and email across multiple lines and mailboxes with OAuth 2.1 or an API key.

  • Search texts and emails across lines.
  • Manage contacts and labels for threads.
  • Send SMS or email from allowed lines.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Provider API origin

The provider documents POST /api/mcp on your CommSync API origin and does not publish server.commsync.ai. Set COMMSYNC_API to the origin shown in your CommSync account before running this command. OAuth 2.1 with PKCE is the primary path; API keys that start with csk_ are the alternative for scripts and servers.

claude mcp add --transport http commsync "$COMMSYNC_API/api/mcp" --header "Authorization: Bearer $COMMSYNC_API_KEY"

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • Your client does not support Streamable HTTP. Use a client that does, and confirm the provider's current endpoint and transport in its docs.
Safety

Before you connect

Remote means provider access
  • The provider can see the requests and data your agent sends through the server.
  • Review OAuth scopes and API-key permissions. Start read-only if the provider offers it.
  • Use project scope for repository-specific servers; use global scope for personal tools.
  • Remove the server and revoke its token when you stop using it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

CommSync documentationhttps://commsync.ai/docs/mcp