SurveyMonkey
SurveyMonkey is an online survey development platform that enables users to create, distribute, and analyze surveys for various purposes.
Verdict
Common use cases
- Draft customer feedback surveys in chat
- Pull response data into analysis threads
- Archive completed surveys from workspace
- Share collector links with stakeholders
- Monitor response counts during campaigns
Integration
- Vendor
- SurveyMonkey
- Category
- other
- Auth
- OAUTH2
- Tools
- 8
- Composio slug
survey_monkey
Tools
- Create Survey
Tool to create a new survey. use when you have a survey title and need an id for follow-up operations. example: "create a survey titled 'customer satisfaction'"
- Delete Surveydestructive
Tool to delete a specific survey. use when the survey id is confirmed correct. deletion is irreversible. example prompt: "delete survey '123456789'."
- Get Contacts
Tool to retrieve a list of contacts. use after authenticating with surveymonkey. call this to fetch all contacts associated with your account.
- Get Groups
Tool to retrieve a list of groups. use after authentication when you need to enumerate or paginate through all groups in your surveymonkey account.
- Get Survey Collectors
Tool to retrieve a list of collectors for a specific survey. use when you need collector urls, counts, and statuses.
- Get Survey Details
Tool to retrieve metadata and counts for a specific survey. use after confirming the survey id.
- Get Survey Responses
Tool to retrieve a list of responses for a specific survey. use when you need to browse or filter responses after confirming the survey id.
- Get Surveys
Tool to retrieve a list of surveys. use when you need to enumerate or paginate through all surveys.
Setup
Setup guide
- 11. In Switchy, open your workspace settings and navigate to the Integrations tab. 2. Search for SurveyMonkey and click Connect. 3. You'll be redirected to SurveyMonkey's OAuth consent screen; log in with your SurveyMonkey account. 4. Grant the requested scopes: Create and View Surveys, View Responses, View Contacts, View Collectors. 5. After authorization, Switchy confirms the connection and displays the @SurveyMonkey handle. 6. Open any Space and type '@SurveyMonkey list my surveys' to verify the integration works. 7. If the MCP returns your survey list, the connection is live. 8. To invoke a tool, @mention SurveyMonkey in a message and describe the task — for example, '@SurveyMonkey create a survey titled Q1 Product Feedback' or '@SurveyMonkey get responses for survey 987654321'.
What teammates see: by default, memories from SurveyMonkey are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Create Feedback Survey
@SurveyMonkey create a survey titled 'Q2 Customer Satisfaction'. Return the survey ID so I can configure questions next.Open in a Space →
List All Surveys
@SurveyMonkey list all surveys in my account. Show the title, ID, and response count for each.Open in a Space →
Fetch Survey Responses
@SurveyMonkey get all responses for survey 123456789. Include timestamps and answer text for each respondent.Open in a Space →
Get Collector Links
@SurveyMonkey show me all collectors for survey 123456789. List the URL, type, and response count for each.Open in a Space →
Delete Old Survey
@SurveyMonkey delete survey 987654321. Confirm the title first, then proceed with deletion.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@SurveyMonkey list all surveys created in the last 30 days and show me their response counts
Found 4 surveys from the past month: 1. **Q1 Product Feedback** (created Jan 15) — 127 responses, 3 collectors active 2. **Employee Onboarding Check-in** (created Jan 22) — 43 responses, 1 collector 3. **Event Registration Interest** (created Feb 2) — 89 responses, 2 collectors 4. **Website Usability Test** (created Feb 8) — 12 responses, 1 collector This is an illustrative example. Your actual survey list will reflect your account's surveys, filtered by the date range you specify.
This example uses the Get Surveys tool to enumerate surveys, then pairs it with Get Survey Details to pull response counts. Requires OAuth scope for reading survey metadata. Pagination applies if you have many surveys; the MCP fetches one page at a time by default.
@SurveyMonkey create a new customer satisfaction survey with 5-point scale questions about product quality, support responsiveness, and likelihood to recommend
Created survey **Customer Satisfaction Survey** (ID: 987654321). The survey includes three 5-point Likert scale questions: - How would you rate the quality of our product? - How responsive was our support team? - How likely are you to recommend us to a colleague? This is an illustrative example. The MCP creates the survey shell; you'll need to use SurveyMonkey's UI or additional API calls to configure question text, logic, and collector settings before sending.
This example demonstrates the Create Survey tool, which generates a survey ID for follow-up operations. The MCP creates the survey container but does not auto-populate questions from natural language—you'll still configure question details in SurveyMonkey's interface or via additional tool calls. OAuth write scope required.
@SurveyMonkey pull all responses from survey 987654321 and summarize the top 3 themes from open-ended feedback
Retrieved 127 responses from **Customer Satisfaction Survey**. Analyzing open-ended feedback: **Top 3 themes:** 1. **Shipping delays** — 34 mentions; customers cite longer-than-expected delivery times. 2. **Intuitive interface** — 28 mentions; users praise ease of navigation and setup. 3. **Support wait times** — 19 mentions; mixed feedback on response speed during peak hours. This is an illustrative example. The AI synthesizes themes from the response text returned by the MCP; actual themes depend on your survey's question structure and respondent input.
This example pairs the Get Survey Responses tool with the AI's reasoning to extract qualitative insights. The MCP fetches raw response data; the AI performs the thematic analysis. Rate limits apply to response retrieval—large surveys may require multiple calls. OAuth read scope for responses required.
Use-case deep-dives
When SurveyMonkey fits recurring event retrospectives
A 6-person event ops team runs monthly webinars and needs to send the same satisfaction survey to 200-300 attendees each time. The SurveyMonkey MCP is the right call here: create the survey once in Switchy, pull collector URLs with Get Survey Collectors, then pipe those links into your email automation. The Get Survey Responses tool lets the team pull raw feedback into a shared chat thread for post-mortem analysis without logging into the web UI. The threshold: if you're sending more than 5 surveys a month with different question sets, the 8-tool scope starts to feel thin—you'll want question-level editing, which this MCP doesn't expose. For a stable template workflow, though, this keeps the survey lifecycle in one workspace and cuts the tab-switching overhead.
SurveyMonkey for quarterly NPS rollups at scale
A 3-person product team at a B2B SaaS company sends quarterly NPS surveys to 1,500 customers and needs to aggregate responses by account tier. The SurveyMonkey MCP handles this well: use Get Surveys to confirm the survey ID, then Get Survey Responses to pull the raw data into Switchy for analysis alongside your CRM exports. The OAuth2 flow means the whole team can authenticate once and share access to the same survey inventory. The trade-off: this MCP doesn't expose question-level filtering or custom variables, so if your survey has 15 questions and you only care about two, you're pulling the full payload and filtering in-chat. If your NPS survey is under 10 questions and you're doing quarterly rollups, the simplicity wins. For weekly micro-surveys with complex branching logic, look elsewhere.
When SurveyMonkey MCP misses for real-time support workflows
A 10-person support team wants to send a 2-question CSAT survey after every ticket close and route low scores to a Slack channel in real time. The SurveyMonkey MCP is borderline here. You can create the survey and pull responses with Get Survey Responses, but the tool doesn't expose webhooks or real-time triggers—you're polling for new responses, which adds latency. If your ticket volume is under 50 a day and you're okay with a 5-minute polling loop, this works as a lightweight integration. Above that threshold, or if you need sub-minute response routing, the MCP's tool set isn't built for it. The buying call: use this for post-hoc analysis of support surveys, not for live alerting. If real-time matters, you need SurveyMonkey's native webhook API, not this MCP.
Frequently asked
What can the SurveyMonkey MCP do in Switchy?
It lets your team create surveys, pull response data, manage collectors, and delete surveys—all from Switchy's chat interface. You can ask questions like 'show me responses for survey 123' or 'create a customer satisfaction survey', and the MCP handles the SurveyMonkey API calls. It's useful for teams who run surveys regularly and want to automate reporting or trigger follow-ups without opening the SurveyMonkey dashboard.
Do I need admin access to connect SurveyMonkey?
You need a SurveyMonkey account with OAuth permissions to read surveys, responses, contacts, and groups, plus write access to create and delete surveys. The MCP uses OAuth2, so you'll authorize Switchy during setup. If your team uses a shared SurveyMonkey account, whoever owns that account should connect it—other team members can then use the MCP through Switchy without needing their own SurveyMonkey login.
Can the MCP edit existing survey questions?
No. The MCP can create new surveys and delete them, but it doesn't expose tools to modify questions, logic, or design of an existing survey. If you need to change a survey's content, you'll still open SurveyMonkey's web editor. The MCP is built for survey lifecycle management and data retrieval, not authoring. Think of it as a read-heavy integration with basic create/delete write actions.
Why use this instead of exporting CSV files from SurveyMonkey?
The MCP pulls live response data on demand, so you can ask 'how many responses did we get today' without waiting for a manual export. It's faster for ad-hoc analysis and lets you chain survey data with other tools in Switchy—like sending new responses to Slack or updating a Google Sheet. If you only export once a month, stick with CSV. If you check responses daily, the MCP saves clicks.
Who on the team should connect the SurveyMonkey MCP?
Whoever owns your team's SurveyMonkey account and has permission to authorize third-party apps. Once connected, any Switchy workspace member can use the MCP to read surveys and responses, but only the connector's SurveyMonkey permissions apply. If your team has multiple SurveyMonkey accounts, connect the one that holds the surveys you want to query most often.