Cursidian
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_LOG_LEVEL | No | debug, info, warn, error (default info) | info |
| OBSIDIAN_READ_ONLY | No | Set to 'true' to disable writes | |
| OBSIDIAN_VAULT_PATH | Yes | Absolute path to your Obsidian vault (expands ~ / %USERPROFILE%) | |
| OBSIDIAN_MAX_FILE_SIZE | No | Max file size in bytes (default 10 MB) | 10485760 |
| OBSIDIAN_BACKUP_ENABLED | No | Pre-write backups to .cursidian-trash (default true; set false to disable) | true |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| noteA | Read, create, update, delete, rename a note, or edit its frontmatter. action=read returns content+frontmatter+contentHash+revisionHash+outgoingLinks. Path accepts vault-relative paths, titles, and frontmatter aliases (except create, which writes the literal path). update: prefer patch (old_string/new_string) or replace_section (heading); replace is size-guarded; optional frontmatter merge on the same update (one journaled op for body + metadata). Pass expectedRevision from read to detect concurrent edits (expectedHash remains a deprecated body-hash alias). Mutations return operationId/undoAvailable when journaling is enabled; use vault undo to reverse. |
| searchA | Find notes. action=content (default): full-text search, prefer 2-3 keywords, token-AND with OR fallback and typo correction, format=compact for index-only results. action=by_tags: frontmatter tag filter (AND). action=list: enumerate notes by folder (missing folder -> not_found). action=recent: newest first. action=tags: full tag vocabulary with counts; accepts no other arguments. content/by_tags/list/recent support cursor/truncated/nextCursor (stale cursor -> structured error with details.changedPaths). Responses may set incomplete+skipped when the vault scan could not read every file. list/recent/content exclude index/log/hot/_raw/_archives unless includeOperational=true. |
| graphA | Return a note's link neighborhood: resolved outgoing wikilinks, unresolved outgoing links, plus paginated backlinks (notes linking here). Depth 1 only. Path accepts vault-relative paths, titles, and frontmatter aliases. |
| vaultA | Vault maintenance. action=health: structured report (orphans, broken links, index drift, stale pages). action=sync_index: regenerate index.md from frontmatter. action=slop_check: read-only LLM-slop report (body + frontmatter). action=deslop: journaled char/emoji auto-fix (confirm: true; dryRun preview). action=create_folder/list_folders/delete_folder: folder ops (delete requires confirm, empty folders only). action=log: append to log.md and optionally hot.md (wiki bookkeeping). action=history: list journaled operations. action=undo: reverse a journaled operation (requires confirm: true). action=manifest: typed read/upsert/remove for _meta/manifest.md ingest ledger. |
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 4 tools
Each tool has a distinct domain: graph handles link relationships, note manages note CRUD, search provides various search/list functions, and vault performs maintenance and operational tasks. No overlap in purpose.
All four tool names are single lowercase nouns (graph, note, search, vault), following a consistent and predictable pattern.
4 tools is well-scoped for a note-taking vault server, covering core operations without unnecessary bloat.
The tool set covers essential CRUD, search, graph, and maintenance operations. Minor gaps include lack of export/import or batch operations, but the core workflows are adequately supported.