mcp server
flask
Feedback layer for video. Reviewers talk through feedback; agents read it as structured comments.
Description as published by the maintainer. Source
- version 1.1.1
- active
active — Registry entry last updated 2026-07-08.
What this server can do
17 functions, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
asset_status(asset_id)- Check the processing status of a video asset. Returns progress percentage for videos being processed, or confirms the asset is ready. Required: asset_id.
contents(limit, offset, folder_id)- Browse contents. Without folder_id: lists what's at the team's top level (root) — both folders and assets that live directly at root. With folder_id: opens that folder and returns its child folders and assets (videos/media). Each item includes its URL.
feedback_get(element_id)- Get a single feedback item with its full reply thread. Returns the item's text body (for recordings: the AI-organized feedback), tags (by name), author, video timestamp, the recording's full verbatim transcript, visual_references (the pointing phrases - "this", "over here" - with the recording time each was spoken; feed them to get_frame to see what was being pointed at), visual attachments (images / has_drawing - render them with get_annotated_frames), and all nested replies. Required: element_id.
feedback_list(limit, offset, asset_id)- List top-level feedback on an asset. Returns each item's text body, tags (by name), author, timestamp, and reply_count. Recording items are ONE comment per recording: the text body is the AI-organized feedback, and the recording object adds the full verbatim transcript plus visual_references (the pointing phrases with the recording time each was spoken). Items with visual attachments carry images (attached image files) and/or has_drawing: true (a drawing made on the asset) - call get_annotated_frames to see them. Use feedback_get to read full reply threads. Required: asset_id.
feedback_post(tags, content, asset_id, reply_to, timestamp)- Create a feedback comment on an asset, as the connected user. PREFER passing timestamp (seconds into the video) whenever the source material has one - e.g. when importing feedback from an email like 'at 0:42 the logo is wrong', convert 0:42 to 42. Without timestamp the comment is a general (non-anchored) note. tags applies the team's EXISTING tags by name (see the tags tool); statuses are tags too. Use reply_to to reply in an existing thread. Cannot attach recordings, drawings, or images. Required: asset_id, content.
feedback_stats(to, from, asset_id, folder_id)- Aggregate feedback statistics across many assets in ONE call - counts per asset and per version (v1, v2, ...), split by type (text/recording), tag, and author, with first/last feedback timestamps. Scope to a folder (folder_id), one asset or version stack (asset_id), or the whole team; narrow the time window with from/to. Use this for trend questions like 'are v1 notes going down across this client's recent videos' or 'what tags dominate this folder' instead of calling feedback_list per asset. For reading the feedback text itself across assets, use recent_activity.
feedback_update(content, add_tags, timestamp, element_id, remove_tags)- Edit an existing feedback item. content (replaces the text) and timestamp (video time in seconds) can only be changed on the connected user's OWN comments. add_tags / remove_tags apply the team's existing tags by NAME and work on ANY feedback item you can comment on (labels and statuses are collaborative - e.g. add the 'Done' tag to mark feedback resolved). Provide at least one of content, timestamp, add_tags, remove_tags. Required: element_id.
get_annotated_frames(element_id)- Supplementary visuals for a feedback item. For recording items: the media under review with the reviewer's drawing rendered in, plus their shared SCREEN when they demonstrated something (e.g. a Photoshop/Figma mockup); webcam frames are NOT included, and the transcript is returned marked [FRAME N]. Also works for text comments that carry visuals: a standalone drawing (has_drawing: true) is rendered onto the frame it was drawn over, and attached images (images array) are returned as frames. If a visual reference is still unclear, call get_frame to drill into a specific moment (at) or spoken word/phrase (word). Returns up to 12 images. Required: element_id.
get_frame(at, word, source, element_id)- Drill into a recording for MORE visual detail: get the exact frame at a specific time (at) or when a specific word/phrase was spoken (word). Use when get_annotated_frames did not show what a reference ('this','here','that') means, or to see a moment the transcript mentions. Returns the asset frame at that moment (plus the active shared screen, if any) and a transcript snippet around it. Required: element_id.
permission_get(limit, offset, folder_id)- See who has access to a folder and their permission levels (full_access, comment, view, none). Returns team members with their roles, plus link and team-member default access levels. Required: folder_id.
recent_activity(limit, since, until, offset, folder_id)- Get the latest comments across your team, newest first. Returns a mix of text and recording comments with author, timestamp, and a link to jump into the conversation. Each item has a `type` field ("text" or "recording") plus the asset it belongs to and its version number, so you can read feedback across many videos in one call. Scope with folder_id to read one client's/project's feedback, narrow the window with since/until, and page with offset. For counts and trends use feedback_stats instead.
search(limit, query)- Search across your team's folders, assets, and feedback by text. Always returns all three categories together. Required: query.
tags(asset_id, folder_id)- List the team's tags and show the share of each tag (plus an 'untagged' bucket) across a scope. Scope defaults to the whole team; pass folder_id to narrow to one folder, or asset_id to narrow to one asset. Shares are count_with_tag / total_elements and do NOT sum to 100% because elements can carry multiple tags.
upload_file_complete(asset_id, version_of)- Finalize a local file upload started with upload_file_start. Call this only AFTER the curl PUT has finished successfully. Verifies the file landed in storage and starts video processing. Safe to retry. Required: asset_id.
upload_file_start(title, file_size, folder_id, version_of, content_type)- Start uploading a LOCAL video file from the user's machine into Flask. Returns the shareable Flask link immediately, plus a presigned upload URL. After calling this, upload the file bytes with the curl command from next_step, then call upload_file_complete. folder_id is OPTIONAL: omit it to upload to the team's top level (root). Max file size 5GB. Free to use for up to 100 MCP uploads; beyond that the user needs a plan at https://flask.do/plan. You still need edit access on the folder if one is given. Required: file_size.
upload_video(title, folder_id, video_url, version_of)- Upload a video from a public URL (a direct video file link or a Google Drive share link) into Flask. Flask downloads it, stores it, and starts processing. Returns the new asset_id — poll asset_status(asset_id) until status is "ready" before linking to it. folder_id is OPTIONAL: omit it to upload to the team's top level (root). Free to use for up to 100 MCP uploads; beyond that the user needs a plan at https://flask.do/plan. You still need edit access on the folder if one is given. For a LOCAL file on disk, use upload_file_start instead. Required: video_url.
wait_for_feedback(since, asset_id, timeout_seconds)- Wait for NEW feedback on an asset. Blocks up to timeout_seconds (default 45) and returns as soon as feedback newer than `since` arrives, or times out with an empty list. To listen continuously, call it again with the returned next_since. Use this after uploading a video for review instead of repeatedly calling feedback_list. Required: asset_id.
Last successful function declaration observed on . Source: https://api.flask.do/api/mcp/mcp. We list what the server declared; we do not call any of these functions.
Endpoint status observed on . Source: https://api.flask.do/api/mcp/mcp.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.1.1 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-08 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-08 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 17 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | api.flask.do | |
| mcp endpoint status | ok | The server listed 17 functions when asked. | as of probe | api.flask.do |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json