Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Formstack to Claude Code

Let Claude build forms and fix submissions in Formstack. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Formstack to Claude Code?

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

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

Full read-write Formstack access lets Claude create and edit forms, add or reorder fields, update submission data, manage folders, and configure notifications, all with your approval. The form-building and submission cleanup that used to mean clicking through the builder happen in the same flow as your other work.

  • Create a new form or duplicate an existing one as a starting point
  • Add, reorder, or update fields on an existing form
  • Edit or correct a submission's stored data
  • Move forms or submissions between folders to organize them
  • Update form notifications or confirmation settings
  • Mark submissions read or flag them for follow-up

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

More on the Formstack connector

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