Unthread

Unthread documents a create_conversation_comment tool on the MCP server, and the REST endpoint it matches posts to the customer by default. That endpoint takes an optional isPrivateNote boolean, and Unthread states a private note posts to the Slack thread without sending a response back to the customer. Omitting the flag sends the message onward.

Fourteen names across two lists that do not overlap. Anthropic's directory lists six read tools; Unthread's own documentation names eight different ones, including five survey readers and three writes. Neither list contains a name from the other. We could not run a live handshake because the endpoint requires OAuth, so no single verified total exists.

No. Anthropic's directory records the permission as Read Only and lists six read tools, but Unthread's documentation has a section headed what data is available to write naming update_conversation, create_conversation_comment and create_approval_request. The directory listing and the vendor's documentation disagree, and the vendor is describing the server it operates.

One scope named mcp. Unthread's RFC 9728 resource descriptor and its authorization server metadata both advertise scopes_supported as the single value mcp, checked on 2026-08-22. That is one switch for the whole server, so nothing at the OAuth grant separates reading a conversation from commenting on one. Your Unthread role is the only real boundary.

No. Every tool name Unthread and Anthropic publish is a fixed operation against a named object, such as list_conversations or get_survey_analytics. None takes an endpoint, service or method string that would forward to the wider REST API. The tool count therefore means what it says, unlike connectors that wrap a whole API behind one dispatcher.

An Unthread account and the server URL. Unthread's setup steps are to open Settings, then Connectors, then Add custom connector, enter a name and the URL https://app.unthread.io/api/mcp, then sign in through the OAuth prompt. Unthread states the assistant can only access data you have permission to view, so your workspace role carries over.

No, they are separate servers with separate URLs. The connector in Anthropic's directory is the admin server at app.unthread.io/api/mcp, used by your support team. The portal server runs at your own portal domain followed by /api/mcp and is for your customers, who can use it to read the knowledge base and file tickets.

No published tool deletes anything. Neither Anthropic's six names nor Unthread's eight carries a delete, remove, merge or archive verb, even though Unthread's REST API documents DELETE as one of its four methods. Closing a conversation is different: it is a status change, which update_conversation most likely reaches, and it is reversible.

Because ticket text is written by your customers. Anyone who can open a conversation can put text in front of your agent, which makes retrieved conversation content untrusted input. Pair that with a documented comment tool whose customer-visible setting is the default, and a well-crafted ticket becomes a route to a message going back out.