zennotes-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ZENNOTES_URL | No | Base URL of the ZenNotes server | http://127.0.0.1:7878 |
| ZENNOTES_AUTH_TOKEN | No | Bearer token of the server for protected routes |
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
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| health_checkA | Ping le serveur (GET /api/healthz). Pas d'auth requise. |
| get_versionB | Version du serveur + runtime Go. |
| get_capabilitiesB | Capacites annoncees par le serveur (watch, templates, workflows...). |
| get_platformB | Plateforme hote du serveur. |
| session_statusB | Etat de session (auth requise ou non). |
| session_loginA | Ouvre une session navigateur via le token bootstrap. |
| session_logoutA | Ferme la session courante. |
| session_rotate_tokenA | Regenere le token d'auth (ATTENTION : invalide l'ancien). |
| vault_infoB | Infos vault : racine + nom. |
| get_vault_settingsA | Lit les reglages du vault (dossiers systeme, daily notes, taches...). |
| set_vault_settingsC | Ecrit les reglages du vault (passer l'objet settings complet). |
| browse_directoriesB | Explore les dossiers cote serveur (vault picker). |
| list_notesB | Liste toutes les notes (metadonnees). |
| list_foldersB | Liste les dossiers du vault. |
| read_noteB | Lit une note (body markdown + frontmatter). Ex: 'Bienvenue.md'. |
| write_noteA | Ecrase le contenu d'une note existante. |
| create_noteC | Cree une note. folder = inbox|quick|archive|trash. |
| capture_noteB | Capture rapide : cree une note puis y ecrit le body si fourni. |
| append_to_noteB | Ajoute du texte a la fin d'une note. |
| prepend_to_noteB | Ajoute du texte au debut d'une note. |
| rename_noteB | Renomme une note (les [[wikilinks]] suivent automatiquement). |
| move_noteC | Deplace une note vers un autre dossier. |
| duplicate_noteC | Duplique une note. |
| trash_noteA | Met une note a la corbeille (restaurable). |
| restore_noteB | Restaure une note depuis la corbeille. |
| delete_noteA | Supprime definitivement une note (non restaurable). |
| empty_trashB | Vide la corbeille. |
| archive_noteC | Archive une note. |
| unarchive_noteC | Sort une note de l'archive. |
| create_excalidrawC | Cree un dessin Excalidraw. |
| read_commentsB | Lit les commentaires d'une note. |
| write_commentsC | Ecrit les commentaires d'une note (liste d'objets commentaire). |
| search_textA | Recherche plein-texte dans le vault (matches par ligne). |
| get_search_capabilitiesB | Moteur de recherche dispo (ripgrep / fzf). |
| all_tasksC | Toutes les taches agregees du vault. |
| tasks_forC | Taches d'une note donnee. |
| create_folderC | Cree un dossier. folder = inbox|quick|archive|trash. |
| rename_folderC | Renomme un sous-dossier. |
| delete_folderD | Supprime un dossier. |
| duplicate_folderC | Duplique un dossier. |
| list_assetsB | Liste les pieces jointes. |
| assets_existsB | Dit si le dossier assets existe. |
| upload_assetB | Upload un fichier local comme asset, optionnellement lie a une note. |
| download_assetB | Telecharge un asset vers un chemin local. |
| rename_assetC | Renomme un asset. |
| move_assetC | Deplace un asset. |
| duplicate_assetC | Duplique un asset. |
| delete_assetA | Supprime un asset (corbeille assets, restaurable). |
| list_deleted_assetsC | Assets supprimes (restaurables). |
| restore_deleted_assetB | Restaure un asset supprime (passer l'objet deleted tel quel). |
| purge_deleted_assetA | Purge definitivement un asset supprime. |
| empty_deleted_assetsA | Vide la corbeille des assets. |
| list_templatesA | Liste les templates custom (.zennotes/templates). |
| read_templateA | Lit un template. Ex: '.zennotes/templates/adr.md'. |
| write_templateC | Cree ou edite un template. |
| delete_templateC | Supprime un template. |
| list_workflowsB | Liste les workflows. |
| write_workflowC | Cree ou edite un workflow. |
| delete_workflowC | Supprime un workflow. |
| apply_workflowC | Applique un run de workflow prepare (workflowId, ops, changes...). |
| undo_workflow_runC | Annule un run de workflow. |
| list_workflow_runsB | Historique des runs de workflows. |
| delete_workflow_runsB | Supprime l'historique des runs d'un workflow. |
| demo_generateB | Genere la visite demo dans le vault. |
| demo_removeC | Retire la visite demo du vault. |
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 65 tools
Most tools map to a clear resource/action pair (list_notes, rename_asset, delete_workflow). A few boundary cases could be confused—create_note, write_note, and capture_note all write note content with subtly different semantics—and browse_directories may be mistaken for list_folders, but descriptions mostly clarify intent.
The dominant verb_noun snake_case pattern is readable and predictable, e.g., list_notes, create_folder, restore_deleted_asset. There are minor exceptions like session_status, vault_info, assets_exists, and demo_generate, but they do not obscure the overall convention.
With 65 tools, this server far exceeds even the 25+ threshold and crosses the 50+ extreme mismatch threshold. No matter how broad ZenNotes is, this many endpoints overwhelms an agent's tool-selection space and context window.
The tool surface covers the full lifecycle for notes, folders, assets, templates, and workflows, including soft-delete/restore and permanent delete paths. Session management, search, tasks, comments, and demo utilities are also present, leaving no major workflow dead ends.