Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect SurveyMonkey to Claude Code

Make Claude build surveys and triage responses in SurveyMonkey. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect SurveyMonkey to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect SurveyMonkey, you add a SurveyMonkey MCP server: a small hosted service that exposes SurveyMonkey's data and actions over the Model Context Protocol. With a custom connector we build for you, that is one command in the terminal, then an OAuth sign-in with your own SurveyMonkey account. No API keys pasted into config files.

claude mcp add --transport http surveymonkey https://your-connector-url/mcp

Then run /mcp inside a Claude Code session to sign in. Add it with --scope project and the connector is checked into the repo for your whole team.

What can Claude Code do in SurveyMonkey once connected?

Full read-write SurveyMonkey access lets Claude create a survey from a brief, add or reorder questions, configure collectors, and triage incoming responses in one place. The build-and-iterate work and the follow-up that used to mean clicking through the editor happen where your surveys already live, once you approve.

  • Create a new survey from a brief and add questions in order
  • Add, edit, or reorder questions and answer choices on an existing survey
  • Set required fields and answer validation rules on questions
  • Create or configure a collector and prepare a share link
  • Read incoming responses and update response status to triage submissions
  • Update a survey's title, settings, or theme before you launch it

One connector, every Claude surface

The connector we build is a remote MCP server, which is the same standard claude.ai and Claude Desktop use. Add it once and the same SurveyMonkey access works in Claude Code for you, in claude.ai for the rest of the team, and in Claude Desktop. One build, one set of permissions, one monthly plan covering all of them.

Build it yourself, or have it built?

If you live in the terminal, you can absolutely write your own MCP server against the SurveyMonkey API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when SurveyMonkey changes its API and when the MCP spec itself moves, and scoping write actions so an agent can never do more than you intended. We build SurveyMonkey connectors with separated read and write tools and approval gates on destructive actions, then host and maintain them so they keep working while you work.

Frequently asked questions

Does the same SurveyMonkey connector work in claude.ai and Claude Code?
Yes. It is one remote MCP server. Claude Code adds it with a single "claude mcp add" command; claude.ai and Claude Desktop add it as a custom connector in Settings. Each person signs in with their own SurveyMonkey account, so access always matches what that person can already see and do.
Do I need to host or maintain anything myself?
No. The connector runs as a hosted service we operate: we handle uptime, token health, API changes on SurveyMonkey's side, and MCP spec migrations under the monthly plan. Your side is one command in the terminal and an OAuth sign-in.
Is it safe to give a coding agent write access to SurveyMonkey?
Write access is scoped, not blanket. Read tools and write tools are separated, destructive actions like deleting or sending are gated behind your explicit approval, and the connector can never exceed the permissions of the SurveyMonkey account it signs in with. Revoking access is one click in SurveyMonkey.

More on the SurveyMonkey connector

SurveyMonkey connector for claude.aiTally + Claude CodeFormstack + Claude CodeWufoo + Claude Code

Tell us what you run. We'll build the connector.

Pick your tool, choose what Claude should do, and get an instant scope and price. No call required.

Build my connectorTalk to us