Every Monday, we pull back the curtain on what’s new in Workato Enterprise MCP.
This Week
Two new servers split the SurveyMonkey lifecycle in half: an Authoring server for building and revising surveys, and a Distribution server for getting them in front of people and tracking responses. That brings the catalog to 62 production-ready servers.
What’s New
SurveyMonkey Authoring — 10 tools
Creates surveys from scratch, a SurveyMonkey template, or by copying an existing one, then builds them out page by page and question by question. Reads a survey’s full structure before editing it, and pulls from SurveyMonkey’s question bank and template library. Deletes aren’t exposed here, even though the underlying API supports them, that’s a deliberate scope decision to prevent accidental deletions.
View SurveyMonkey Authoring documentation →
SurveyMonkey Distribution — 14 tools
Publishes a survey via web-link, email, or SMS, sends invitations to individual recipients or reusable contact lists, and tracks response counts. Also manages webhook subscriptions for downstream automation, including a guarded delete for cleaning up old webhooks.
View SurveyMonkey Distribution documentation →
Why This Matters
The two servers share one thing: a survey id. Everything else stays split. Authoring can rename a survey, add a page, or revise a question, but it can’t publish anything or tell you who’s responded. Distribution can generate a link, send five hundred emails, and count responses, but it can’t touch a single word of the survey itself. That boundary matches how the work actually happens, a researcher designing a survey and a coordinator sending it to last quarter’s contact list are doing different jobs, or one person doing both, just not in the same step.
The safety design goes further than scope alone. SurveyMonkey’s API supports deleting surveys, pages, and questions, but the Authoring server doesn’t expose any of it, a survey someone spent an hour building isn’t at risk from one wrong conversational turn. The Distribution server’s delete surface is narrow. It can only delete webhook subscriptions and it’s still a guarded action, requiring confirmation before firing.
Composability Pairings
SurveyMonkey Authoring + SurveyMonkey Distribution: build a customer satisfaction survey from a template, then hand its id to Distribution to create an email collector and send it to a contact list.
SurveyMonkey Distribution + Slack: check response counts on an active survey, then post a status update in a team channel without opening SurveyMonkey.
SurveyMonkey Authoring + Google Slides: pull a survey’s question structure into a deck when prepping a stakeholder review of what’s about to go out.
Real-World Use Cases
SurveyMonkey Authoring for the researcher building a new survey.
- “Create a customer satisfaction survey from the NPS template.”
- “Add three rating questions to page 2.”
- “What’s already on this survey right now?”
- “Rename this survey and update the submit button text.”
Design notes: get_survey_details is the read step before add_question or update_question touches anything, so edits land on the right page and question. list_survey_templates and list_question_bank_questions give the AI assistant starting material instead of writing questions from scratch. There’s no delete_survey, delete_page, or delete_question tool, even though the underlying API allows it.
SurveyMonkey Distribution for the coordinator getting a survey out the door.
- “Give me a link I can paste in Slack.”
- “Email this survey to last quarter’s attendees.”
- “How many people have completed it so far?”
- “Stop the webhook feeding the old integration.”
Design notes: find_survey returns just enough to confirm the right survey, id, title, question count, without exposing its structure, since that’s the Authoring server’s job. list_responses and get_response return counts and basic metadata, not answer text or aggregated analytics. delete_webhook is the one destructive action this server exposes, and it’s guarded.
What Makes These Enterprise-Ready
Verified User Access: All tool calls execute under the authenticated user’s own SurveyMonkey identity. Survey edits, invitations, and webhook changes are attributed to the acting user.
Managed infrastructure: Workato hosts, scales, and maintains both servers. No API versions to track, no rate limits to manage, no infrastructure to provision.
No accidental deletions: Surveys, pages, and questions can be created and updated, but never deleted through the Authoring server, even though the underlying API supports it. delete_webhook is the only destructive action the Distribution server exposes, and it’s treated as a guarded write rather than an immediate deletion.
Clear scope boundaries: The Authoring server can’t publish or read responses. The Distribution server can’t touch the survey structure.
Composable: These servers can chain with Slack, Google Slides, and the rest of the catalog for workflows spanning survey design, distribution, and reporting.
Audit trails: Every tool call is logged with full context: who, what, when, and what was returned.
Get Started
SurveyMonkey Authoring and SurveyMonkey Distribution are available now for Workato customers with Enterprise MCP.
Install time: Minutes
Custom development: None
Deployment complexity: One-click activation
View the full catalog — now 62 pre-built servers.
Ready to connect your stack? Check out our self-service trial.
The bottom line: Other vendors are still announcing MCP roadmaps. We’re shipping production-ready servers every week.
See you next Monday.