StoryCanon

jp.softglowPublished by softglow.jpOfficial publisherv1.0.0Updated Oct 24, 2026

A structured story bible for long-form fiction: scenes, characters, world, plot and foreshadowing.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryMedia & Design

Overview

AI-generated overview

A remote story-bible server for long-form fiction that lets an assistant save and consult a work's scenes, characters, world, plot and foreshadowing.

What you can do
Store and retrieve per-work story settings, manuscript text, characters and worldbuilding, as described in the README's purpose statement. Keep track of plot threads, foreshadowing and open TODOs across a long work. Recall the current state of the story so an assistant can continue consistently. No individual tools are listed in the manifest, so exact operations are not documented here.
When to use it
Useful when drafting or consulting a long-form novel with an assistant and you want settings, characters and foreshadowing kept per work rather than re-pasted each session. Best suited to writers who already work with the StoryCanon service.
Requirements
A remote endpoint reached over streamable HTTP; no local package or runtime is needed. Authentication is required via OAuth 2.1 with dynamic client registration, or an Authorization bearer token for clients that cannot do OAuth. Network access to the service is required.
Before you install
The server holds your manuscript text and story settings, so treat it as a store of unpublished creative work and check how it is retained. An Authorization bearer token is a credential; keep it out of shared configuration. The README notes that a misconfigured build can bake a development secret value into production, so verify deployment settings if you self-host.

Installation

In SourceWeft

  1. Open StoryCanon in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/jp.softglow%2Fstorycanon/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "storycanon": {
      "type": "http",
      "url": "https://storycanon.softglow.jp/mcp"
    }
  }
}

README

StoryCanon

StoryCanon は、ChatGPT で生成・相談した小説の設定、本文、キャラクター、世界観、伏線、TODO、現在の物語状態を作品ごとに保存するための MVP 実装です。

構成

  • apps/web: Next.js + TypeScript + Prisma + PostgreSQL の Web/API アプリ
  • packages/db: Prisma クライアント。Node と Cloudflare Workers で別の生成物が要るため独立したパッケージにしてある（後述）
  • docs: 内部仕様、外部仕様、移行の記録
  • tests/integration: ローカル結合テスト

デプロイ先

本番は Cloudflare Workers + Supabase PostgreSQL（東京） で稼働している。 main への push で .github/workflows/deploy-workers.yml がマイグレーションとデプロイを行う。

2026-08-30 までは AWS（ALB + ECS Fargate + RDS）だった。移行の経緯と当時ハマった点は docs/cloudflare-cutover.md に残してある。AWS 側の資源は撤去済みで、 CDK のブートストラップも消してあるため、AWS へ戻すには cdk bootstrap からやり直しになる。

ローカル開発

powershell
npm installCopy-Item .env.example apps/web/.envdocker compose up -d postgresnpm run prisma:migrate -w apps/webnpm run dev -w apps/web

テスト

powershell
npm run test -w apps/web        # ユニットnpm run test:integration        # 結合（外部リソースは作らない）

Prisma クライアント

Prisma 7 は TypeScript しか出力しないため、クライアントは packages/db でコンパイルしてから使う。 Node と workerd では必要な生成物が違うので両方を作り、package.json の conditional export で 振り分けている。呼び出し側は @storycanon/db を import するだけでよい。

生成物は git 管理外で、npm run dev / build / test / lint が必要な方を自動で作る。 tsc を単体で走らせる場合だけ、先に npm run db:node -w apps/web が要る。

Cloudflare へのデプロイ

通常は main への push で CI が行う。手元から出す場合は apps/web で:

powershell
npm run deploy:worker

npx opennextjs-cloudflare build を直接叩かないこと。 deploy:worker は scripts/build-worker.mjs 経由でローカルの .env 類を退避してからビルドする。 これを飛ばすと next build がローカルの値をバンドルに焼き込み、NEXTAUTH_SECRET が 開発用の値のまま本番に乗る。

Source: README.md at commit 1583869

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.