chaoz23/inkcheck

Overview

CI for Ink stories, it runs compile checks, exhaustively playtests story branches, and detects dead content. It is available as both an MCP server and a CLI, and is built in TypeScript.

Best for

Best for
Ink story developers who want automated CI checks to keep branching narratives full, reachable, and error-free

Use cases

• Add compile and branch validation to an Ink story CI pipeline
• Find unreachable or dead story paths before release
• Automate story testing through the MCP server or CLI

Notes

CI for Ink stories, it runs compile checks, exhaustively playtests story branches, and detects dead content. It is available as both an MCP server and a CLI, and is built in TypeScript.

2 stars on GitHub. Last updated 2026-08-25. Licensed MIT.

Use cases

• Add compile and branch validation to an Ink story CI pipeline
• Find unreachable or dead story paths before release
• Automate story testing through the MCP server or CLI

Pros

• Combines compile checks, branch playtesting, and dead content detection in one tool
• Fits naturally into CI workflows
• Offers both CLI and MCP interfaces for flexible integration

Cons

• Exhaustive branch playtesting may become expensive for very large stories
• Small project with limited stars and community support

Indexed from awesome-mcp-servers-punkpeye and enriched against its public facts.