Claude Unwrap connectorWhat Claude can do in your Unwrap account.
The Claude Unwrap connector exposes 17 tools. 12 read your customer feedback and Unwrap's help docs, 3 produce or send something, and 2 are documented nowhere. Here is what Claude analyzes, what it produces, and where Unwrap's docs contradict themselves.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when you listen to customers
Unwrap organizes your customer feedback into views, segments and theme groups. With the connector you ask Claude your question: it picks the Unwrap view to query, looks for the topics that matter, filters by segment and can come back with statistics and a chart.
Spot the priority issues. search_actionable_groups returns the most actionable groups for a question, with filters and sorting on a numeric segment. Unwrap pitches it for top issues and prioritization.
Follow a trend. plot_chart draws charts or tables over time or by breakdown, to see how something evolves, how items rank or how shares compare.
Measure what customers actually say. Claude builds a sample of feedback with sample_feedback_entries, then analyze_entry_text runs one question across every entry and returns how often an answer comes up, with examples.
What Claude does not do: edit your source feedback or your taxonomy, since no documented tool handles that. Nothing runs on its own either, so no alert when a new theme climbs. Continuous monitoring is a job for an automation tool, a different trade; Integrations gathers that side, tool by tool, for when you need something running on a schedule.
The vocabulary in one minute
Five words to read the rest without detours.
- Connector
- The link you set up once between Claude and an account you already have, so it can work there while it answers you.
- Tool
- A named action the connector opens to Claude. Claude picks the ones it needs on its own; the directory sheet lists them.
- Authorization
- Unwrap's own sign-in screen, where you hand Claude the access it will use. You can take it back the same way.
- Approval
- The confirmation Claude waits for before an action that changes an account, shown in the chat right when it matters.
- MCP
- The shared standard behind connectors: it is what lets an assistant like Claude talk to an outside service.
Connect the Claude Unwrap connector
- 01
Find Unwrap
In Claude's settings, open Customize, then Connectors, and look for Unwrap. On a Team or Enterprise workspace, an Owner or Primary Owner has to add it first so each member can connect.
- 02
Start the connection
Click Connect on its row, then sign in through the window Unwrap opens itself. If the connection drops, use Disconnect and reconnect, which is also what Unwrap recommends.
- 03
Read the authorization screen
Read the authorization screen before you approve. It belongs to Unwrap, not to Claude, and it decides what the access covers. Whatever you grant there can be withdrawn later.
The 17 tools, grouped by what they do
Unwrap gives Claude 17 tools: 12 that read your account, 3 that change something in it, and 2 no official source describes.
Twelve reading tools, three that produce or send something, two without a description. Tool names stay exactly as Claude shows them.
- 12 read
- 3 write
- 2 not documented
Tools index
What Claude reads (12)
12 toolslist_views
Lists the Unwrap views your organization has, with their ID and name. It is the first thing Claude calls, since it has to know which view to work on.
get_started
Hands Claude Unwrap's usage guide: the data model and the recommended workflows. Unwrap asks for it to be called first, before any search.
list_feedback_integrations
Shows which feedback sources feed a given view and how well each is covered, so you know where the analyzed opinions come from.
search_segments
Searches segment fields and their values by meaning for the ones tied to a question.
list_segment_field_values
Lists the exact values allowed for a segment field, so filters match the spelling Unwrap expects down to the character.
discover_filter_schema
Returns every filter field available for a view, so the valid options are known up front instead of discovered by trial and error.
search_groups
Looks through Unwrap's taxonomy of groups by meaning to find the issues or themes tied to a query, with optional filtering on top.
search_actionable_groups
Returns the most actionable groups for a question, with filters and sorting on a numeric segment. Unwrap aims it at top-issue lists and prioritization.
plot_chart
Produces charts or tables over time or by breakdown, to follow a trend, compare shares between groups or build a ranking.
analyze_entry_text
Puts one instruction or question to every entry in a saved sample and returns prevalence statistics along with example results.
search_documentation
Queries Unwrap's public help center and returns a ranked list of matching article titles, each with its URL.
read_documentation_article
Reads one or more articles from Unwrap's documentation and returns them as Markdown, handy for setup or how-to questions.
What Claude creates or sends (3)
3 toolsThree tools that create a sample or send feedback. No source spells out their confirmation, so the general rule applies.
sample_feedback_entries
Approval: see the ruleCreates a named sample of feedback entries, either random to stay representative or targeted by meaning. Later analyses run on it.
classify_feedback_entries
Approval: see the ruleSorts the entries of a saved sample into labels defined in advance and creates one sub-sample per label.
leave_feedback
Approval: see the ruleSends feedback straight to the Unwrap team about the connector itself, not about your customer data.
Not documented (2)
2 toolsThe directory publishes these two names and says nothing about their role. This page won't guess from the names.
query_feedback_data
The directory sheet publishes this name, and no official source describes it under that name. Unwrap's article mentions a tool with a similar name, without anything confirming it is the same one.
get_group_insights_playbook
This name only appears on the directory sheet: neither Unwrap's article nor any Claude page describes it, and this page will not guess anything at all from the label.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before every action it takes on an account for you. The request shows up in the chat when it applies.
Unwrap recommends a setup of its own: leave its reading tools on permanent allow and keep its write tools under approval. On a Team or Enterprise workspace, owners decide whether a member may let some actions through without a new prompt, and they can cap what the connector does for the whole organization. Claude only sees the views your permissions open to you, never the rest of the account, whoever set the connector up.
Which plans it is available on
None of the 819 sheets in the official directory shows plan availability. That answer, connector by connector, is not published anywhere.
The general rule is published: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner switches the connector on for the organization before members connect. The current state is on the connector's sheet in the official directory.
Where this connector stops
A connector is not an automation: Claude calls these tools while it answers you, and nothing fires on its own. Only Unwrap documents this connector, in its knowledge base.
Unwrap's documentation does not quite match the sheet: two tool names differ or are missing, and the article contradicts itself about being read-only, as the box below explains. The directory badge is not a security audit, and Anthropic says so on every sheet: it does not choose a publisher's tools and does not guarantee how they behave. For monitoring that runs without you on a schedule, see the automation side under Integrations.
Are all of Unwrap's tools read-only?
- Unwrap MCP article, header of the tool table ↗September 2026Unwrap states that all of its tools are currently read-only.
- Unwrap MCP article, descriptions in the same table ↗September 2026The same table describes one tool that creates a named sample, another that creates sub-samples and a third that sends feedback to the Unwrap team.
What this page followsUnwrap's page contradicts itself on the same date. This page follows the tool-by-tool descriptions: those three tools sit on the write side, and Unwrap advises keeping its write tools under approval anyway.
Need help connecting Unwrap to Claude?
A person reads every message.