Clipform MCP

What Clipform MCP does

Clipform MCP exposes Clipform form-building and creative-production features through MCP tools. It can create video-style forms from a title and ordered nodes, return viewer and builder links, import questions from public Google Forms, Typeform, or Tally forms, and manage existing forms in a workspace.

Forms can include choice questions, open text, contact details, payments, buttons, redirects, downloads, and completion screens. The server also supports node-level editing, media attachments, linear routing, publishing, tags, deletion, and response inspection. Response tools provide both aggregate results and individual submissions, with some sensitive or media-heavy answers represented by counts or placeholders.

How it works

The recommended remote connection uses https://mcp.clipform.io with OAuth 2.1 and dynamic client registration. A signed-in connection places forms in the approved Clipform workspace and applies that workspace’s plan. The local package communicates with the Clipform API over stdio and authenticates with a bearer API key.

Remote connections can also run anonymously. In that mode, forms are created in a temporary session account, go live after content checking, accept up to three responses, and go offline after seven days unless claimed. Account-dependent functions such as payments, uploads, downloads, and external links remain disabled until sign-up. A one-time claim link may be returned during form creation.

Forms receive a start node and end screen automatically. Add intermediate nodes with clipform_create_form or clipform_add_node, then use clipform_update_node and clipform_set_logic for changes. Option-based branching is configured in Clipform’s dashboard rather than by clipform_set_logic.

Setup and configuration

For remote use, point an OAuth-capable MCP client at https://mcp.clipform.io. Claude.ai and ChatGPT have connector-specific setup flows; other OAuth clients can use the same endpoint.

For local stdio use, install the npm package through npx and provide the API endpoint and workspace API key. A typical MCP configuration is:

{
  "mcpServers": {
    "clipform": {
      "command": "npx",
      "args": ["-y", "@clipform/mcp-server"],
      "env": {
        "CLIPFORM_API_KEY": "cf_xxx",
        "API_URL": "https://api.clipform.io"
      }
    }
  }
}

Create API keys in Clipform under Developers > API keys. API_URL can point to the hosted API or a local/self-hosted API deployment. The local server requires an API key; anonymous testing uses the remote endpoint instead.

Tools and capabilities

• Create, import, list, inspect, update, publish, and delete forms.
• Add, edit, remove, and linearly connect form nodes.
• Collect choices, text, contact details, payments, files, acknowledgments, and redirects.
• Upload media, complete still-image uploads, attach assets to supported nodes, and inspect media status.
• Generate narrated audio with word-level captions and search news, images, stock video, music, and creative assets.
• Browse and render video templates or custom compositions, then check asynchronous render jobs.
• Retrieve response aggregates, time-filtered submissions, GeoJSON boundaries, form guidance, and build workflows.

Limitations and notes

Imported source forms must be publicly accessible. Unsupported or ambiguous question types are skipped and reported rather than converted speculatively. Workspace listing, identity, results, response, and deletion operations require a signed-in account.

Media operations have workflow constraints: still-image uploads require confirmation after the signed upload completes, while video uploads settle automatically. Rendering can attach output directly to a form node when node_id and form_id are supplied. For multi-item renders, jobs can be checked together with clipform_check_render.

Individual response data is intentionally limited. Contact details, file uploads, and audio or video answers are redacted, and payment data is reduced to amount and status; detailed customer payment information remains in the Clipform dashboard. Destructive form and node operations require confirmation.