@appsoftwareltd/etherpk-mcp 0.6.0 → 0.7.0

package/README.md

@@ -81,6 +81,9 @@ prints this reference, `--version` (`-v`) the version.
 | `semantic setup` | Install the embedding runtime (about 300 MB, through your npm) and the 23 MB model into the cache directory. Once per computer. |
 | `semantic status` | Whether semantic search is set up here, and each cached graph's embedding progress. |
 | `semantic remove` | Delete the runtime and model. Each graph's stored vectors stay in its cache and are reused if you set up again. |
+| `publish (--graph <id or name> \| --folder <path>) --publication <id> [--out <dir>]` | Publish one publication of a graph to a folder on this computer and print the report. `--out` sets the folder for that graph and publication and is remembered: the command without `--out`, and the agent's `publish` tool, write there from then on (the agent can't choose a folder). The folder's owned files (top-level `.html`, `assets/`, `theme/`, the search, feed and report files) are rewritten and their strays removed; everything else is left alone. Writes files; deploying them is yours. |
+| `diagrams setup` | Install a Chromium (about 170 MB) into the cache directory so a publish can draw Mermaid diagrams. Once per computer; a publish with diagrams refuses until then. |
+| `diagrams status` | Which browser a publish would use, if any. |
 
 | Flag | Applies to | Meaning |
 | --- | --- | --- |
@@ -91,6 +94,8 @@ prints this reference, `--version` (`-v`) the version.
 | `--folder <path>` | `serve` | The local graph folder to serve. Exclusive with `--graph` and `--sync-server`. |
 | `--no-semantic` | `serve` | Keep this agent text-only even when semantic search is set up. |
 | `--all` | `logout` | Every server at once. |
+| `--publication <id>` | `publish` | Which publication of the graph. `list_publications` and Settings → Publish show the ids. |
+| `--out <dir>` | `publish` | Where the site goes on this computer. Remembered for the graph and publication. |
 
 | Environment variable | Meaning |
 | --- | --- |
@@ -100,13 +105,27 @@ prints this reference, `--version` (`-v`) the version.
 | `ETHERPK_MCP_CACHE_DIR` | The cache root for graphs, the semantic runtime and the model. Default `~/.cache/etherpk/mcp` (`XDG_CACHE_HOME` respected). Set it in the agent registration's `env` as well as your shell: the agent starts `serve` with its own environment. |
 | `ETHERPK_MCP_SEMANTIC_THREADS` | Threads for the embedding model. Default a quarter of the cores, at most four. |
 | `ETHERPK_MCP_DEBUG_MEMORY` | `1` logs the process's memory use every 10 seconds and on every progress line. |
+| `ETHERPK_MCP_PUBLISH_CONFIG` | The file remembering each publication's publish folder. Default `publish.json` beside the config file. |
+| `ETHERPK_CHROMIUM` | A Chromium on this computer for drawing diagrams, instead of the one `diagrams setup` installs. NixOS needs this. |
 
 ## What the agent gets
 
-`list_documents`, `read_document`, `search`, `backlinks`, `tasks`, `edit_document` (an exact,
-unique old→new replacement; on a synced graph it merges with anyone typing elsewhere on the
-page), `append_document` (a page, or a day's journal entry, created if needed) and
-`create_page`. One running instance serves one graph.
+Thirty-two tools, the same over a synced graph and a folder. Reading: `graph_info`,
+`list_documents` (with a range of journal days), `read_document` (the body as text, the
+frontmatter as data), `read_documents`, `search`, `backlinks`, `tasks`, `list_assets`,
+`read_asset`, `list_publications`. Writing: `edit_document` (an exact, unique old→new
+replacement; on a synced graph it merges with anyone typing elsewhere on the page),
+`append_document` (a page, or a day's journal entry, created if needed), `create_page`,
+`set_frontmatter` (`public`, `publications`, `date`, any key; never the title or aliases),
+`set_task`, `set_aliases`, `plan_rename` and `rename` (scoped concepts carried along, links
+rewritten by default, a merge only when confirmed), `upload_asset` (returns the markdown to
+paste), `create_publication`, `update_publication` and `publish` (into the folder you set with
+the `publish` command; it can't choose one). Themes: `list_themes`, `read_theme` and
+`read_theme_file` (a theme's files out to disk to edit), `create_theme` and
+`customise_publication_theme` (a copy in the graph, since a bundled theme is never edited in
+place), `write_theme_file`, `delete_theme_file`, `import_theme_folder`, `delete_theme`, and
+`preview_theme` (a rendered site to inspect, with screenshots when a browser is set up). A
+protected document is refused by every one of them. One running instance serves one graph.
 
 No skill or extra setup is needed: the server describes its tools and the graph, and Claude Code
 reaches for them when you ask about your notes. To make that a rule rather than a good guess, add