Branchwright MCP
Related Servers
Alternatives to Branchwright MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides a persistent, branching store for fictional scenes — stories, character assignments, turns and editable summaries — exposed as ten validated, revision-checked MCP tools. Supports optimistic concurrency, idempotent turn appends, canon rules and story export over a bearer-token-authorized HTTP boundary that fails closed.MIT
- AlicenseNot gradedqualityDmaintenanceEnables LLM-driven text game state management by exposing MCP tools for managing players, locations, items, entities, and abstract concepts.MIT
- AlicenseNot gradedqualityCmaintenanceA locally-run MCP server that connects to Twine's story library, enabling AI-assisted story management, passage editing, link-graph analysis, and narrative intelligence from any MCP-compatible client.32 npm5MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI-driven long-form novel creation and management, including chapter generation, character and timeline tracking, semantic memory retrieval, version savepoints, and deep consistency checking across multiple projects through MCP tools, with support for local LM Studio or any OpenAI-compatible API.15MIT
- FlicenseBqualityDmaintenanceAn MCP server that provides 18 tools for dice rolling, luck tests, character management, world state, combat, and save/load, enabling an AI game master to run a solo-play gamebook entirely through deterministic game logic.181-
- AlicenseNot gradedqualityBmaintenanceEnables AI narrators to maintain persistent world state for interactive fiction and tabletop play by managing entities, relationships, dice rolls, threads, clocks, and continuity checks.MIT
TDQS
Scored across 17 tools
Each tool targets a clearly distinct phase or resource: canon ingestion/search/read, branch creation/listing, state/knowledge/history retrieval, and the turn lifecycle (prepare, roll, commit, recover). The descriptions explicitly separate potentially overlapping tools like prepare_turn, commit_turn, and get_recovery, so an agent can select correctly.
All 17 tool names use snake_case and follow a predictable verb_noun pattern (read_guide, prepare_turn, list_campaigns, create_branch, get_state, commit_turn, restore_checkpoint). There are no mixed conventions or vague standalone verbs.
The set has 17 tools, slightly above the typical 3–15 range, but the domain is a complex stateful RPG workflow with distinct campaign, canon, branch, turn, and recovery operations. Each tool appears to earn its place, though some consolidation might be possible.
The surface covers core lifecycle operations: campaign creation/listing, canon ingestion/search/read, branch creation/listing, turn preparation/rolling/commit, state/knowledge/history reads, world preview, and recovery. Minor gaps exist around explicit checkpoint creation, campaign/branch update or deletion, and actor management, but the main workflows are supported.