How do I install Clipform?

Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Clipform need an API key?

The publisher lists these environment variables: CLIPFORM_API_KEY, API_URL.

When was Clipform last checked?

Last checked 2026-11-11. Interactive video forms that capture authentic responses. Build engaging forms in minutes.

Clipform MCP server

Power your agent

Add this server

The publisher's own URL. Not a PlugMCP endpoint.

Add to Cursor Add in Claude Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Server URL

https://mcp.clipform.io

Credentials from the publisher

CLIPFORM_API_KEY — API key that scopes tool calls to your workspace (create one in the dashboard under Settings, API keys). Not needed to list tools, only to call them.
API_URL — Clipform API base URL.

The Claude button above opens Claude with the name and URL filled in. You still confirm it there.

shClaude Code

1claude mcp add --transport http io.github.clipform-mcp-server https://mcp.clipform.io

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.clipform-mcp-server": {4      "command": "npx",5      "args": [6        "-y",7        "mcp-remote",8        "https://mcp.clipform.io"9      ]10    }11  }12}

claude_desktop_config.json

Remote · HTTPPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Remote

Transport: http
Version: 5.5.0

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

@clipform/mcp-server

MCP server for Clipform - build and manage video-style forms from any MCP client (Claude, ChatGPT, Cursor, Windsurf, etc.).

Install

There are two ways to connect: remote (recommended, uses your Clipform account) and local (anonymous, free-tier limits).

Remote (recommended)

Use this if you have a Clipform account. Forms are created directly in your workspace and your plan tier applies (no 3-node cap on Pro).

Claude (claude.ai): Settings → Connectors → Add custom connector → enter https://mcp.clipform.io

ChatGPT: Settings → Connectors → Advanced → enable Developer Mode → Create connector → enter https://mcp.clipform.io (requires Pro/Team/Enterprise)

Any MCP client with OAuth: Point it at https://mcp.clipform.io - discovery, registration, and auth are handled automatically via OAuth 2.1 + Dynamic Client Registration (RFC 7591).

Local - Claude Code / Claude Desktop / Cursor / etc.

Use this for stdio-based MCP clients. Pass your API key to authenticate with your workspace and plan tier.

Claude Code:

claude mcp add clipform -e CLIPFORM_API_KEY=cf_xxx -- npx -y @clipform/mcp-server

Claude Desktop / Cursor / Windsurf / OpenClaw - add to your MCP config:

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

Generate an API key in your Clipform dashboard under Developers > API keys. The local server always needs one - to try Clipform without an account, connect to https://mcp.clipform.io instead (see "How it works").

Environment variables

Variable	Required	Purpose
`CLIPFORM_API_KEY`	For workspace auth	Bearer key - forms land in the key's workspace with its plan limits. Also unlocks the creative tools (search, TTS, video rendering). Required by the local server.
`API_URL`	Yes	Clipform API base URL (`https://api.clipform.io`, or your local/self-hosted API).

Tools

Your MCP client lists these automatically on connect (via tools/list). Full reference - arguments, schemas, and examples - is in the docs.

Tool	Description
`clipform_create_form`	Create a new Clipform (interactive video-style form).
`clipform_import_form`	Convert a public Google Form, Typeform, or Tally form into a new Clipform.
`clipform_list_forms`	List forms in your workspace with optional filtering.
`clipform_whoami`	Show the current identity: auth mode (api key, oauth, session, or anonymous), active workspace, and plan limits.
`clipform_get_form`	Retrieve a form's details including all nodes in sequential order and their routing.
`clipform_update_form`	Update a form's title, publish status, settings, or tags.
`clipform_delete_form`	Move a form and all its nodes to the trash.
`clipform_get_results`	View response counts, choice/action answer breakdowns, and recent open-text answers for a form.
`clipform_get_responses`	List a Clipform form's individual responses (submissions) with time filtering - complements clipform_get_results (aggregates).
`clipform_add_node`	Add a new node to an existing form.
`clipform_update_node`	Update one or more existing nodes' text, type, config, or options.
`clipform_delete_node`	Delete a node from a form.
`clipform_upload_media_asset`	Put one or more media files into your workspace media library (max 10, uploaded sequentially).
`clipform_complete_media_upload`	Confirm a signed-PUT still image upload finished, after PUTting the bytes to the upload_url returned by clipform_upload_media_asset.
`clipform_attach_node_media`	Attach an existing workspace media asset (from clipform_upload_media_asset) to one or more nodes (max 10).
`clipform_get_node_media`	Get the media attached to a node, including processing status.
`clipform_delete_node_media`

Example

Create a Clipform called "Customer Feedback" with a choice question asking "How would you rate our service?" with options Excellent, Good, Fair, Poor, then an open-ended question asking "Any additional comments?", and finish with an end screen saying "Thanks for your feedback!"

How it works

Remote (OAuth): Bearer tokens are audience-bound to https://mcp.clipform.io (RFC 8707) and scoped to mcp only. Forms land directly in the workspace you approved during consent by default. One connection reaches every workspace you belong to in the same company: pass workspace_id (ids from clipform_whoami) on clipform_create_form, clipform_import_form, clipform_list_forms, clipform_upload_media_asset, or clipform_generate_tts, or a form_id from another workspace on any form tool - including clipform_upload_media_asset, clipform_generate_tts, and clipform_complete_media_upload, where it's a routing hint only (the result still lands in that workspace's media library, not on a node). Membership is re-checked on every call, and results name the workspace.

Local with API key: The CLIPFORM_API_KEY is sent as a standard Authorization: Bearer header. Forms are created directly in the key's workspace with your plan tier limits.

Remote anonymous (no sign-in): Connecting to https://mcp.clipform.io without signing in builds into a temporary account of the session's own. Forms stay drafts with a private preview link - nothing goes live - and while unclaimed, the form UUID is the credential to edit it. Build results include a one-time claim URL that signs you into that account (on the first form, periodically after, and at the form limit); free-plan limits apply. The local stdio server always needs CLIPFORM_API_KEY.

These tools need a signed-in Clipform account (OAuth, or an API key): clipform_list_forms, clipform_whoami, clipform_get_results, clipform_get_responses, clipform_delete_form. An anonymous remote session that calls one is asked to sign in instead. Everything else, including clipform_get_guide, clipform_get_workflow and clipform_list_assets, works without an account.

Forms are created with a start node and end screen automatically - you just add the nodes in between.

Clipform

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Clipform?

Does Clipform need an API key?

What transport does Clipform use?

When was Clipform last checked?

Documentation

@clipform/mcp-server

Install

Remote (recommended)

Local - Claude Code / Claude Desktop / Cursor / etc.

Environment variables

Tools

Example

How it works

Links