Skip to main content
Glama

Server Details

Verification videos for AI coding agents: upload recordings over MCP and share viewer links. Keep work moving in parallel and review results asynchronously, when you're ready, from your laptop or phone. Add video evidence to pull requests so teammates can see how your changes work during code review.

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-11-25
URL
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 7 tools

Disambiguation4/5

The lifecycle tools (create_video_upload → complete_video_upload → get_video_link → delete_video) are clearly distinct steps with explicit ordering constraints. The main overlap is between list_videos/search_videos and list_tasks/search_videos, but the descriptions explicitly spell out the difference (exhaustive listing vs semantic search, and search_videos' differing default scope for `mine`), so misselection is unlikely.

Naming Consistency5/5

All seven tools use consistent snake_case verb_noun form (create_video_upload, complete_video_upload, delete_video, get_video_link, list_tasks, list_videos, search_videos). The verb set (create/complete/delete/get/list/search) maps predictably onto the nouns, with no style mixing.

Tool Count5/5

Seven tools is well-scoped for a video-recording service: an upload lifecycle, retrieval (link, list, search) and one supporting vocabulary helper. Each tool earns its place and none appears redundant with another.

Completeness4/5

Coverage spans the full lifecycle: create upload, complete it, list/search recordings, fetch a public link, and delete. Minor gaps remain — there is no update tool to amend a recording's task/title/context metadata, and no explicit status/health check beyond re-listing, but agents can work around both.

Publisher details

Operator
Kirill Kolomin
Operator website
https://showitworks.app
Vendor relationship
First-party
Privacy policy
Not provided
Trust center
Not available
Restrictions
Requires a Show It Works account and a project API key created in Settings. Tool calls require Bearer authentication; initialize and tools/list are public. Recordings and public viewer links expire according to the project's retention policy.

Available Tools

7 tools
complete_video_uploadAInspect

Publish a pending recording after its direct upload finishes. Call only after create_video_upload and a successful PUT of the entire file to the returned upload URL; this tool does not upload bytes. Requires a project API key with video.upload permission. Checks the stored object's byte size, MIME type and MP4/WebM container signature, not the correctness of the work shown or the full media contents. On success, changes PENDING to READY and returns the recording; use get_video_link next to retrieve its public viewer link and report retainUntil. Anyone with that link can watch until retainUntil; delete_video can remove the recording earlier. A size, MIME type or container-signature mismatch refuses publication and initiates deletion of the uploaded object. Failure to inspect the stored object's metadata marks the recording FAILED. For either failure, create a new upload and upload the file again rather than retrying completion on that recording. Only PENDING recordings can be completed: calling again after success returns an error, so use get_video_link instead.

Inputs: videoId (required).

create_video_uploadAInspect

Write title, taskName, ownerContext and publicContext in English (code en, locale en-US) — this project's language — and follow that locale for dates and numbers. The answer says so when what you sent is not in it. Leave code, identifiers, commands and file paths exactly as they appear in the repository, and leave worktreeName as the checkout's own directory name rather than translating it. This creates a direct R2 upload for an MP4 or WebM recording, filed under the project this API key belongs to. Worktree and task are public; ownerContext is shown to project members only, never through the public link; publicContext is shown only when explicitly supplied as public-safe. This project is currently closed to new recordings: create_video_upload will be refused until an owner turns uploads back on in the project's settings. Do not record a session to upload here — ask the person you are working with first.

Inputs: title (required), byteSize (required), filename (required), mimeType (required), +5 more.

delete_videoAInspect

Permanently delete a recording.

Inputs: videoId (required).

list_tasksAInspect

List the task names already used in this API key's project, so you can reuse an existing one instead of inventing a near-duplicate. Copy taskName verbatim into create_video_upload. Names are folded case-insensitively and on whitespace, so one entry can cover several spellings, listed as variants. recordingCount is how many recordings carry the task right now, and untagged counts the recordings filed under no task at all. A name is listed while at least one of its recordings is still inside its retention window — 14 to 60 days after upload depending on the project's plan — and once the last of them reaches that deadline the name goes from this list with it. firstUsedAt/lastUsedAt are upload times. Only your own uploads are counted by default; pass mine: false to count every project member's. Without query, entries come back most-recently-used first, truncated means more names exist than limit returned, and totalTasks says how many. Other optional filters: taskName (substring), createdAfter/createdBefore (ISO timestamps), limit. A filter narrows the recordings that are counted, so the counts and dates then describe that window rather than the project's whole history. Optional query instead returns the tasks of the recordings that best match a description of the work, ordered by match quality — only the best-matching recordings nominate a task, so that answer is a shortlist rather than the project's whole vocabulary, totalTasks and truncated describe just those tasks, and untagged is omitted. The counts and dates of a task shown that way still cover every one of its recordings, not only the matching ones. query matches by meaning in any language, and a query in English (code en, locale en-US) — this project's language — also matches on wording.

Inputs: mine, limit, query, taskName, +2 more.

list_videosAInspect

List the recordings in this API key's project, including dashboard reviewer comments and viewed status. Expired recordings are omitted; each row's retainUntil is when that recording and its public link are deleted, and firstViewedAt is when someone first played the public link, or null if nobody has. Ignore expiresAt, which is upload-authorization plumbing and always reads as past on a published recording.

Inputs: no named parameters.

search_videosAInspect

Find recordings in this API key's project by meaning as well as by wording — describe what the session was about, or name a task, and the closest recordings come back ranked. Use it before inventing a new TASK value, to find the recordings an earlier session already filed under one. Optional filters: taskName (substring), mine (only your own uploads — unlike list_tasks, this one searches every project member's recordings unless you pass it), createdAfter/createdBefore (ISO timestamps) and limit. Expired recordings are never returned. A query in any language works, because matching is semantic; this project works in English (code en, locale en-US), and a query in that language also matches on wording, which is the more precise half.

Inputs: query (required), mine, limit, taskName, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      A shared task board exposed over MCP that lets a team's mixed AI coding agents (Claude Code, Codex, Copilot, Gemini CLI, Cursor) claim tasks, build each one on its own git branch, review and merge pull requests, and coordinate through board activity and locks. Humans watch and steer the same board from a web page, answering questions, approving tasks and choosing who merges.
      1
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources