Skip to content

Cursor Clipform clipform_update_node

How to: Cursor Clipform clipform_update_node

client:Cursor transport:streamable-http tool:clipform_update_node

Add Clipform to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "mcp-server": {
      "url": "https://mcp.clipform.io"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something clipform_update_node does. Cursor lists the server's tools on connect and calls clipform_update_node itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that Clipform's identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

Clipform will not start until these are set, so clipform_update_node never becomes available.

  • CLIPFORM_API_KEY
  • API_URL

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.