Picflow API and MCP server Let your AI agent set up galleries and follow the feedback.

ToolWhat it doesAccess

• upload_assets Create a gallery if needed and upload images, videos or other files into it. writeAsks first

  Picflow takes the major image formats, RAW photos, video, PDF and design files, and stores any other file without a preview. RAW files are shown as resized JPGs while the original stays intact. Uploading reaches no one until the gallery is shared. By default you confirm each call; you can switch that off for this tool.

  MCP callpicflow_write → upload_assets

  REST endpointPOST https://cotlet.dev/api/v1/picflow/assets

  Parameters

  Parameters: upload_assets

  Name	Type	Description
  gallery string required	string	Gallery name, as manage_folders lists it.
  files array required	array	Links the Cloud Browser can download, one per file.
  create boolean	boolean	Set true to create the gallery first.

  Example input

  {
    "gallery": "gallery",
    "files": "files"
  }

  Example response

  {
    "gallery": "Lake House Wedding",
    "uploaded": 3,
    "files": [
      "ceremony-001.jpg",
      "ceremony-002.jpg",
      "first-dance.mp4"
    ]
  }

• import_from_cloud_storage Create a gallery from files in Dropbox, Google Drive or Box through Select Source. writeAsks first

  Picflow asks you to authorize the provider once. The first time, you do that yourself in the Cloud Browser; after that the agent picks the files and confirms the import. By default you confirm each call; you can switch that off for this tool.

  MCP callpicflow_write → import_from_cloud_storage

  REST endpointPOST https://cotlet.dev/api/v1/picflow/cloud-storages

  Parameters

  Parameters: import_from_cloud_storage

  Name	Type	Description
  gallery string required	string	Gallery name, as manage_folders lists it.
  provider string required	string	One of `dropbox`, `google_drive`, `box`.
  path string required	string	Folder or files to import, as the provider shows them.

  Example input

  {
    "gallery": "gallery",
    "provider": "provider",
    "path": "path"
  }

  Example response

  {
    "gallery": "Spring Lookbook",
    "provider": "dropbox",
    "path": "/Clients/Example Brand/Spring",
    "imported": 48
  }

• manage_folders List folders and galleries, create, rename or move a folder, unfold it, or delete it. writeAsks first

  Folders can nest. Unfold moves every gallery one level up. Deleting a folder deletes all galleries in it, so the agent lists them and waits for your OK. By default you confirm each call; you can switch that off for this tool.

  MCP callpicflow_write → manage_folders

  REST endpointPOST https://cotlet.dev/api/v1/picflow/folders/manage

  Parameters

  Parameters: manage_folders

  Name	Type	Description
  action string required	string	One of `list`, `create`, `rename`, `move`, `unfold`, `delete`. `list` and `get` only read.
  folder string	string	Folder name; leave empty with `list` for the dashboard root.
  new_name string	string	For `create` and `rename`.
  to string	string	For `move`: the parent folder.

  Example input

  {
    "action": "action"
  }

  Example response

  {
    "folder": "Weddings 2026",
    "galleries": [
      {
        "gallery": "Lake House Wedding",
        "assets": 412,
        "approved": 86
      },
      {
        "gallery": "Garden Ceremony",
        "assets": 268,
        "approved": 120
      },
      {
        "gallery": "City Hall Elopement",
        "assets": 95,
        "approved": 40
      }
    ]
  }

• move_copy_gallery Move or copy a gallery to a folder or into another gallery as a Sub-Gallery, or delete it. writeAsks first

  This is Move/Copy to (...) on the dashboard or in the gallery menu. A deleted gallery is gone for your clients too, so delete waits for your OK. By default you confirm each call; you can switch that off for this tool.

  MCP callpicflow_write → move_copy_gallery

  REST endpointPOST https://cotlet.dev/api/v1/picflow/copy-gallery/move

  Parameters

  Parameters: move_copy_gallery

  Name	Type	Description
  action string required	string	One of `move`, `copy`, `delete`. `list` and `get` only read.
  gallery string required	string	Gallery name, as manage_folders lists it.
  to string	string	For `move` and `copy`: a folder, the root, or a gallery to nest it in.
  as_sub_gallery boolean	boolean	Set true to place it inside the `to` gallery.

  Example input

  {
    "action": "action",
    "gallery": "gallery"
  }

  Example response

  {
    "gallery": "City Hall Elopement",
    "action": "move",
    "to": "Weddings 2026",
    "done": true
  }

