inkcheck MCP server

inkcheck is a quality-check tool for interactive fiction stories written in a format called ink. It compiles your story, walks through the choices a reader could make, and tells you where things break or where content can never be reached. It is handy for writers and small teams who want to catch problems before players do.

What this MCP server does

You ask your AI to check your ink story. The AI uses this helper to run inkcheck on your story file. inkcheck compiles the story with the official ink compiler, explores the choice paths within set limits, and looks for runtime errors, unreachable knots, and distinct endings. Then it hands back a report with exact paths you can follow to reproduce any problem it found.

Click to zoom

What you can do with it

• Compile your ink story and see if it builds without errors
• Explore choice branches to find runtime errors
• Spot knots or sections that no reader can ever reach
• List every distinct ending the story can produce
• Get exact step-by-step paths to reproduce a failure
• Run the same check again after you fix something
• Use a project config file so every check uses the same settings

Try asking your AI

• “Check my ink story for runtime errors and unreachable content”
• “Run inkcheck on story.ink and show me any broken paths”
• “What endings can a reader reach in my story?”
• “Use my inkcheck.yml settings and check the story again”

What it gives back to you

You get a structured report in the chat. It lists any compile errors, runtime errors with the exact choice path that triggers them, unreachable knots, and the distinct endings it found. If the search had to stop early because of limits, the report says so and explains why coverage was partial.

Before you start

Who it's for

Interactive fiction writers, narrative designers, and small game teams who write stories in ink and want a quick mechanical check before release.