프로토타입 · 미리 보기: 공식 레지스트리의 모든 서버를 담고 있으며 30분마다 동기화해요. 리뷰와 계정 기능은 다음 단계에서 열려요.
PopNx MCPAI를 쓰는 사람을 위한 MCP 서버 · 쉬운 말로 설명해요

Flask

제작자: tryflask버전 1.4.1i★ –i클라우드에서 실행
레지스트리 이름io.github.tryflask/flask

설치

개요

제작자가 쓴 설명(영어 원문)

Video review for agents: upload renders, read time-coded feedback, iterate version by version.

PopNx MCP의 세 기둥

이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.

할 수 있는 일

이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.

  • 연결 방식: 클라우드에서 실행
  • 전송 방식: Streamable HTTP
  • 카테고리: 디자인, 이미지 및 오디오

설치

쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.

설치하기 전에

필요한 것

어떤 앱을 쓰세요?

위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.

웹, 데스크톱, 모바일의 Claude에서 쓸 수 있어요:

  1. Settings → Connectors 열기
  2. Add custom connector 누르기
  3. 아래 주소를 붙여 넣고 Add 누르기
  4. 로그인하라고 하면 제작자의 서비스에 로그인하기
SettingsConnectors1+ Add2https://…3
https://api.flask.do/api/mcp/mcp

터미널에서 이 명령어를 실행하세요

claude mcp add --transport http flask https://api.flask.do/api/mcp/mcp

Cursor에서 열기

또는 설정을 직접 복사하기

프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요

