6sense
Ask an AI agent about 6sense account insights, buying signals and keyword trends.
Design AI interview agents, invite participants, and analyse the transcripts.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Perspective AI MCP server connects a Perspective workspace to Claude, ChatGPT and any MCP client. It exposes 32 tools for designing AI interview agents, inviting participants, reading the resulting transcripts and wiring the results into Slack, HubSpot or Gmail. Sign-in is OAuth, or a workspace-scoped key you create yourself. One tool emails real people; one deletes.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
/mcp.A perspective is one conversation agent plus everything it produces. You describe what you want to learn, Perspective generates an outline of goals and questions, picks an agent type, and then runs a one-on-one adaptive conversation with each participant. The transcripts, stats and insights all belong to that perspective, which is why almost every tool name starts with it.
No, but you can use one. Perspective documents OAuth as the recommended path: you add the URL to your client, sign in once in a browser, and the client manages the connection with no token in a config file. For clients that cannot do OAuth, Perspective lets you create a workspace-scoped MCP key and send its token as a bearer header instead.
Yes. The participant_invite tool creates 48-hour magic links, reissues invite links and can optionally send invitation emails, according to Perspective's MCP documentation. That means a connected assistant can contact real people on your behalf. Treat it as the one tool on this server with an audience outside your workspace and confirm every call before it runs.
One tool deletes: automation_delete removes an automation. Perspective's documentation groups it with automation_create, automation_update and automation_test as the tools that manage per-interview and scheduled automations. No tool on the directory listing deletes a perspective, a conversation or a participant record, so the destructive surface is limited to automation wiring.
Only the workspaces the credential covers. Perspective states that each MCP key is scoped to the workspaces you select, and that an assistant using it reaches only those workspaces and only while you remain a member. Its documented advice is one key per assistant, scoped narrowly, so a leaked key has a limited blast radius.
The key is not scoped to that workspace, or you have since left it. Perspective's troubleshooting notes say keys reach only the workspaces they were granted, and that this holds even for admins. The fix is to create or recreate a key that includes the workspace you are targeting, then reconnect the assistant.
Indirectly. The MCP server itself has no separate price, but the work it triggers consumes Perspective credits. Perspective's pricing page prices a conversation at 10 credits, a research project at 1 credit and an analysis session at 1 credit, with 100 credits included free and a Pro subscription from $99 per month for 1,000 credits monthly.
https://getperspective.ai/mcp — HTTP 401 with a WWW-Authenticate Bearer challenge naming its resource metadata document, 2026-09-08. No tool list was read; the server is gated and we did not authenticate. · retrieved 2026-09-08mcp and offline_access scopes, and the authorization server metadata at (HTTP 200, 2026-09-08). · retrieved 2026-09-08getperspective.ai/robots.txt permits all agents on /docs/ and carries Content-Signal: ai-train=no, search=yes, ai-input=yes (checked 2026-09-08) — the publisher has expressly permitted AI synthesis of this content. · retrieved 2026-09-08Connect Perspective AI once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.