• manage_gallery_sections List, add, reorder or delete the sections of a gallery: images, sub-gallery, text or embed. writeAsks first

  Sections stack vertically and can be reordered at any time, even after sharing, so changes show at once to anyone with the link. By default you confirm each call; you can switch that off for this tool.

  MCP callpicflow_write → manage_gallery_sections

  REST endpointPOST https://cotlet.dev/api/v1/picflow/gallery-sections/manage

  Parameters

  Parameters: manage_gallery_sections

  Name	Type	Description
  action string required	string	One of `list`, `add`, `move`, `delete`. `list` and `get` only read.
  gallery string required	string	Gallery name, as manage_folders lists it.
  type string	string	For `add`: `image`, `sub_gallery`, `text` or `embed`.
  content object	object	For `add`: a text section's title and paragraph, or an embed section's content.
  position number	number	For `move`: the new place from the top.

  Example input

  {
    "action": "action",
    "gallery": "gallery"
  }

  Example response

  {
    "gallery": "Lake House Wedding",
    "sections": [
      {
        "type": "text",
        "title": "Welcome"
      },
      {
        "type": "image",
        "title": "Ceremony"
      },
      {
        "type": "sub_gallery",
        "title": "Reception"
      }
    ]
  }

ToolWhat it doesAccess

• manage_gallery_access Read or set who can open a gallery: link access, password, team access and invited guests. writeAsks first

  Public: anyone with the link. Protected: the link plus a password. Private: only invited collaborators. Galleries are visible to all team members unless hidden. Access changes decide who sees client work, so each waits for your OK. By default you confirm each call; you can switch that off for this tool.

  MCP callpicflow_write → manage_gallery_access

  REST endpointPOST https://cotlet.dev/api/v1/picflow/gallery-access/manage

  Parameters

  Parameters: manage_gallery_access

  Name	Type	Description
  action string required	string	One of `get`, `set_link`, `invite_guest`, `hide_from_team`. `list` and `get` only read.
  gallery string required	string	Gallery name, as manage_folders lists it.
  link_access string	string	For `set_link`: `public`, `protected` or `private`.
  password string	string	For `protected`.
  email string	string	For `invite_guest`: the guest, who needs a Picflow account.
  permission string	string	For `invite_guest`: what the guest may do, such as view, review, download or upload.

  Example input

  {
    "action": "action",
    "gallery": "gallery"
  }

  Example response

  {
    "gallery": "Lake House Wedding",
    "link_access": "protected",
    "guests": [
      {
        "email": "planner@example.com",
        "permission": "review"
      }
    ],
    "saved": true
  }

• get_share_links Get the link of a gallery or folder, or a gallery's embed code with its display options. read

  Returns the link or code; nothing is sent. Share it yourself, or hand it to your email or CRM step. An embedded gallery updates on your site when you change it in Picflow.

  MCP callpicflow_read → get_share_links

  REST endpointGET https://cotlet.dev/api/v1/picflow/share-links

  Parameters

  Parameters: get_share_links

  Name	Type	Description
  gallery string	string	A gallery, or leave empty and give `folder`.
  folder string	string	A folder; everyone with its link sees each gallery by that gallery's own access.
  embed object	object	Optional, galleries only: image_view (`overview` or `full_size`), cover and contact_info on or off.

  Example response

  {
    "gallery": "Lake House Wedding",
    "link": "https://example.picflow.com/lake-house-wedding",
    "access": "protected"
  }

ToolWhat it doesAccess

• read_feedback Read a gallery's feedback: favorites, comments, annotations, approval flags, labels and statuses. read

  Per asset: who favorited it, comments with replies, annotations, the approval flag, color label and asset status. Reviewers who identified themselves are named. Nothing is changed.

  MCP callpicflow_read → read_feedback

  REST endpointGET https://cotlet.dev/api/v1/picflow/feedbacks/read

  Parameters

  Parameters: read_feedback

  Name	Type	Description
  gallery string required	string	Gallery name, as manage_folders lists it.
  filter string	string	Optional: `favorites`, `comments`, `approved`, `rejected`, a color label or an asset status.

  Example input

  {
    "gallery": "gallery"
  }

  Example response

  {
    "gallery": "Lake House Wedding",
    "approved": 86,
    "rejected": 12,
    "comments": [
      {
        "asset": "ceremony-014.jpg",
        "by": "Example Client",
        "text": "Could this one be a little brighter?"
      }
    ]
  }

• reply_to_comment Reply to a reviewer's comment on an asset. writeAsks first

  The reply shows to the reviewer in the gallery. On Biz, team-only comments stay hidden from clients; the agent says which kind it posts. By default you confirm each call; you can switch that off for this tool.

  MCP callpicflow_write → reply_to_comment

  REST endpointPOST https://cotlet.dev/api/v1/picflow/comment/replies

  Parameters

  Parameters: reply_to_comment

  Name	Type	Description
  gallery string required	string	Gallery name, as manage_folders lists it.
  asset string required	string	File name of the asset.
  comment string required	string	The comment you answer, by its first words or author.
  text string required	string	Your reply.

  Example input

  {
    "gallery": "gallery",
    "asset": "asset",
    "comment": "comment",
    "text": "text"
  }

  Example response

  {
    "gallery": "Lake House Wedding",
    "asset": "ceremony-014.jpg",
    "reply": "Yes, I will brighten it in the final edit.",
    "posted": true
  }

