Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Wufoo to Claude Code

Let Claude read, filter, and triage incoming Wufoo entries. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Wufoo to Claude Code?

Claude Code reaches outside tools through MCP servers. To connect Wufoo, you add a Wufoo MCP server: a small hosted service that exposes Wufoo'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 Wufoo account. No API keys pasted into config files.

claude mcp add --transport http wufoo 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 Wufoo once connected?

Read-write Wufoo access lets Claude pull and filter incoming entries, summarize submissions, submit new entries on your behalf, register or remove webhooks to drive follow-up, and export filtered submissions on request. The sorting and routing that used to mean manual clicks happen where the data already lives, after you approve. Building forms and editing fields still happen in the Wufoo builder, since the API is read-only for form structure.

  • Pull and filter entries from a form to summarize submissions
  • Submit a new entry to a form from data you provide
  • Export a filtered set of submissions for a report once you approve
  • Register or remove a webhook so a matching entry drives follow-up
  • Flag entries that need follow-up in your summary or a connected task tool
  • List forms and reports to point Claude at the right submissions

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 Wufoo 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 Wufoo API. The protocol is open. What you take on is everything around the happy path: OAuth token refresh, hosting, monitoring, keeping up when Wufoo 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 Wufoo 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 Wufoo 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 Wufoo 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 Wufoo'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 Wufoo?
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 Wufoo account it signs in with. Revoking access is one click in Wufoo.

More on the Wufoo connector

Wufoo connector for claude.aiSurveyMonkey + Claude CodeTally + Claude CodeFormstack + 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