Skip to content
Custom Connectors
SolutionsConnectorsPricingResourcesBlog
Build my connector

Connect Paperform to Claude Code

Have Claude edit forms and triage submissions in Paperform. From the terminal, inside the sessions where you already work.

Build my connectorTalk to us

How do you connect Paperform to Claude Code?

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

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

Full read-write Paperform access lets Claude edit existing forms, adjust fields and logic, read and summarize submissions, and manage products, coupons, and submission webhooks once you approve. The editing and triage that used to mean clicking through the editor and exporting spreadsheets happen where your forms already live.

  • Update an existing form's fields, questions, and options from a brief
  • Edit an existing form's fields, options, or conditional logic
  • Read and summarize recent submissions for a given form
  • Read submissions and record tags or status in a connected CRM or sheet
  • Export or hand off submission data to another connected tool
  • Set up or update a submission webhook to push responses to a connected tool

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

More on the Paperform connector

Paperform 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