Unwrap.ai

Not quite. Unwrap's documentation states all its tools are currently read-only, and every OAuth scope the server advertises ends in read. But the same doc table describes sample_feedback_entries as creating a named sample and classify_feedback_entries as creating sub-samples for each label. Those persist server-side, so the label understates what the connector does.

A named, saved sample of feedback entries drawn from a view. Unwrap documents two modes, a representative random sample and a targeted semantic sample. The sample persists because two other tools depend on it: analyze_entry_text runs an instruction across a saved sample, and classify_feedback_entries splits one into labelled sub-samples. Nothing leaves your workspace.

No. Unwrap documents leave_feedback as sending feedback on the MCP directly to the Unwrap team. It writes outbound to the vendor, not into your feedback dataset, your views or your samples. It is the one tool on the list whose output an agent cannot read back, and the one whose destination is Unwrap rather than your own account.

A view is the access boundary. Unwrap documents list_views as returning the views the authenticated org has permission for, and every data tool takes a view_id. Your agent picks one view, then queries within it. Static org-wide OAuth credentials are the exception: Unwrap says those grant read access to all views in the org.

Five, and all five end in read. Its RFC 9728 descriptor advertises team teams read, groups read, charts read, filters read and entries read, retrieved live on 2026-08-18. No scope covers creating a sample, so the consent screen cannot express the difference between reading your feedback and saving a named subset of it.

Yes, through static OAuth credentials. Unwrap documents an admin-only flow that issues a client ID and secret from the Organizations page, giving every user of those credentials read access to all views in the org. That bypasses per-user view permissions, so an individual OAuth sign-in is the tighter option for most teams.

Ask for Unwrap by name in the prompt. Unwrap's docs suggest phrasing requests explicitly, such as asking Unwrap for your top issues, when a client does not pick the tools up on its own. Unwrap also recommends loading its guide prompt first, and marking read-only tools as always-allow so the client stops pausing for approval.