SingChat

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as org.singchat/singchat and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 29 Sept 2026. Not supplied by the maker.

• ping

  Health check for the SingChat MCP server. Returns 'pong' and whether this request is authenticated to a workspace.

• singchat_setup

  Get the user up and running with SingChat live-chat. Call this FIRST. If no authenticated workspace is configured, this creates a brand-new free workspace and returns a short-lived, single-use browser

• get_embed_snippet

  Return the SingChat chat-widget embed code for this workspace's web inbox, in three flavors: plain HTML, React (useEffect), and Next.js (next/script). Requires a workspace API key. Optionally pass `pl

• claim_account

  Return the link to claim (permanently secure) this SingChat workspace by setting an email and password. Use this for workspaces that were auto-created via MCP so the user does not lose access. The lin

• list_conversations

  List the workspace's support conversations (agent/inbox view), newest activity first. Optionally filter by status or a free-text search over the contact name/email and last message. Returns a compact

• get_conversation

  Fetch a single conversation with its contact details and the most recent messages (oldest→newest).

• reply_to_conversation

  Send an agent reply through a supported SingChat real-time inbox. This takes the conversation over from the AI and broadcasts the message to the visitor and agent inbox. Email, Telegram, and WhatsApp

• resolve_conversation

  Mark a conversation as RESOLVED (closes it). The visitor's widget will no longer show it as active.