• add_annotation Draw an arrow, line, circle or brush mark on an image, with a note. writeAsks first

  Annotations are visible to everyone who can review the gallery. Use them for retouch notes or crop lines. By default you confirm each call; you can switch that off for this tool.

  MCP callpicflow_write → add_annotation

  REST endpointPOST https://cotlet.dev/api/v1/picflow/annotations

  Parameters

  Parameters: add_annotation

  Name	Type	Description
  gallery string required	string	Gallery name, as manage_folders lists it.
  asset string required	string	File name of the image.
  tool string required	string	One of `brush`, `arrow`, `line`, `circle`.
  points array required	array	Positions as percentages of width and height: start and end for arrow and line, center and radius for circle, a path for brush.
  note string	string	What the mark means, for example "retouch here".

  Example input

  {
    "gallery": "gallery",
    "asset": "asset",
    "tool": "tool",
    "points": "points"
  }

  Example response

  {
    "gallery": "Lake House Wedding",
    "asset": "ceremony-014.jpg",
    "tool": "circle",
    "note": "Brighten the shadow on the left",
    "saved": true
  }

• set_asset_status Set one or many assets to Needs Review, In Progress, Approved or Rejected. writeAsks first

  Statuses are what your team and reviewers filter by. Approving counts toward the gallery's Approval Limit when one is set. By default you confirm each call; you can switch that off for this tool.

  MCP callpicflow_write → set_asset_status

  REST endpointPUT https://cotlet.dev/api/v1/picflow/asset-status

  Parameters

  Parameters: set_asset_status

  Name	Type	Description
  gallery string required	string	Gallery name, as manage_folders lists it.
  assets array required	array	File names.
  status string required	string	One of `needs_review`, `in_progress`, `approved`, `rejected`.

  Example input

  {
    "gallery": "gallery",
    "assets": "assets",
    "status": "status"
  }

  Example response

  {
    "gallery": "Spring Lookbook",
    "assets": 6,
    "status": "in_progress",
    "saved": true
  }

• configure_review_settings Turn review tools and downloads on or off for a gallery, set Approve-Only and an Approval Limit. writeAsks first

  Each gallery has its own settings. Reviewers see the change on their next visit, so the agent shows you the new settings first. By default you confirm each call; you can switch that off for this tool.

  MCP callpicflow_write → configure_review_settings

  REST endpointPOST https://cotlet.dev/api/v1/picflow/review-settings/configure

  Parameters

  Parameters: configure_review_settings

  Name	Type	Description
  gallery string required	string	Gallery name, as manage_folders lists it.
  review object	object	favorites, comments, annotations, approval_flags and color_labels on or off, plus custom label names.
  approve_only boolean	boolean	Hide all other statuses and show a single Approve button.
  approval_limit object	object	count, and `hard` true to stop approvals at the limit or false to let clients exceed it.
  downloads object	object	enabled, gallery ZIP on or off, and the image sizes offered.

  Example input

  {
    "gallery": "Lake House Wedding",
    "approve_only": true,
    "approval_limit": {
      "count": 100,
      "hard": false
    },
    "downloads": {
      "enabled": false
    }
  }

  Example response

  {
    "gallery": "Lake House Wedding",
    "approve_only": true,
    "approval_limit": {
      "count": 100,
      "hard": false
    },
    "downloads": {
      "enabled": false
    },
    "saved": true
  }

ToolWhat it doesAccess

• manage_team_members List workspace members with their roles, invite a member, change a role or remove someone. writeAsks first

  Admins can manage settings, billing and members; members create and manage projects. Some roles need a paid plan, and Biz includes 10 members. Only an owner or admin login can run the writes, and each waits for your OK. By default you confirm each call; you can switch that off for this tool.

  MCP callpicflow_write → manage_team_members

  REST endpointPOST https://cotlet.dev/api/v1/picflow/team-members/manage

  Parameters

  Parameters: manage_team_members

  Name	Type	Description
  action string required	string	One of `list`, `invite`, `set_role`, `remove`. `list` and `get` only read.
  email string	string	For `invite`, `set_role` and `remove`.
  role string	string	`admin` or `member`. The single owner cannot be changed here.

  Example input

  {
    "action": "action"
  }

  Example response

  {
    "members": [
      {
        "email": "alex@example.com",
        "role": "owner"
      },
      {
        "email": "editor@example.com",
        "role": "member"
      }
    ]
  }