Listen Labs

Browse AI-moderated interview studies, read transcripts, pull analysis.

Add to Agentman Studio

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

Resources

What the Listen Labs connector does

The Listen Labs MCP server connects Listen Labs — a platform that runs AI-moderated user interviews with recruited participants — to Claude, ChatGPT and any MCP-compatible agent. It covers browsing studies, reading respondent transcripts and pulling AI analysis. Listen Labs also documents tools that create, edit and launch studies, which recruits real people and spends credits. Sign-in is OAuth.

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.

Listen Labs tools (11)

  • list_studies
  • get_study_responses
  • get_response
  • get_study_analysis
  • search_across_studies

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • No OAuth scopes exist at all. The server's own RFC 9728 descriptor at https://mcp.listenlabs.ai/.well-known/oauth-protected-resource/mcp and its authorization server metadata both declared scopes_supported as [] on 2026-08-22. The boundary that matters here — between reading a transcript and spending credits to recruit strangers — does not exist at the grant. It exists only in your Listen Labs role, which the consent screen does not let you narrow for this session.
  • Anthropic's directory understates the surface. It lists 5 tools and records permissions as Read. Listen Labs names 11 and documents write, launch and delete capabilities. Do not size the risk from the listing.
  • The real tool count is above 11. Folder create, rename, move and delete are documented capabilities with no published tool name, so we cannot enumerate them and neither can you.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail or readOnlyHint is published here. Every read/write label on this page is our classification of names and documented behaviour.
  • Launching costs money and cannot be undone by unlaunching. Listen Labs states a launched study begins collecting responses immediately, that started responses are allowed to finish even past a response limit, and that participant incentives are the customer's responsibility, billed separately from platform credits. You can pause or close a study, but interviews already completed are already paid for.
  • Analysis needs a completed run. get_study_analysis returns nothing useful until one exists; check has_analysis on list_studies first.
  • Edits to a live study are invisible until published. Listen Labs states edits stay in draft, and that deleting questions that already have responses removes those answers from analysis.
  • Credits cannot be topped up over MCP. Listen Labs' research skill states a short balance has to be resolved in the Listen dashboard.
  • Transcript content is untrusted input. It is written by recruited members of the public. Pairing broad transcript reads with edit_study or launch_study in one session is the combination to avoid.
  • No vendor-published rate limits. We found none documented for the MCP server.

Frequently asked questions

Can the Listen Labs connector launch a study and recruit real people?

Yes. Listen Labs documents a launch_study tool that publishes a study and starts recruitment, and its own research skill marks that call as spending credits. Recruitment draws on a panel Listen Labs describes as 30 million-plus verified respondents in 45-plus countries, so a launch dispatches AI-moderated interviews to real human participants.

Why does Anthropic's directory list only 5 Listen Labs tools?

The directory entry predates the write tools, or omits them. Anthropic lists five read tools and marks the connector permissions as Read. Listen Labs' own research skill names eleven tools at commit cbff3cf, and its MCP documentation describes creating, editing, launching and deleting. Treat five as a stale floor, not the surface.

What OAuth permissions does the Listen Labs MCP server request?

None that narrow anything. The server's RFC 9728 resource descriptor and its authorization server metadata both declared scopes_supported as an empty array on 2026-08-22. There is no scope separating reading a transcript from launching recruitment, so consent is all-or-nothing within whatever your Listen Labs user account can already reach.

What personal data can the Listen Labs connector read?

Interview transcripts of real research participants, and the media behind them. Listen Labs documents transcripts as the complete text of each interview, and its response API returns signed audio URLs valid for one hour plus HLS and MP4 video URLs. Screen-share studies also capture recorded application windows or full screens.

Does the connector let an agent delete anything in Listen Labs?

Yes, folders. Listen Labs' MCP permissions state the integration can create, rename, move or delete folders, and its troubleshooting page confirms only empty folders can be deleted. No documented tool deletes a study or a response. Listen Labs publishes no tool name for any folder operation, so the delete path is unnamed.

What stops an agent from launching a Listen Labs study by accident?

Your account role and a client-side gate, not the connector. Listen Labs defines a Collaborator role that can build studies but cannot launch them, and only Researchers and Admins can start recruitment. Listen Labs' own research skill separately instructs the agent to never launch on its own initiative and to require explicit confirmation.

Why does the Listen Labs analysis tool return nothing useful?

The study has no completed analysis run yet. Listen Labs states that get_study_analysis requires a finished analysis, and that new or in-progress studies may not have one. Check list_studies for has_analysis set to true before asking for a report. Reports update continuously as new responses arrive.

Why does my MCP client say Method not allowed on Listen Labs?

The client is using the wrong transport. Listen Labs states the server is stateless and accepts only POST on the /mcp path, and that clients must use Streamable HTTP rather than SSE session polling on GET. Confirmed live on 2026-08-22: a GET to the endpoint returns 401 rather than a session stream.

Sources

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Listen Labs to work.

Connect Listen Labs once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio