Claude Perspective AI connectorWhat Claude can do in your Perspective AI account.
The Claude Perspective AI connector exposes 35 tools: 17 read, 5 write, 13 undocumented. They design conversation agents, read results and insights, and invite participants. Here: what Claude can change, what it only reads, and what the publisher leaves unsaid.
Verified Trustpilot reviews · AI, automation & growth agency
What the Claude Perspective AI connector changes for your research
Perspective replaces static forms with AI-led conversations. With the connector, you ask Claude in plain words, and it can pick an agent template, draft the outline, check how a study is going and dig through the answers, all inside the chat. Perspective's own guide is the only source that lists what each family of tools does.
An interview agent drafted from a brief. agent_template_search finds a template that fits a company, team or use case, then perspective_create starts the draft and perspective_respond answers the design follow-ups Perspective raises.
The themes behind many interviews. Perspective points to conversations_search for what people say about a topic, conversations_data_analysis for counts and trends, and conversations_explorer for a close read of the transcripts.
Participants invited. participant_invite creates 48-hour magic links and can send the invite emails.
What the directory sheet does not say. Five tools change your workspace, and no source describes a confirmation specific to any of them. Thirteen more are only named by family, or not at all, so this page does not say whether they read or write: the automation tools, the Slack channel tools, the preview and embed tools, and two names with no description. Claude only acts while it answers you. For event-driven chains between apps, see the platforms on the Integrations hub.
Five words to know first
The Claude vocabulary you will meet around Perspective AI.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can use it while it writes its reply.
- Tool
- One named action a connector opens to Claude. Claude picks the ones a request needs; the directory sheet lists every one by name.
- Authorization
- The service's own sign-in screen, where you grant Claude the access it will use. Given once per person and revocable the same way.
- Approval
- The confirmation Claude waits for before it changes something in your account, shown in the conversation at that moment.
- MCP
- The shared standard behind connectors: it is what allows an assistant like Claude to reach an outside service through one common format.
Connect Perspective AI to Claude in three steps
- 01
Find it in your settings
In Claude, open Customize, then Connectors, and look for Perspective AI in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable it before members can each sign in.
- 02
Start the sign-in
Click Connect on its row, then sign in to Perspective in the browser window it opens. If the link breaks later, choose Disconnect and connect again from the same row.
- 03
Read the authorization screen
Read the authorization screen before accepting. It belongs to Perspective, not Claude, and it sets what the access covers. Once accepted, the connector is ready in your next conversation.
The 35 tools, grouped by what they do
Perspective AI gives Claude 35 tools: 17 that read your account, 5 that change something in it, and 13 no official source describes.
Seventeen consult your workspace, five change it, thirteen have no documented direction. Tool names stay as Claude displays them.
- 17 read
- 5 write
- 13 not documented
What Claude reads (17)
17 toolsLookups on workspaces, templates, results, insights, analyses, connected providers and running jobs.
agent_template_get
Pulls the full detail of one agent template from Perspective's library, along with a ready-made brief that Claude can hand to perspective_create when it starts a new agent.
agent_template_search
Searches Perspective's agent library for templates that fit a company, a team or a use case, so Claude starts from an existing base rather than a blank page.
conversations_data_analysis
Runs a quantitative pass across conversations: counts, breakdowns and trends. Perspective points to it when the question is about volumes rather than wording.
conversations_explorer
Explores the text of conversations in depth, for exact phrases, comparisons and close reads. Perspective reserves it for the moment you need the words themselves rather than a summary.
conversations_search
Searches across conversations for themes and sentiment, answering questions of the kind "what do people say about X?" with findings rather than raw rows. Perspective recommends it whenever the question is about themes.
integration_manage
Lists the providers connected to your workspace, opens their setup URLs and finds the Slack, HubSpot or Gmail tool slugs that automations use as delivery channels.
perspective_await_job
Lets Claude wait for the result of a design, an exploration or an import that Perspective is still running, instead of answering before the work is done.
perspective_get_conversation
Part of the Results family, which Perspective describes as inspecting stats, browsing responses and pulling summaries or transcripts. Here, Claude pulls one conversation so it can quote what a participant actually said.
perspective_get_conversations
Fetches summaries or transcripts for a set of conversations, within the same Results family, so Claude can read them side by side rather than one at a time.
perspective_get_stats
Returns the statistics of a perspective. Perspective also cites fetching stats as a simple first request to confirm the connection works before any heavier analysis, which makes it a natural starting point.
perspective_list_conversations
Browses the responses a perspective has collected, the browsing step of the Results family, so Claude can see what came in and choose which conversations to open next with the other result tools.
read_insight
Opens the full content of one analyst insight picked from the list, so Claude can quote it or answer the questions it raises. Perspective pairs it with the listing tool: insights listed first, then one read in full.
read_insights
Lists the analyst insights already available on a project, the first half of the pair Perspective describes. The publisher advises starting with status or existing insights before running a new analysis.
read_perspective_status
Gives a quick health check of a project in one call: progress, volume, credits and automations, according to Perspective's own description. The publisher suggests starting here, or with existing insights, before heavier analysis.
workspace_get
Inspects the details of one Perspective workspace, so Claude can make sure it is in the right place before touching a study.
workspace_get_default
Belongs to the Workspace family, described by Perspective as finding the right workspace and inspecting its details. This entry returns the workspace treated as your default.
workspace_list
Lists the workspaces your access reaches. Perspective recommends this kind of simple request to verify the connection before complex analysis, alongside fetching stats.
What Claude changes (5)
5 toolsFive tools that create or revise a draft, import an interview or invite participants. No source details their confirmation, so the general rule below applies.
participant_invite
Approval: see the ruleCreates 48-hour magic links, reissues invite links, can send invite emails and attaches context to each participant.
perspective_create
Approval: see the ruleCreates a new perspective draft, meaning the conversation agent and its outline, from your brief or from a template's brief.
perspective_import_conversation
Approval: see the ruleBrings an interview held outside Perspective into a perspective from its transcript, whether it was an in-person meeting or a Zoom, Gong, Meet or Teams call, so it is analyzed alongside native conversations.
perspective_respond
Approval: see the ruleAnswers the design follow-ups Perspective raises while it builds a draft, so the outline reflects your intent rather than defaults.
perspective_update
Approval: see the ruleRevises an existing outline, to adjust an agent already in place rather than recreating it.
Undocumented (13)
13 toolsPerspective describes eleven of these only as a family whose verbs mix reading and changing, and two not at all. This page does not infer, from a name, which one reads and which one writes.
automation_create
Listed by Perspective in its Automations family, which the guide sums up as managing per-interview and scheduled automations, then testing delivery. No source says which of the five tools does what, nor whether this one reads or changes anything.
automation_delete
Another member of the Automations family. Perspective's one line for the family covers managing automations and testing their delivery; nothing official describes this tool on its own, so its direction stays open here.
automation_list
Named in the same Automations row of Perspective's guide, a row that no source splits tool by tool and whose verbs mix looking and changing. Nothing isolates this tool, so the page cannot say whether it only reads.
automation_test
Grouped by Perspective with the other automation tools under a single description that ends with testing delivery. No source states, tool by tool, whether this particular call sends or changes anything.
automation_update
The fifth name in Perspective's Automations row. The guide gives the row one shared purpose and no description per tool, so the read or write direction of this one is undocumented.
perspective_get
This name appears in the directory's tool list, and that is all that has been published about it. Perspective's guide does not mention it and no Claude page does either, so this page stops there.
perspective_get_embed_options
Perspective files it under Deployment, a family described as generating preview links, share or direct URLs and embed snippets. No source says whether generating them creates anything on Perspective's side, so the direction is left open.
perspective_get_preview_link
The other Deployment entry. Perspective's single sentence for the pair speaks of generating links, URLs and snippets, without describing either tool separately or saying whether a link is created in the workspace.
perspective_list
Same silence here: the directory lists the name and no official source describes it. Saying so is more useful than a guess drawn from the wording of the name.
slack_channel_refresh
One of four Slack channel tools that Perspective describes together: finding and verifying channels to use as automation targets, and refreshing the channel directory from Slack. The guide does not split that sentence tool by tool.
slack_channel_refresh_status
Sits in the same Slack channels row as three other tools. Perspective's shared sentence mixes looking up channels with refreshing a directory, so whether this one reads or changes anything is not documented.
slack_channel_resolve
Named in Perspective's Slack channels family, which as a whole finds, verifies and refreshes channels used as automation targets. No source describes this entry on its own, and its read or write direction is not stated.
slack_channel_search
The first name of the Slack channels row in Perspective's guide. Because the row's single description covers both lookups and a refresh, and no source splits it, this page does not assign it a direction.
What Claude asks before acting
By default, Claude pauses and asks before any action it takes on an account on your behalf. The prompt shows up in the conversation when it counts.
On Team and Enterprise, workspace owners decide whether members can let some actions through without being asked every time. They can also cap what a connector may do for the whole organization, leaving analysis open and shutting writes, and no one lifts that from their own account. Claude works with the access of the person signed in, and nothing more. No source describes a confirmation step specific to any Perspective tool, so this default is the rule on record here.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. That answer, connector by connector, is published nowhere.
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 can sign in. You also need a Perspective AI workspace. For the current status, open the Perspective AI sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you; it does not wake up when an interview completes. Only automations configured inside Perspective act on their own.
The tool list is an observed floor, not a ceiling: an administrator can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic writes on every sheet that it does not choose a publisher's tools nor guarantee their behaviour. Only Perspective documents this connector, in its MCP guide; no Claude help article covers it. Other connectors are gathered on the Claude connectors hub.
Need help connecting Perspective AI to Claude?
A person reads every message.