Build Stepper workflows by asking Claude or ChatGPT
You know what should happen after a form comes in. Wiring up the trigger, the app steps and the field mapping is the slow part. Describe it to your assistant instead. It builds the workflow in Stepper, tests each step against your connected apps, and publishes it when you say so.
What you can ask for
Build.
"When someone submits my order form, add a row to my Google Sheet and email me a summary."
Your assistant builds the workflow, picks the right sheet and columns with you, and shows you what each step would write.
Test.
"Try the Google Sheets step with the last submission."
It runs that step on sample data, so the test can write a real row or send a real message. It asks you first when it would, and you see the result before the workflow goes live.
Fix.
"Why did my onboarding workflow fail yesterday?"
It reads the run, tells you which step failed and why, and suggests the change.
It can't connect your accounts for you. When a workflow needs an app you haven't connected, it gives you a link to connect it in Stepper.
Skill Sets or the MCP server?
Stepper has two MCP servers. Pick the one that fits the job.
| Compare | Skill Sets | MCP server |
|---|---|---|
| What it's for | Giving an AI agent a curated, permissioned set of app actions it can call | Building, testing, publishing and fixing Stepper workflows |
| You set up | Which apps and actions the agent may use | Nothing beyond signing in |
| Also covers | Paperform forms and Papersign documents, if your team uses them |
You stay in charge
- ✓ Everything opens in the visual editor. Each workflow your assistant builds is a normal Stepper workflow. Open it, read every step, and change it by hand whenever you like.
- ✓ You approve what goes live. Your assistant is set up to check with you before it publishes or runs a workflow, or tests a step that sends something real. Your AI app also asks you to allow each action, unless you've chosen to always allow it.
- ✓ Your account, your sign-in. You connect by signing in and approving access. No password goes to the assistant.
- ✓ Disconnect any time, from your assistant's settings.
Connect it
| Where you work | How |
|---|---|
| Claude (web, desktop) | Settings → Connectors → Browse connectors, then search for Paperform. If it isn't listed yet, choose Add custom connector and paste the server URL. |
| ChatGPT | Apps → search for Paperform |
| Claude Code | claude mcp add --transport http paperform https://api.paperform.app/mcp |
| Cursor | Add to Cursor |
| VS Code | Install in VS Code |
| Anything else | Server URL https://api.paperform.app/mcp
Streamable HTTP with OAuth sign-in.
|
You sign in to your account and approve access when you connect. You can create an account in the same window.
Questions
Which plans include it?
Every Stepper plan, including Free.
Does it use my credits or steps?
Yes, the same as any other workflow. Workflows your assistant builds are normal Stepper workflows, and their runs use credits as usual.
What if it gets something wrong?
Your assistant checks with you before anything goes live, and you can open every workflow in the visual editor. AI can misread a request, so check the steps and the data each one writes before you approve.
Describe the workflow you keep putting off
The same connection builds Paperform forms and sends Papersign documents.