
Author Mcp Server
io.github.litheonhqPublished by GitHub account litheonhqv0.1.1Updated Oct 24, 2026
Recall, check, search, timeline, and graph tools for fiction writers via Seizn Memory v3.
Overview
A local MCP server that gives an AI assistant recall, conflict-checking, search, timeline and relationship-graph tools over a fiction writer's Seizn canon.
- What you can do
- Recall canon for a named character, place, object, rule, event or promise, including recent mentions, current state and pending conflicts, and approve a fact as canon. Check a passage of prose for canon conflicts ranked by severity. Semantically search across all project entities. Read chapter-by-chapter timeline beats, optionally within a range. Explore a relationship graph subset rooted at an entity.
- When to use it
- Useful for fiction writers who keep their story bible in Seizn Author and want their existing AI chat client to check drafts for continuity errors, look up established facts, or browse timelines and relationships without switching editors.
- Requirements
- A local Node.js runtime to run the npm package (globally or via npx), and a Seizn API key supplied in the SEIZN_API_KEY environment variable. An optional SEIZN_API_BASE_URL overrides the default API endpoint. A Seizn account and plan quota apply; the check and timeline tools also need your own LLM key or a managed plan.
Installation
In SourceWeft
- Open Author Mcp Server in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@seizn/author-mcp-server
[npm version] [license] [status]
MCP server exposing Seizn Author canon recall, conflict check, semantic search, timeline, and relationship graph tools to any MCP-compatible AI agent (Claude Desktop, Claude Code, Cursor, Cline, Continue, Zed, etc.).
Bring Seizn canon into the AI tool you already use. No new editor required.
What it does
When connected, your AI agent gains six tools:
All tools call the Seizn Author REST API (/api/v1/*) with your Bearer token.
Setup
1. Get a Seizn API key
Generate one at https://seizn.com/dashboard/account/api-keys (Free tier: 100 calls/day, BYOK required).
2. Install (npm)
Or use npx:
3. Wire into your MCP client
Claude Desktop
Add to claude_desktop_config.json:
Claude Code
Cursor / Cline / Continue
See your client's MCP server documentation. The package supports:
- stdio (default for desktop clients)
- streamable-http (for hosted scenarios)
- SSE (legacy)
Configuration
Usage examples
In your AI chat:
'Recall everything Seizn knows about Seoyun in project ch7-draft.' → invokes
seizn_author_recallwith name=Seoyun
'Check this scene for canon conflicts: ...' → invokes
seizn_author_checkwith the pasted text
'Show me the timeline from Ch.5 to Ch.7.' → invokes
seizn_author_timelinewith from=ch5, to=ch7
The AI decides when to call each tool based on the conversation. You don't have to remember tool names.
Pricing
Track 2 plan covers Track 2 surface (API + MCP) only. Seizn Author has separate plans for the web dashboard (Track 1, KRW) and the Tauri desktop app (Track 3, KRW). One Stripe customer holds multiple subscriptions, billed independently. See https://seizn.com/pricing for cross-track upsell details.
No subscription required for AI inference. Tools split into two groups:
The Seizn subscription covers the canon backend and recall infrastructure. The two AI-enhanced tools (check, timeline) require either your own LLM key (BYOK, any tier) or Studio Managed ($299/mo) which includes 500 Opus calls.
Your host AI agent's LLM is separate. Whether you use Claude Pro/Max subscription via Claude Code/Desktop, Cursor Pro, or BYOK in Cline/Continue — the host handles its own LLM cost. Seizn doesn't double-charge.
See https://seizn.com/pricing for full details.
Versioning
While the package is on 0.x.y we may ship breaking changes on minor bumps (0.2.0 etc.) — we'll call them out clearly in CHANGELOG.md. Once we tag 1.0.0, strict semver applies: major = breaking, minor = additive, patch = fix-only.
Each release is published with a matching GitHub tag (v0.1.0, …) and a CHANGELOG.md entry.
License
MIT © Litheon LLC
Issues / contributions
https://github.com/litheonhq/seizn/issues (label: track-2-platform)
Source: packages/author-mcp-server/README.md at commit af6a465
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
40% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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.