novel-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NOVEL_MODEL | No | Model name for the provider | |
| NOVEL_API_KEY | No | API key for OpenAI-compatible provider | |
| NOVEL_BASE_URL | No | Base URL for OpenAI-compatible provider | |
| NOVEL_PROVIDER | No | Provider type: mock, openai-compatible, or anthropic | mock |
| ANTHROPIC_API_KEY | No | API key for Anthropic provider |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| validate_projectB | Validate a novel project without changing it. |
| build_contextC | Create a run and record an inspectable context packet for one chapter. |
| generate_draftC | Generate and record a draft with a configured provider; mock works offline. |
| submit_draftA | Record draft text produced by an external AI tool in an existing run. |
| review_runB | Review the recorded draft and create a state proposal for human approval. |
| project_statusC | Return project status or one run's status. |
| inspect_runB | Inspect run state, artifacts, and proposed state differences. |
| approve_runA | Human approval gate: commit draft and proposed state exactly once and create a snapshot. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct action in the novel project workflow: validation, context building, draft generation, external submission, review, inspection, approval, and status. No overlapping purposes.
All tool names follow the verb_noun pattern in snake_case (e.g., validate_project, generate_draft, approve_run), providing clear and predictable naming.
With 8 tools, the set is well-scoped for a novel writing assistant, covering the essential workflow stages without excess or deficiency.
Core CRUD-like operations are present: create (build_context), update (submit_draft, approve_run), read (project_status, inspect_run), delete is absent but not critical. Minor gap: no tool to list all runs or chapters, but the workflow is coherent.