Prose
A local novel-writing engine: SQL Server canon for whole fictional universes, a desktop Writer, and a CLI and MCP server so Claude can draft, read and repair books against that canon.
Power your agent
การติดตั้งจากผู้เผยแพร่ ไม่ใช่เอนด์พอยต์ของ PlugMCP
URL แบบรีโมตหรือคำสั่งบนเครื่องของคุณ? การติดตั้งสองแบบต่างกันอย่างไร
รันบน PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
เปิดจากผู้เผยแพร่
A local novel-writing engine: SQL Server canon for whole fictional universes, a desktop Writer, and a CLI and MCP server so Claude can draft, read and repair books against that canon.
A local novel-writing engine: SQL Server canon for whole fictional universes, a desktop Writer, and a CLI and MCP server so Claude can draft, read and repair books against that canon.

Prose runs on your own machine. There is no hosted version: the hosted deployment was retired on 2026-08-23 and the project is local-only by design.
Prose.Hub is an ASP.NET Core process bound to 127.0.0.1:5900. It is the only process that touches the database. It hosts the engine's services, the Writer pages and an observability dashboard. The CLI and the MCP server are thin clients that forward every call to it and refuse to start when it is not healthy.
Writer.exe is a WPF + WebView2 window that finds or starts the Hub and opens its /writer page. The editor itself (Prose.WriterUi) is compiled into the Hub, with a book editor, a reader view (/read) and a canon browser (/repo). Launcher.exe is a small picker that opens the Writer or the KDP publishing app, starting the Hub first when needed.
Prose.ObserverUi is served by the Hub at /app: dashboard, beats, logs, a 2D and 3D graph view, Dynamic Context Memory runs and the canon repositories, pushed live over SignalR.
The current way of working (RFC 0015, approved 2026-09-23). Every book moves through computed stations: planned, written, captured, read, clean, verified, pressed. Work is driven by work orders, decisions are recorded as rulings, and each Claude session is a row in the database. No LLM judges, votes or scores. See The Novel Factory below.
Every canon row belongs to exactly one universe. Books are a tree of nodes (series, book, chapter) over beats, the atomic unit of story. Beats and nodes are system-versioned, so every edit can be rewound. Entities carry embeddings, typed relationship edges with story-time validity windows, and an append-only state ledger.
--splice-beats).--read-beats), with read receipts and read notes.ProseWriterRouter) for drafting beats from canon.--export-node renders a book to .docx, EPUB, PDF and plain text with metadata files. Audiobook export renders a whole book through ElevenLabs. A separate WPF app, Prose.KdpPublish, drives the Amazon KDP site to publish and republish books.
293 tools in 53 families, surfaced to any MCP client as mcp__prose__<name>. Claude can read and write beats, entities, rulings and work orders through the same Hub the CLI uses.
Prerequisites:
(localdb)\MSSQLLocalDB, database Prose).Clone, wire up the git hooks and build:
git clone https://github.com/mindattic/Prose.git
cd Prose
git config core.hooksPath .githooks
dotnet build src\Prose.slnx
Without the core.hooksPath line the repo's pre-commit, commit-msg and post-commit hooks silently never run. post-commit mirrors every Markdown file into the MarkdownFiles table; commit-msg runs the shared MindAttic commit-message check.
Publish and start the Hub. It applies any pending EF Core migrations at startup, then waits for /api/health:
powershell -ExecutionPolicy Bypass -File run.ps1 -Apps Hub -Start Hub
Enable temporal versioning on a fresh database and check the CLI can reach the Hub:
.\prose.cmd --migrate-sql --schema
.\prose.cmd agent bootstrap
.\prose.cmd --list-books --universe glmz
agent bootstrap prints ready when the Hub is healthy. Open the editor:
powershell -ExecutionPolicy Bypass -File run.ps1 -Apps Writer -Start Writer
Register the MCP server with Claude Code (one time):
claude mcp add prose dotnet run --project <path-to-your-clone>/src/Prose.Mcp/Prose.Mcp.csproj --no-build --configuration Release
Build src/Prose.Mcp in Release first. The tools appear as mcp__prose__*. For Claude Desktop, see src/Prose.Mcp/README.md.
prose.cmd / Prose.Cli ----POST /api/cli-invoke----+
Prose.Mcp (stdio MCP) ----POST /api/mcp-invoke----+
Prose.Writer.exe (WebView2) ----GET /writer-------+--> Prose.Hub (Hub.exe, 127.0.0.1:5900) --> SQL Server
Prose.Launcher.exe ----starts the Hub if down-----+ hosts the Prose.Core services,
Prose.WriterUi (/writer, /read, /repo)
and Prose.ObserverUi (/app)
HubGate.EnsureReachableOrExit, no in-process fallback). The CLI forwards a handler class name plus its arguments; the Hub's CliDispatch runs the handler from Prose.Cli. MCP tools forward through HubInvoker to /api/mcp-invoke, where ToolDispatch runs the tool's body.Prose.Writer has no Prose.Core reference. All editor code lives in Prose.WriterUi, compiled into the Hub, so an editor change needs a Hub redeploy./api/health returns 503 when SQL Server is unreachable. Protected endpoints take an X-Prose-Key header that the CLI and MCP server read from Settings.json.--universe <slug> or set PROSE_UNIVERSE. A content command with no universe is refused rather than defaulted.Hub HTTP endpoints include /api/health, /api/cli-invoke, /api/mcp-invoke, /api/factory/*, /api/universes/*, /api/outbox/{consumer}, /api/generate-scene and /api/agent/bootstrap, plus SignalR at /hubs/observability.
engine_data/*.json is a seed and export mirror, not canon.Beats, Nodes and other canon tables are system-versioned, so every edit is rewindable with FOR SYSTEM_TIME ALL.EntityStateEvents ledger.SeriesNode, BookNode and ChapterNode on one Nodes table, linked by ParentNodeId.IUniverseContext, not by convention. An entity needed in two universes gets two rows.sqlcmd, not even a read-only lookup.RFC 0015 replaced loose plans and memory with state in the Hub. The agent protocol is docs/agent/PROSE_PROTOCOL.md; the design is docs/rfc/0015-novel-factory.md.
WO:<id>).The read gate marks a beat unread when its text changes, when it moves, or when an entity it mentions changes. factory_next walks chapters in reading order and returns the first actionable station.
prose --factory next --universe glmz
prose --factory status --node <book> --universe glmz
prose --order list
prose --read-beats --slug <book> --from 1 --to 40 --universe glmz
prose --read-status --node <book> --list --universe glmz
prose --splice-beats --node <book> --file docket.json --universe glmz # dry run
prose --splice-beats --node <book> --file docket.json --apply --universe glmz # apply
prose --export-node --slug <book> --universe glmz
The first book through the full line was Bushido Coda: one in-order read of all 521 beats, one entity batch, a re-read of every beat the gate flagged, verification of 114 tagged entities, then the press (V73, 2026-09-23).
Since RFC 0009 (2026-09-06) no service rewrites finished prose on its own. Writing happens in session, with the full prior prose and the cast's records in view (factory_context), and every change goes through the one prose door (NodeWorkbenchService and BeatSpliceService).
ProseWriterRouter remains the single entry point for generating a beat from canon (--expand-beat, --generate-scene). It assembles a wide context before calling the model. Its current inputs, from its constructor:
CombatSceneWriter.WriteCombatSceneAsync handles multi-exchange combat set pieces (loadouts, ammunition, bio-battery). BeatGeneratorService is the lower layer and is not called directly from new code.
Route generation to any OpenAI-compatible endpoint, such as Ollama on a rented GPU, without editing configuration. The overrides are per command:
prose --expand-beat --slug <slug> --universe glmz `
--local-url https://<pod-id>-11434.proxy.runpod.net/v1/chat/completions `
--local-model qwen2.5-32b-writer
Flags: --local (use the stored LocalLlmBaseUrl), --local-url, --local-model, --local-key.
There are no 0 to 100 score gates, and persona vote panels are off by default (bible law SS-LAW-17). A named, fixable finding tells you more than a number.
On 2026-09-22 RFC 0014 measured every instrument by its findings: 30,745 filed, all time, and 8 ever applied. Three producers earned those 8, and they stay live:
Thirty commands were switched off, among them the reader panels, the craft checklist, the continuity and contradiction finders, the obligation ledger, the scanners and the nightly AutoCorrect battery. Nothing was deleted: each handler is intact, the CLI explains why when you call one, and deleting its line from src/Prose.Cli/DeactivatedInstruments.cs brings it back. --findings (including --findings stats --by-instrument) and --publish-readiness stay live, because they are how an instrument earns its way back.
Codified from docs/LOGIC.md. One model call per dimension over the book's enabled beats:
Findings are triaged BLOCKER, MODERATE or MINOR. Exit code 0 is clean, 1 is moderate or minor only, 2 is any blocker.
prose --logic-sweep --slug <slug> --universe glmz
prose --logic-sweep --slug <slug> --until-dry --required-dry 2 --max-rounds 8 --universe glmz
--until-dry runs one convergence round per call. State lives in NodeConvergenceStates, keyed to a fingerprint over every enabled beat's text, so an unchanged book skips the round at no cost and any edit resets the dry-round count. Hitting the round cap files a not-converging finding instead of looping forever.
Every beat save also triggers a narrow sweep of its blast radius: the edited beat, its neighbours within three positions, and every beat elsewhere in the book that mentions the same entity (BlastRadiusService).
The fact ledger (ContinuityClaims) holds (entity, predicate, object) claims extracted from prose. --ledger-adjudicate judges same-predicate contradiction groups against the prose they came from. It writes claim status only, never prose, and is cost-gated: one model call per uncached group, cached on the claim ids and every anchor beat's text hash. Numeric predicates such as age or tenure_years compare as numbers, so "fifty" and "50" are one claim. Its best catch: Kyle's residence given as "eleven years" in one place and "four years" in another, the spine of Bushido Coda.
--check-text-integrity [--fix] [--json] scans every beat and every book bible across all universes for two corruption signatures: U+FFFD, and stray control characters below 32 other than tab, line feed and carriage return. --fix repairs only three unambiguous patterns (U+FFFD before a digit becomes the currency symbol Φ; a control character between two spaces becomes an em dash; one before a digit becomes §). Everything else is reported for a human. The scan compares characters in C#, never with SQL CHARINDEX, which returned false negatives for U+FFFD under this database's collation.
UniverseGraphService builds an in-memory graph over every entity in the active universe. It is a projection rebuilt from SQL, never the store of record; the JSON snapshots under engine/data/graph/ are an output cache written by --rebuild-graph.
--graph-health --universe <slug> [--used-in-prose-only] reports orphaned nodes, weakly connected nodes and suspicious names, at no model cost. Most orphans are deliberate flavour (guns, drugs and minor characters seeded for depth). --used-in-prose-only keeps only entities that actually appear in prose: on GLMZ (2026-08-15) that cut 789 orphans and 8,660 weak links down to about 206 entities that really needed edges.
Relationships that are only true for part of a story are Edges rows with StoryValidFrom and StoryValidUntil. --world-state --beat <id> [--story-time <date>] shows what is true at that point; the reference example is Kyle's motorcycle, owned until its destruction and owned again when the rebuilt Mk. 2 is revealed.
prose.cmd at the repo root runs dotnet run --project src/Prose.Cli -- <args>. Most commands need a universe: --universe <slug> or PROSE_UNIVERSE.
The full, generated reference is docs/CLI_COMMANDS.md: 290 commands, 30 deactivated, 10 cost-gated. Regenerate it with prose --export-commands, which runs without a Hub. The tables below are a guide to the commands you will use most.
Cost-gated commands spend model money and route through the Hub's cost gate; everything else is deterministic or read-only.
Prose.Mcp exposes 293 [McpServerTool] methods in 53 families. The generated reference, with parameters and descriptions, is docs/MCP_TOOLS.md. Regenerate it with:
dotnet run --project src/Prose.Mcp -- --export-tools docs/MCP_TOOLS.md
The server is a Hub client: each tool forwards to /api/mcp-invoke with the caller's universe and the Hub key. Many tools write (beat text, entity fields, rulings, work orders). Factory tools include factory_next, factory_context, read_beats, splice_beats, record_ruling, work_order_add and verify_entity_begin. Cross-universe lookups (get_universe_entity, search_universe) do not switch the session's universe; switch_universe does.
Agent hosts other than Claude use the same protocol. prose agent bootstrap --json is the CLI fallback; AGENTS.md and docs/agent/PROSE_PROTOCOL.md are the entry points.
Server=(localdb)\MSSQLLocalDB;Database=Prose;Trusted_Connection=True;TrustServerCertificate=True;
Windows authentication. The connection string resolves from the ConnectionStrings__Prose environment variable, then appsettings.json (ConnectionStrings:Prose), then the LocalDB default. The Hub applies pending EF Core migrations at startup and refuses to start if one fails.
The schema reference, docs/schema.md, is generated by tools/gen-schema.ps1 and is not committed (it is in .gitignore). Key tables:
Raw T-SQL under src/Prose.Core/Data/Sql/ is mostly historical. If a fresh database lacks rows from one of those scripts, register it in SqlSeedService.Seeds and run it with prose --seed <name>; never apply it by hand.
Every canon and story row belongs to exactly one universe (bible law SS-LAW-15). Each has a folder under docs/universes holding its generated glossary.


Scoping fails closed: an unset or unknown universe blocks the command instead of defaulting, the fix for an earlier cross-universe content leak. Two terminals or sessions can target different universes at once.
Prose is also a store other MindAttic apps read and write (RFC 0007). The contract is one JSON file per universe, <app>/universe/<slug>.universe.json, described by docs/schemas/universe.schema.json: a universe header plus entities with type, summary, details, relations and tags.
UniverseInterchangeService maps entities onto the entity spine. Import is an idempotent upsert by universe and slug; a relation to an unknown entity creates a stub that is promoted when its own row arrives.--universe-import <path>, --universe-export <slug> <path>, --universe-sync <path>.import_universe_file, export_universe_file, get_universe_entity, search_universe.POST /api/universes/{slug}/import plus reads of entities, neighbours, search, snapshot and stats.GET and POST /api/outbox/{consumer} queue one-line messages for another app's Claude session; ?peek=true reads without marking delivered.generate_scene, prose --generate-scene or POST /api/generate-scene writes a scene or a line of dialogue without a book row, with canon grounding intact.--barks-export <universe> <path> emits every single-speaker beat as {barkId, speakerEntitySlug, text, context}.The first consumer is ExperimentEve. The runbook for the next one is docs/CONSUMER_ONBOARDING.md.
LlmRouter is the fallback chain: it tries the active provider (claude by default), then walks ActiveLlmProviderChain in order. Any exception on a hop moves to the next. Every hop is logged to LlmCallHistories.
prose-llm works even when Core or the database does not:
prose-llm --provider <id> --prompt <text-or-@file-or-dash> [--system <text>] [--temperature <n>] [--max-tokens <n>] [--model <id>] [--json]
API keys resolve through SettingsService.ResolveApiKey: Vault configuration, then Prose's own app-scoped key, then a PROSE_* environment variable, then the shared MindAttic credential store under %APPDATA%/MindAttic/LLM/, then a legacy Settings.json field. There is no CLI or MCP command to switch the active provider; edit ActiveLlmProviderChain. docs/PROVIDERS.md lists which services depend on which provider.
All environment variables are optional; set only what a feature you use needs.
Run the Hub with ASPNETCORE_ENVIRONMENT=Development, or MindAttic authentication fails closed (only --reset-password is affected). MindAttic.Authentication (6.0.0) sends its own security alerts (for example when --reset-password sets a new password) over SMTP from the Vault Notifications bucket (MindAttic:Vault:Notifications:email, loaded by the Hub), not the PROSE_SMTP_* settings; without it the Hub logs a startup warning that auth email will not be delivered. Prose has no web sign-in, so there is no self-service reset page and no PublicBaseUrl.
Prose/
prose.cmd the CLI shim (dotnet run on src/Prose.Cli)
run.ps1 publishes Hub, Writer, Launcher to C:\Apps\MindAttic\Prose\ (writes run.bat there)
writer.bat dev-only: dotnet run of Prose.Writer
src/
Prose.slnx
Prose.Core/ engine: EF Core context and entities, services, Services/Factory/
Prose.Hub/ Hub.exe: minimal-API endpoints, SignalR, dispatch to CLI and MCP code
Prose.Hub.Contracts/ DTOs shared by the Hub and its UI clients
Prose.Cli/ the prose command; Cli/ holds about 300 handler classes
Prose.Mcp/ stdio MCP server; Tools*.cs, one class per area
Prose.WriterUi/ the editor (Razor class library hosted by the Hub)
Prose.ObserverUi/ the observability dashboard at /app
Prose.Writer/ Writer.exe, the WPF + WebView2 window
Prose.Launcher/ Launcher.exe, opens Writer or KdpPublish
Prose.LlmCli/ prose-llm, the standalone provider CLI
Prose.UnitTests/ NUnit tests with SQLite fixtures
tools/ launch-app.ps1, install-shortcuts.ps1
docs/ the Codex: USER_STORIES.md, rfc/, agent/, universes/, generated references
(BIBLE.md, WORLD.md, CRAFT.md, schema.md are generated and gitignored)
tools/ codex.ps1, gen-schema.ps1, prose-agent.ps1
scripts/ maintenance scripts
engine/, engine_data/ seed and export mirrors and media; SQL is the live read path
html/ patent-disclosures.htm
src/README.md is the orientation map for the solution. src/Prose.V4.Cli holds no project and is not in the solution.
dotnet build src\Prose.slnx
Publish the desktop apps to C:\Apps\MindAttic\Prose\ (Hub.exe, Writer.exe, Launcher.exe; KdpPublish has its own repo and deploys to C:\Apps\KdpPublish\):
powershell -ExecutionPolicy Bypass -File run.ps1 # all three, only what changed
powershell -ExecutionPolicy Bypass -File run.ps1 -Force # all three, clean rebuild
powershell -ExecutionPolicy Bypass -File run.ps1 -Apps Hub -Start Hub # Hub only
powershell -ExecutionPolicy Bypass -File run.ps1 -Apps Writer -Start Writer
powershell -ExecutionPolicy Bypass -File src\tools\launch-app.ps1 -App writer # start without rebuilding
run.ps1 republishes an app only when its exe is missing or one of its source files (its project plus every project it references) is newer than the deployed exe; -Force republishes with a clean rebuild. It stops only the apps it replaces and publishes through %LOCALAPPDATA%\Prose\build-artifacts, so it never fights a running MCP server for bin\. It writes C:\Apps\MindAttic\Prose\run.bat, which the desktop shortcuts point at: run.bat Hub, run.bat Writer, run.bat Launcher, or no argument for every app and the Launcher. It opens a menu: 1) Deploy & Run republishes (run.ps1 -Force) and then starts the app; 2) Run starts the deployed build without redeploying. Deploy & Run falls back to the existing build if the repo is gone or the publish fails. Directory.Build.props excludes obj_* and bin_* folders so isolated builds from parallel sessions do not collide.
After editing any Codex file under docs/:
powershell -File tools/codex.ps1 digest
powershell -File tools/codex.ps1 doctor
Docs (this README as the home page, docs/*.md as articles) are published to https://mindattic.github.io/Prose/ by the shared DocFX workflow in .github/workflows/docs.yml on every push to main.
dotnet test src\Prose.UnitTests\Prose.UnitTests.csproj
dotnet test src\Prose.UnitTests\Prose.UnitTests.csproj --filter "Category=LiveKeysTrusted" # live provider keys, costs money
There are 285 *Tests.cs files (NUnit). Most tests run on in-memory SQLite through TestDbFactory; explicit fixtures that need a live database or live keys are skipped by default. Wiring tests fail the build if an MCP factory tool lacks its usage attribute or a repository save loses its no-op guard.
There is no hosted deployment and there will not be one (author decision, 2026-08-23). The Azure App Service pipeline, the Azure SQL provisioning guide and their docs were deleted. "Deploying" means publishing the desktop apps locally with run.ps1; the only CI is the docs workflow that publishes to GitHub Pages.
The commit history is the design history: 1,590 commits since 2026-03-25. The reasoning behind each structural decision is in the Architectural Decision Register, section 14 of the generated bible (docs/BIBLE.md).
Recorded so they are not relearned.
STUFF is 1-based, so hand fixes repaired the wrong character. A literal -- passed through bash into sqlcmd arrived as a single ASCII SUB control character, and that mechanism produced most of 97 corrupted dashes across 11 book bibles. Always go through the service, and through the Hub.WorldStateAtBeatService once took 500 edges with no ORDER BY, so new rows were silently invisible.Ten invention disclosures describe systems in the engine as designed. They are pre-filing documents; formal claims would be drafted by patent counsel. Full text: html/patent-disclosures.htm. Some of the systems described (the structural blueprint, the quorum review panels and the emotional rubric) have since been retired or switched off.
docs/BIBLE.md, WORLD.md, CRAFT.md, DELIGHT.md, ENGINE.md, GLMZ.md, SCRY.md) and docs/schema.md are generated from the database and gitignored, so a fresh clone does not have them until you run prose --generate-canon-md --all (through the Hub) and tools/gen-schema.ps1 (which reads the LocalDB schema directly).docs/PROVIDERS.md predates the provider expansion.tools/codex.ps1 doctor fails on a checkout without the generated docs/BIBLE.md (missing required file, and unresolved SS- cross-references in docs/USER_STORIES.md, two RFCs and docs/data/ENTITY_IDENTITY.md). Front-matter and digest checks pass./do, /quicksave and /show.docs/BIBLE.md (generated, see Limitations): engine invariants and the Architectural Decision Register.workflow db render; change them with the workflow CLI, never by hand.CRAFT.md and DELIGHT.md, is generated).This repository has no LICENSE file. All rights reserved.
PDF export uses QuestPDF under its Community license.
Part of MindAttic — see more projects at github.com/mindattic. Related: ExperimentEve, the first Universe Interchange consumer.
A local novel-writing engine: SQL Server canon for whole fictional universes, a desktop Writer, and a CLI and MCP server so Claude can draft, read and repair books against that canon.
เครื่องมือ
ยังไม่มีรายการเครื่องมือ เซิร์ฟเวอร์แบบรีโมตจะได้รายการหลังการตรวจสอบสถานะครั้งแรก
FAQ
คัดลอกคอนฟิก stdio สำหรับ Cursor, Claude Desktop, Claude Code หรือ VS Code ได้ในหน้านี้ คอนฟิกนี้ใช้การติดตั้งของผู้เผยแพร่ ไม่ใช่พร็อกซีของ PlugMCP
ระเบียนนี้ไม่ได้ระบุตัวแปรสภาพแวดล้อมที่จำเป็น
Prose ทำงานแบบโลคัลผ่าน stdio
ตรวจสอบล่าสุดเมื่อ 2026-11-09 A local novel-writing engine: SQL Server canon for whole fictional universes, a desktop Writer, and a CLI and MCP server so Claude can draft, read and repair books against that canon.