Skip to main content
Glama
tholtman1-del

beat-mcp-bridge

by tholtman1-del
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to beat-mcp-bridge

No user-submitted related servers found.

    Related Servers

    • writebetter

      badalyansven
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects Claude Desktop to a local WriteBetter macOS app for managing commands, prompts, context folders, run history, and usage stats entirely on the user's machine.
      MIT

    • drive-update-mcp

      drboden
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables Claude to update existing Google Drive files in place via a service account, preserving file ID, link, and revision history. Supports finding, creating, listing revisions, and updating files through a Streamable HTTP MCP server.
      -

    • Obsidian MCP Ultimate

      YakshithK
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Desktop to directly access and manage Obsidian vault files, supporting reading, writing, patching, searching, and file operations without requiring Obsidian to be open.
      3,358 npm
      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

    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

    ActivityMaintained
    ResponsivenessNo issues

    Resources