list_novel_projects
List the novel projects available under the project root
LABSCO SUMMARY
Manuscript and notes, kept apart on purpose.
Anyone who has written a long novel knows the question: did I establish this, or did I only plan it? Being able to search the setting notes and the manuscript separately answers that directly, and having both semantic and regex search means you can look for a phrase you remember exactly or an idea you only remember vaguely.
What it is
A writing-support server for long-form fiction. A project is a directory holding novel.json, a settings folder for character and world notes, and a contents folder for the manuscript itself. Both are indexed, and every search can be scoped to one or the other, which is the distinction that matters when you are asking whether a detail is established or merely drafted. A file watcher keeps the index current as you write.
What you get
search_novel_text— full-text search across the project with regular expression supportsearch_rag— semantic similarity search using multilingual-e5-small embeddings over Qdrant, with 384-dimension vectors and multilingual coverage- A
fileTypeparameter on both searches —contentfor manuscript only,settingsfor notes only,bothby default list_novel_projects— enumerate the projects under the root you configured- Reading and creating files: fetch the settings, the manuscript or the instruction files for a project, and add a new settings or content file
- Chunking with 20% overlap so a passage split across chunks keeps its context, and pre-filtering done inside Qdrant rather than after retrieval
Requirements
Nothing — no account, no key. Node.js 20.0.0 or higher, plus Docker if you want semantic search; when --qdrant-url is not given the server starts Qdrant in Docker itself, and --docker-enabled false turns that off. From a clone, npm install and npm run build, then point the client at dist/index.js with --project-root set to the directory holding your novels. When Qdrant is unavailable the server falls back with a detailed error rather than silently degrading.
Setup effort
Build from source — git clone https://github.com/cedretaber/dialogoi
USE CASES
01
Checking whether a detail is already on the page
Search the manuscript alone for the fact, so notes and plans do not get mistaken for text that exists.
02
Finding the scene you half-remember
Search by meaning rather than wording when you cannot recall the exact phrase you used.
03
Keeping a character consistent
Search the settings files for what was established about a character before writing them again.
04
Working across several manuscripts
List the projects under your root and pick the one to search.
11 tools
Listed in project code.
list_novel_settings
List a novel's settings files with the first three lines of each
get_novel_settings
Read a novel's settings (.md or .txt); name a file to get just that one
add_novel_setting
Create a new settings file, with path safety checks
list_novel_content
List a novel's manuscript files with the first three lines of each
get_novel_content
Read the manuscript (.txt or .md); name a file to get just that one
add_novel_content
Create a new manuscript file, with path safety checks
list_novel_instructions
List the project's instruction files (such as DIALOGOI.md) with their first three lines; meant to be called first
get_novel_instructions
Read the project's guidelines in full (DIALOGOI.md); without a filename, all instruction files are joined
search_novel_text
Keyword or regular-expression search across the project's text files, filtered to manuscript, settings or both
search_rag
Semantic search for related passages with multilingual-e5-small embeddings in Qdrant, filtered to manuscript, settings or both
BEFORE YOU INSTALL
What to know first
Tools you get
11 tools registered in the project's code.
Requires
Node.js 20.0.0 or later
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
You clone and build this one yourself.
Server setup
TERMINAL
git clone https://github.com/cedretaber/dialogoi
cd dialogoi
npm install
npm run buildMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"dialogoi": {
"command": "node",
"args": [
"<YOUR_PATH_TO_DIALOGOI>/dist/index.js",
"--project-root",
"<YOUR_PATH_TO_NOVELS>"
],
"cwd": "<YOUR_PATH_TO_DIALOGOI>"
}
}
}
