SurveyMonkey

SurveyMonkey

A major survey platform with OAuth APIs and webhooks for collectors, surveys, pages, questions, responses, contacts, and analysis workflows.

Research, forms & feedbackSystem of intelligenceExtensible SaaS
An illustration of access surfaces surrounding a governed system.
System roleSystem of intelligence
Access maturityExtensible SaaS
MCP supportOfficial MCP server
Reference updatedNot stated by publisher
BYO-UI reviewedJul 22, 2026

Concrete capability record

Data, retrieval, actions, identity, and operating limits

A field-by-field summary of what the reviewed first-party references actually support. Publisher update dates and BYO-UI review dates are shown separately below.

01 · Records and state owned

Surveys, pages, questions, question types, web-link collectors, response counts, full answers, statistical summaries, user information, survey properties, and AI-suggested survey plans.

02 · Data you can retrieve

Search surveys; inspect survey, page, question, and user details; read response metadata or full answers; produce statistical summaries and suggested survey plans.

03 · Actions and write paths

Create surveys, pages, questions, and shareable web links; edit questions or survey properties, reorder questions, and delete questions, except on live surveys.

04 · Authentication and permissions

The user connects SurveyMonkey through Claude and grants survey, collector, response, answer, and user-information access; effective tools depend on plan, seat, role, and survey sharing.

05 · Monitoring, approval, and recovery

Users must review granted permissions and proposed outputs or actions. Team and Enterprise Primary Admins can disable the connector, and live surveys cannot be edited through Claude.

06 · Limits and caveats

SurveyMonkey access requires US-stored account data. Plan, seat, or role can limit output; Basic accounts expose only 25 responses, and live surveys cannot be edited.

Agent access

MCP support

Official MCP serverSurveyMonkey hosted MCP / AI connectorCurrent documented service

Support: Official MCP server

Read scope: Find surveys and inspect pages or questions, retrieve response counts and full answer data, summarize results statistically, and generate an AI-suggested plan before creation.

Write scope: Build surveys and web-link collectors, add or delete questions and pages, edit question wording or survey properties, and reorder questions before the survey goes live.

Authentication: Interactive SurveyMonkey connection through Claude with a user-approved grant in connector settings covering accessible surveys, collectors, responses, answers, and user information; SurveyMonkey account permissions remain effective.

Approval boundary: Review the permission grant and each proposed mutation; require explicit confirmation before creating a shareable link, changing survey structure, deleting questions, or updating survey properties.

Protocol does not erase product boundaries.

Confirm the current tool catalog, plan, region, scopes, rate limits, terms, and write behavior before implementation.

Editorial assessment

Access-maturity dimensions

A comparative architecture lens—not a quality score, market ranking, or buying recommendation. Scale: 1–5.

Data access4
Action access4
Event access4
Identity4
Governance4
Agent access4
UI extensibility4
Portability3
Observability3
Documentation4

Proposed customer-shaped experiences

What customers could create on top.

The output could be an export, report, graph, artifact, application, agent, workflow, or downstream feed. These proposals are derived from documented access—not claims that SurveyMonkey ships them.

Single-platform patterns

  • Feedback program and response-analysis cockpit
  • Research synthesis room
  • Feedback triage console
  • Evidence-backed insight brief
Use in the brief builder →

Multi-platform compositions

  • SurveyMonkey + CRM or product analytics: research synthesis room
  • SurveyMonkey + work and knowledge system + content or planning platform: cross-system decision workspace
Explore composition recipes →

Evidence and dates

First-party references, with publisher and review dates separated

“Publisher updated” is shown only when the page exposes an update date. “BYO-UI reviewed” records when this research checked the reference. A missing publisher date is reported as missing—not replaced with the review date.

4 recorded sources
MCP / agent-role validationRepresentative source
https://help.surveymonkey.com/en/surveymonkey/integrations/claude-app/ ↗

Read and write tools, permission grant, plan and role effects, US data eligibility, protected-account defaults, admin disablement, and live-survey restrictions

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 22, 2026

SurveyMonkey Claude connector tools, permissions, governance, and limits reviewed 2026-07-22

API and webhooksSource inventory
https://developer.surveymonkey.com/api/v3/ ↗

First-party API reference.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Developer portalSource inventory
https://developer.surveymonkey.com/ ↗

First-party developer documentation.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

HomepageSource inventory
https://www.surveymonkey.com/ ↗

Product overview.

Publisher updated
Not stated by publisher
BYO-UI reviewed
Jul 10, 2026

Inventory source: structurally normalized; content was not individually reopened in this pass.

Verified fact

Tied to cited first-party evidence reviewed for this profile.

Source inventory

Official links recorded for deeper research but not necessarily reopened endpoint by endpoint.

Editorial assessment

System role, maturity interpretation, and architectural boundary.

Proposed design

Interface patterns and compositions—not vendor product claims.