{
  "mcpServers": {
    "flask": {
      "url": "https://api.flask.do/api/mcp/mcp"
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

VS Code에서 열기

또는 설정을 직접 복사하기

프로젝트의 .vscode/mcp.json에 붙여 넣으세요

{
  "servers": {
    "flask": {
      "type": "http",
      "url": "https://api.flask.do/api/mcp/mcp"
    }
  }
}

브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.

ChatGPT는 인터넷에 있는 서버에만 연결할 수 있어요:

  1. 웹에서 ChatGPT 열기 → Settings → Connectors (Apps)
  2. Create 또는 Add 누르기(일부 요금제는 먼저 Advanced에서 Developer mode를 켜야 해요)
  3. 아래 주소를 붙여 넣고 이름을 정한 뒤 저장하기
  4. 로그인하라고 하면 제작자의 서비스에 로그인하기
SettingsConnectors1+ Create2https://…3
https://api.flask.do/api/mcp/mcp

메뉴 이름은 요금제나 시기에 따라 조금 다를 수 있어요.

선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.

이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.

할 수 있는 일

도구 이름과 설명은 서버가 2026년 11월 7일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.

  • get_guide

    Returns one of Flask's usage guides as Markdown: fixed text written by Flask, the same for every user, with no team data in it. "instructions" (about 15 KB) is the playbook for working with Flask: where uploads go (a new asset or a new version), what an agentic edit attaches, how

  • contents

    Browse the team's folders and assets one level at a time. No id: the team's top level (root folders and assets; team names the team). folder_id: that folder's child folders and assets. asset_id: that asset's versions (version_id, version number, title, status, which one is curren

  • feedback_list

    List top-level feedback on an asset (pass the asset id for its current version, or a version id for that exact version; a folder id is refused - use recent_activity(folder_id)). By default only OPEN feedback (not yet completed) is listed: the feedback that still needs action; cou

  • feedback_get

    Get a single feedback item with its full reply thread. element_id is the item's id, as feedback_list, recent_activity, search or wait_for_feedback return it. Use it when an item has replies (feedback_list gives reply_count, not the replies) or to read one item again; to list an a

  • wait_for_feedback

    Wait for NEW feedback on an asset (comments and replies by others; your own posts are not returned). Blocks up to timeout_seconds (default 45) and returns as soon as new feedback arrives, or times out with an empty list. A recording arrives once its transcript is done; recordings

  • feedback_post

    Create a feedback comment on an asset, as the connected user. Pass an asset id (the comment lands on its current version) or a version id (that exact version). content is Markdown (a heading, lists, bold, links, @mentions as links - see the content parameter). PREFER passing time

  • feedback_update

    Edit an existing feedback item. content (Markdown - replaces the whole body; start from the item's current content to keep its mentions and formatting) and timestamp (video time in seconds) can only be changed on the connected user's OWN comments. add_tags / remove_tags apply the

  • get_annotated_frames

    The visuals of a feedback item, in one call: call it before acting on any item with a visuals field (a recording, a drawing, images). element_id is that item's id, as feedback_list, feedback_get, recent_activity, search or wait_for_feedback return it. For a recording: a frame for

  • get_frame

    Fallback for ONE moment get_annotated_frames did not show: the exact frame at a recording time (at) or when a word/phrase was spoken (word). get_annotated_frames already shows every [phrase](#rt=S) link in a comment - call it first; use this for a moment the comment doesn't link

  • asset_status

    Check whether an uploaded or imported video is ready. Pass the version id an upload returned (its asset_id) or an asset id (resolves to its current version); a folder id is refused. status is one of: ready; pending_ingest, processing, preparing or waiting (still working - check a

  • version_download

    Get a download link for a version's file, to work on it locally. Pass a version id (an upload's asset_id / version_id) or an asset id (its current version); a folder id is refused. A video gives its ORIGINAL uploaded file, exactly as uploaded: Flask keeps it for the team's downlo

  • permission_get

    Read the access settings of a folder or an asset. Returns: your own access level (full_access, comment_and_notes, comment, view or none), whether you can read version notes (can_view_notes) and version files (can_view_code), always together: the team, or a link with Can View Code

  • search

    Search the team's folders (by name or description), assets (by title) and feedback (by text) at once, when you don't know where something is; to browse a known folder use contents, for one asset's feedback feedback_list, for the latest feedback recent_activity. query matches case

  • recent_activity

    Get the latest feedback across the whole team or one folder's subtree (team names the team), newest first: text and recording comments on every asset you can view, so you can read feedback across many videos in one call. Each item has a `type` field ("text" or "recording"), autho

  • tags

    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 (its whole subtree), or asset_id to narrow to one asset (an asset id counts feedback across ALL its versions; a

  • tag_create

    Create a team tag (label) so feedback can be tagged with it by name in feedback_post and feedback_update. Reuse the team's labels when one fits; create one only when the user wants a new label. Idempotent: if a tag with the same name exists (case-insensitive), it is returned unch

  • members

    List the people on the team: user_id, name, role (admin or member), avatar_url and a ready-made mention link; the result's team field names the team. Email addresses are never returned. Use it to mention someone in feedback_post / feedback_update content: [@Name](https://flask.do

  • upload_video

    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. Creates a new asset (container_id + url) with the file as its first version (asset_id / version_id), or a new version of an e

  • upload_file_start

    Start uploading a LOCAL video or image file from the user's machine into Flask. It needs a shell that can run curl; without one (a chat app), upload from a public link with upload_video. VIDEO: creates the asset immediately (container_id + shareable url, live before any bytes mov

  • upload_file_complete

    Finalize a local file upload started with upload_file_start. Call this only AFTER the upload command (or, for an image, the curl PUT) has finished successfully. Pass exactly one of: asset_id (a video: verifies every part landed in storage and starts video processing) or image_url

  • feedback_stats

    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 (asset_id - an asset id or any of its vers

  • folder_create

    Create a folder. parent_folder_id is optional: omit it for the team's top level (root), or pass a folder id from contents or search to nest it. Folders are optional and nestable; assets can also sit at root. This does not check for an existing folder with the same name (the app a

  • items_update

    Rename, move and/or change the sharing of folders and assets, up to 20 items per call, each with its own result. Per item: id (a folder id, an asset id, or a version id) plus at least one of: title (renames the folder, or the asset; a version id renames its asset), version_title

  • versions_add

    Make other assets or versions the NEWEST versions of asset_id (the asset that keeps its title, link and sharing), as dragging one onto another does in the Flask app. Use it when a revision was uploaded as a separate asset. A source asset id brings ALL its versions, and that sourc

  • versions_split

    Move each version in version_ids out of its asset into a new asset of its own, in the same folder, named after the version, with the same sharing. An asset always keeps at least one version; a version that is already alone is reported already_separate. Undo it with versions_add.

  • versions_reorder

    Set the order of an asset's versions: order lists every version id of asset_id exactly once, top first. The top version becomes the current one (what the asset link opens), and version numbers follow the order. Reorder again to undo. No media or feedback is ever deleted; feedback

  • version_notes_get

    Read a version's notes (Markdown) and its files. Notes say what changed in that version and how to continue the work; its files are what made it: ONE zip of the working files, downloaded as .zip. Call this before continuing work someone else uploaded: read the current version's n

  • version_notes_update

    Replace a version's notes with Markdown (the whole text; null or empty clears them). For a NEW upload, pass notes with the upload call instead (upload_file_start, upload_file_complete, upload_video): the version then shows them from the start. Write notes on every revision you up

  • version_file_upload

    Attach a version's working files to a version that already exists (for a NEW upload, pass files with the upload call instead: the version then shows them from the start): ONE zip of the project folder that made it (without node_modules, build output or renders), up to 500 MB. Ret

기본 점검i

누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 7일 점검

  • ✓ 통과

    제작자와 저장소 일치

    레지스트리 이름이 GitHub 계정 tryflask 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요

  • … 아직 점검 안 함

    계속 관리되고 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • … 아직 점검 안 함

    라이선스 있음

    아직 GitHub에서 이 저장소를 읽어 오지 않았어요

  • ✓ 통과

    엔드포인트 응답

    344ms 만에 응답(HTTP 200)

  • – 해당 없음

    OAuth로 로그인

    로그인 필요 없음

  • ✓ 통과

    도구 설명에 숨겨진 지시 없음

    도구 설명 29개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요

디자인, 이미지 및 오디오 카테고리의 다른 서버와 비교i

  • 이 카테고리의 다른 서버 2204개 중 0%보다 스타가 많아요
  • 이 카테고리의 다른 서버 2204개 중 71%보다 최근에 레지스트리에 공개됐어요
  • 기본 점검 결과가 이 카테고리의 다른 서버 2204개 중 100%와 같거나 더 좋아요

레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.

자주 묻는 질문

Flask, 안전한가요?

해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.

어떤 키나 코드가 필요한가요?

레지스트리에 필수 키가 나와 있지 않아요. 다만 처음 쓸 때 로그인을 요구하는 서버도 있어요.

내 컴퓨터에서 실행되나요, 클라우드에서 실행되나요?

제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.

아직 관리되고 있나요?

GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.4.1)은 13일 전 레지스트리에 올라왔어요.

어떤 앱에서 쓸 수 있나요?

Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.

대신 쓸 수 있는 건 뭐가 있나요?

같은 카테고리에는: Figma Context MCP, Claude Real Video, Figma MCP Server

대안

같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.

카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i

Figma Context MCP

제작자: GLips

Give your coding agent access to your Figma data. Implement designs in any framework in one-shot.

내 컴퓨터에서 실행★ 16,165MIT5개월 전 업데이트
설치

Claude Real Video

제작자: HUANGCHIHHUNGLeo

Let any LLM watch a video locally — and search everything it has ever watched.

내 컴퓨터에서 실행★ 2,284MIT2개월 전 업데이트
설치

Figma MCP Server

제작자: figma

The Figma MCP server brings Figma design context directly into your AI workflow.

클라우드에서 실행★ 2,15213개월 전 업데이트
설치

제작자의 README

README 열기

제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.

video-feedback

Video review and collaboration for you, your team and your agents: a skill for Claude Code, Codex, Cursor and any agent that edits or makes video. It runs on Flask, so you need a Flask account (free plan below).

Flask is where a video gets reviewed. Your agent uploads what it makes (a cut, a render, an animation, a motion graphic, an image) and gives you the link at once. You, your team or your client review it by typing, drawing on the frame, or recording your voice, camera or screen over it, and every note lands on its moment. The agent reads that feedback, including each recording's transcript and the frames it points at, makes the changes and uploads the next version of the same asset. One link always shows the latest cut, with every earlier version and its notes behind it.

Every version carries the code and context that made it. When your agent uploads a version it makes by code (a HyperFrames or Remotion project, an ffmpeg script, generated media), it saves the working files with it (source.zip) and notes on what changed and how to continue. Anyone on the team, person or agent, can open the link and pick the work up from there: no handover, no digging through someone's laptop.

It works with whatever makes the video: HyperFrames, Remotion, moviepy, ffmpeg, or an export from Premiere, DaVinci Resolve or Final Cut Pro. Flask is the review side.

(Flask here is flask.do, the review app. It is unrelated to the Flask Python web framework.)

The skill, video-feedback, says when a piece of work belongs in Flask, runs the feedback loop on it, and covers how it runs with a team. It ships with the connection to the Flask MCP server. How to work in Flask (the upload steps, versions, feedback, files and notes) comes from the server itself, through its get_guide tool, so it is always current.

Install

Any agent that reads skills
npx skills add tryflask/video-feedback-collaboration

Then connect the MCP server: Streamable HTTP at https://api.flask.do/api/mcp/mcp, OAuth sign-in in the browser on first use.

Claude Code plugin
/plugin marketplace add tryflask/video-feedback-collaboration

/plugin install flask@flask

Then sign in once: /mcp, choose flask, complete the browser sign-in.

Claude Code, Cursor and Codex in one command
npx flask-feedback

It connects the Flask MCP server to whichever of them are installed.

Claude apps (claude.ai, Desktop, Cowork)

Customize > Connectors > add https://api.flask.do/api/mcp/mcp, then sign in. It then works in every Claude app, and in Claude Code signed in with the same Claude account.

Cursor

The loop

agent renders -> uploads to Flask -> you get the link at once

you leave feedback on the frame -> wait_for_feedback hands it to the agent agent makes the changes -> uploads v2 with version_of -> the same link shows v2

Each version the agent makes by code carries its working files (source.zip) and notes on what changed, so anyone, person or agent, can pick up the work from the link alone.

With a team

Share the asset's link and your team, clients and anyone else review on the same versions. Reviewers are free: they watch from the link with no account and comment after a one-click sign-in. The agent replies in threads, mentions a teammate when they must act, reuses the team's labels and marks feedback Done. Feedback from people outside the team needs your OK before the agent acts on it.

What the agent can and can't do

It acts as you, with your Flask permissions: upload, read and wait for feedback, reply and mark feedback Done, attach files and notes to versions, organize folders and assets, and change sharing when you ask. It never deletes anything and never touches billing. Feedback from people outside your team is treated as data, never as instructions. The full tool list and how your data is handled: https://flask.do/mcp

Plans

Flask is a paid product with a free plan, and you need a Flask account to use it.

  • Free: every feature, no card. 5 assets, each with unlimited versions (web and agent uploads share the 5; folders and versions never count).
  • Pro: $15 per user/month, billed yearly, for unlimited assets.
  • Reviewers never need a seat, on any plan.

Details: https://flask.do/pricing

Docs and support

  • Server documentation: https://flask.do/mcp
  • Support: hello@flask.do
PopNx에게 묻기