beat-mcp-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BEAT_BRIDGE_DIR | Yes | The absolute path to the shared bridge folder used for communication between Claude and the Beat plugin. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| beat_pingA | Check whether Beat is running and reachable, and list its open documents. Call this first. |
| beat_list_documentsA | List every screenplay currently open in Beat, with the docIndex to use for other tools. |
| beat_get_textA | Get the complete Fountain text of a Beat document. |
| beat_set_textA | Replace the ENTIRE text of a Beat document with new Fountain text. Use this for full rewrites; prefer beat_replace_scene for targeted edits so you don't disturb the rest of the script. |
| beat_get_outlineA | Get the full outline of a Beat document: scene headings, sections and synopsis lines, in order, with the sceneIndex needed by beat_get_scene_text / beat_replace_scene. |
| beat_get_scenesA | Get just the scenes (no sections/synopses) of a Beat document, with sceneIndex, heading text, and position. |
| beat_get_scene_textA | Get the full text of a single scene by its sceneIndex (from beat_get_scenes). |
| beat_replace_sceneA | Replace a single scene's text in place (heading through the line before the next scene), identified by sceneIndex from beat_get_scenes. The rest of the script is untouched. |
| beat_insert_textB | Insert text at a specific character index in a Beat document (indexes come from beat_get_outline/beat_get_scenes). |
| beat_append_textA | Append text (e.g. a new scene) to the end of a Beat document. |
| beat_inspect_documentsA | Debug helper: dumps whatever fields the installed Beat version exposes on its document objects. Only needed if beat_list_documents titles/paths look wrong. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
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.
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.
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.
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.