Clipform

Video form builder for engaging, mobile-friendly forms

Clipform turns a conversation into an interactive, video-first form. Describe the quiz, survey, feedback form, or sign-up you want, and your AI builds it in your Clipform workspace - questions, options, scoring, answer feedback, an end screen, and a shareable link - in one go.

What you can ask

Build a structured application form - job applications, programme admissions, grant proposals with video responses
Example path

MCP connector

Server URL: https://mcp.clipform.io
Login: OAuth
Protocol: MCP 2026-07-28
Instructions: Clipform builds interactive video-style forms that other people fill in, with their answers (video, audio, or text) stored for the owner to read back: quiz, survey, interview, testimonial, application, booking, client intake, and lead capture. Drafting questions as text to review or paste is a chat task, not a Clipform build. When this is the start of a new conversation and the user has not yet said what they want to build, welcome them as someone who is now connected to Clipform and offer to build their first form together, then offer these starting points as plain text: quiz, survey, interview, testimonial, application, booking, client intake, lead capture, or something else - ask which one fits, or invite them to describe what they need instead. If the user's first message already states what they want to build, even loosely, skip that offer entirely and go straight into the brief-driven flow below. When the brief is clear, build the form directly; when it's vague, ask one or two short questions first. Prefer rich media: video over images over plain text. Before building, derive a register from the topic and audience (e.g. hype, playful, warm, considered, elegant, sombre); if the user states a mood explicitly, that wins. State the register once, then apply it to every rendering choice - narration tone, motion preset, music, pacing. Never mix registers in one form. At the start of a build, call to load the recipe for the form type, and for craft detail. Every *_id argument is a UUID returned by the tools - not the short share_id from a form URL. Use when the request is about the account itself (the active workspace, plan, or limits); building a form does not need it first. Deleting a form moves it to the trash (restorable from the dashboard); deleting a node cannot be undone (a node deleted on a live form stays on the live form until you publish); removing media from a node only unlinks it, and the media asset stays in the library. Those tools ask the user to confirm before running.

Tools

Reads data17

Changes data7

Deletes or can't be undone9

Skills

None in the store listings or on the server

What you can ask

Build a structured application form - job applications, programme admissions, grant proposals with video responses

Example path

MCP connector

Server URL

https://mcp.clipform.io

OAuth

Protocol

MCP 2026-07-28

Instructions

Clipform builds interactive video-style forms that other people fill in, with their answers (video, audio, or text) stored for the owner to read back: quiz, survey, interview, testimonial, application, booking, client intake, and lead capture. Drafting questions as text to review or paste is a chat task, not a Clipform build. When this is the start of a new conversation and the user has not yet said what they want to build, welcome them as someone who is now connected to Clipform and offer to build their first form together, then offer these starting points as plain text: quiz, survey, interview, testimonial, application, booking, client intake, lead capture, or something else - ask which one fits, or invite them to describe what they need instead. If the user's first message already states what they want to build, even loosely, skip that offer entirely and go straight into the brief-driven flow below. When the brief is clear, build the form directly; when it's vague, ask one or two short questions first. Prefer rich media: video over images over plain text. Before building, derive a register from the topic and audience (e.g. hype, playful, warm, considered, elegant, sombre); if the user states a mood explicitly, that wins. State the register once, then apply it to every rendering choice - narration tone, motion preset, music, pacing. Never mix registers in one form. At the start of a build, call to load the recipe for the form type, and for craft detail. Every *_id argument is a UUID returned by the tools - not the short share_id from a form URL. Use when the request is about the account itself (the active workspace, plan, or limits); building a form does not need it first. Deleting a form moves it to the trash (restorable from the dashboard); deleting a node cannot be undone (a node deleted on a live form stays on the live form until you publish); removing media from a node only unlinks it, and the media asset stays in the library. Those tools ask the user to confirm before running.

Tools