obsidian-ts-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_VAULT | Yes | Default vault name appended to every CLI call. The name must match exactly what Obsidian shows in the vault switcher. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_noteB | Create a new note in the Obsidian vault. Supports optional content and templates. Use this when you need to record a new session, decision, or piece of documentation. |
| read_noteA | Read the full contents of a note. Returns the markdown content including frontmatter. Provide at least one of 'file' or 'path' to identify the note. |
| append_to_noteA | Append content to the end of an existing note. Useful for adding session logs, tasks, or follow-up notes to an existing document. |
| prepend_to_noteB | Prepend content after the frontmatter of a note. Useful for adding a summary or status update at the top of an existing document. |
| search_vaultA | Search the vault for text. Returns matching files and context. Use Obsidian's full search syntax (supports operators, tags, paths). |
| daily_noteA | Get today's daily note path, creating it if it doesn't exist. Returns the file path of the daily note. |
| daily_appendA | Append content to today's daily note. Creates the daily note if it doesn't exist. Useful for logging tasks, session summaries, or quick entries. |
| get_vault_infoB | Get information about the Obsidian vault: name, path, file count, folder count, and size. |
| list_filesB | List files in the vault. Can filter by folder and/or file extension. |
| get_tagsA | List all tags in the vault with their occurrence counts. Always returns all tags with counts included. |
| get_backlinksA | List all notes that link to a given note (backlinks/incoming links). Provide at least one of 'file' or 'path' to identify the note. |
| get_outlineB | Get the heading structure/outline of a note. |
| set_propertyC | Set a frontmatter property on a note. Supports text, list, number, checkbox, date, datetime types. |
| read_propertyB | Read a frontmatter property value from a note. |
| list_tasksB | List tasks from notes. Can filter by file, completion status, or show tasks from the daily note. |
| toggle_taskA | Toggle a task's completion status. Identify the task by 'ref' (path:line) or by 'file' and 'line' together. |
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 16 tools
Most tools have distinct purposes, but there is some overlap between 'append_to_note' and 'prepend_to_note' (both modify note content), and 'daily_append' and 'append_to_note' (both append content, but to different targets). Descriptions help clarify these differences, but an agent might occasionally confuse them when deciding between appending to a specific note versus the daily note.
All tool names follow a consistent verb_noun pattern with snake_case, such as 'append_to_note', 'create_note', and 'get_backlinks'. There are no deviations in naming conventions, making the set predictable and easy to parse.
With 16 tools, the server is well-scoped for managing an Obsidian vault, covering operations like note creation, reading, updating, searching, and task management. Each tool serves a specific function without redundancy, fitting the domain's complexity appropriately.
The tool set provides comprehensive coverage for Obsidian vault management, including CRUD operations for notes (create, read, update via append/prepend), property handling, search, backlinks, tags, tasks, and vault info. There are no obvious gaps; agents can perform full workflows from note creation to organization and retrieval.