Skip to main content
Glama
beat-mcp-bridge

beat-mcp-bridge

Related Servers

Alternatives to beat-mcp-bridge

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude to read, edit, and generate real Final Cut Pro timelines from exported FCPXML, covering cut detection, silence removal, markers from transcripts and beats, role assignment, rough cuts, keyframes and speed ramps, cross-NLE export, and pushes straight into a running Final Cut Pro. Every write is journaled with its SHA-256 and can be undone, so edits stay non-destructive and reviewable.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude to read, edit, and generate real Final Cut Pro timelines from exported FCPXML — trimming and splitting clips, removing silence, placing markers from transcripts or beats, assigning roles, building rough cuts, and inspecting timeline health. Writes are journaled and reversible, and finished edits can be exported to other NLEs or pushed directly into a running Final Cut Pro.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude to read, edit, and generate real Final Cut Pro timelines from exported FCPXML, covering cut detection, trims, splits, silence removal, markers, roles, transcript-based edits, keyframes and speed ramps, plus live pushes into a running Final Cut Pro. Every write is journaled, undoable, and guarded by SHA-256 checks so edits can be reviewed and delivered safely.
      -
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables Claude to read, edit, and generate real Final Cut Pro timelines from exported FCPXML, including cut detection, marker placement, role assignment, silence removal, transcript- and beat-based editing, rough cuts, keyframes, speed ramps, and cross-NLE export. Every write is journaled with its SHA-256 and can be undone, and edits can be pushed directly into a running Final Cut Pro without a manual re-import.
      -

    TDQS

    A3.9/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: read vs write, whole-document vs single-scene. The overlap between beat_get_outline and beat_get_scenes (both return sceneIndex) is real but descriptions clarify the difference (outline includes sections/synopses). beat_ping and beat_list_documents both list open documents, but ping is framed as an initial health check.

    Naming Consistency4/5

    The beat_ prefix is applied uniformly and the verb_noun pattern dominates (replace_scene, insert_text, get_outline, set_text). Minor deviations: beat_ping lacks a noun, and the get_/list_ mix for retrieval is slightly inconsistent but follows a conventional distinction.

    Tool Count5/5

    11 tools is well-scoped for a screenplay bridge: 6 read/inspection tools and 5 write/edit tools cover the domain without redundancy or bloat. Each tool earns its place for the stated purpose of interacting with Beat documents.

    Completeness4/5

    The surface covers the full text lifecycle: read (full, outline, scenes, single scene) and write (full replace, scene replace, insert, append). Notable gaps are the lack of an explicit scene deletion tool (workable via replace with empty text) and no document lifecycle operations, but these appear outside the bridge's scope.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues