Skip to main content
Glama
girishkvs

rostrum

by girishkvs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to rostrum

No user-submitted related servers found.

    Related Servers

    • LosslessCut MCP

      dcavalcante
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to inspect media and project files, create reviewable v2 projects, and perform verified native exports of selected segments as separate files through a private editor instance. It provides a small, safety-checked workflow that verifies output paths, streams, and durations with FFprobe.
      MIT

    • cutroom

      0xpratzyy
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to edit talking-head videos locally by transcribing footage, applying validated edit operations like cutting fillers and silences, adding zooms, captions, looks and branding, and checking results with rendered previews. Agents can also read pinned editor feedback notes with annotated frames, resolve them, and export MP4, SRT or OTIO while the user watches changes live.
      1
      MIT

    • video-agent-mcp

      YansIlinta
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to run project-scoped video editing workflows: propose and approve editing strategies, apply validated plans, review immutable versions, and export final renders via FFmpeg, with durable persistence and approval gates.
      1
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools map to distinct pipeline stages: analyze, decide, render, verify, and map_time are clearly separate. The main ambiguity is between job_status and status, and to a lesser extent plan/list_cuts, though their descriptions clarify the intended use.

    Naming Consistency3/5

    Names are readable and all use snake_case, but they mix bare verbs (analyze, plan, decide, render, verify), verb_noun patterns (list_cuts, import_decisions, map_time), and noun-style names (job_status, status, doctor). This is a mixed convention rather than a predictable pattern.

    Tool Count5/5

    Eleven tools is well within a reasonable range for a video-analysis and rendering workflow. Each tool corresponds to a meaningful pipeline step rather than feeling redundant or padded.

    Completeness4/5

    The surface covers the core lifecycle: analysis, project status, cut inspection, decisions, rendering, verification, time mapping, and environment diagnostics. Minor gaps exist around project/talk management, such as listing or deleting projects, but core workflows are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources