@mrfentmen/screenplaywriter-mcp

MCPcommunity
v1.0.3io.github.mrfentmenMITUpdated 3d agonpmGitHub

MCP server for reading, writing, and analyzing screenplays in Fountain format

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
60Downloads/wk
3d agoLast update
Package
Authorio.github.mrfentmen
LicenseMIT
Version1.0.3
Sourcenpm+mcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/20
→ Publisher: run `forge publish` from the package repo to claim ownership
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
—npm Trusted Publishing (Sigstore)+0/5
→ Publish from GitHub Actions with --provenance so the attestation binds this package to this repo
—npm maintainer match+0/5
→ Earned once your identity is verified above and that login is an npm maintainer of this package
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
Dependencies✓ 60 resolved+ · none vulnerable
Tool surface12 tools · 3 privileged
Security scan✓ Cleanv1.0.3 · todayHow well does this scan work?
EvalsNone
IndexedSep 23, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

12 tools · 3 privileged
Statically extracted from the published packagev1.0.3 · 11h ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

parse_screenplayParse a Fountain screenplay from text or file into a structured AST. This is the first step before any analysis or editing.

Parse a Fountain screenplay from text or file into a structured AST. This is the first step before any analysis or editing.

No input schema was published for this tool.

load_screenplay_fileLoad a Fountain screenplay from a file path on disk and parse it.

Load a Fountain screenplay from a file path on disk and parse it.

No input schema was published for this tool.

write_screenplayprivilegedWrite a new screenplay in Fountain format. The LLM should provide proper Fountain syntax. Saves to disk.

Write a new screenplay in Fountain format. The LLM should provide proper Fountain syntax. Saves to disk.

No input schema was published for this tool.

get_sceneGet a specific scene from a stored screenplay by number.

Get a specific scene from a stored screenplay by number.

No input schema was published for this tool.

edit_sceneprivilegedReplace a scene in a stored screenplay. Writes the modified screenplay to disk.

Replace a scene in a stored screenplay. Writes the modified screenplay to disk.

No input schema was published for this tool.

add_sceneAdd a new scene to a stored screenplay. Writes the modified screenplay to disk.

Add a new scene to a stored screenplay. Writes the modified screenplay to disk.

No input schema was published for this tool.

remove_sceneprivilegedRemove a scene from a stored screenplay.

Remove a scene from a stored screenplay.

No input schema was published for this tool.

character_reportGet detailed stats for all characters in a stored screenplay.

Get detailed stats for all characters in a stored screenplay.

No input schema was published for this tool.

scene_breakdownGet a production breakdown of all scenes: characters, action/dialogue lines, estimated pages.

Get a production breakdown of all scenes: characters, action/dialogue lines, estimated pages.

No input schema was published for this tool.

runtime_estimateEstimate the runtime of a stored screenplay based on page count (1 page ≈ 1 minute).

Estimate the runtime of a stored screenplay based on page count (1 page ≈ 1 minute).

No input schema was published for this tool.

export_fountainExport a stored screenplay back to Fountain format and save to disk.

Export a stored screenplay back to Fountain format and save to disk.

No input schema was published for this tool.

list_screenplaysList all currently loaded screenplays in memory.

List all currently loaded screenplays in memory.

No input schema was published for this tool.

12 of 12 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

MCP server for reading, writing, and analyzing screenplays in Fountain format

Keywords
mcpscreenplayfountainwritingfilmparser
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-24 — observed resolution, not a publisher declaration.

60 packages resolved · 2 direct · none carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the depth-4 limit. Anything below that level was never resolved.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+42 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.