palace-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_HOST | No | Host where Obsidian's REST API listens | 127.0.0.1 |
| OBSIDIAN_PORT | No | Port for the REST API | 27123 |
| OBSIDIAN_API_KEY | Yes | Bearer token from the Local REST API plugin | |
| OBSIDIAN_PROTOCOL | No | http or https | http |
| PALACE_APPEND_DENY | No | Comma-separated paths where append_note is blocked | /Context/,/System/,Index.md |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_notesA | List files and folders. Pass a subdirectory path, or leave empty for the vault root. |
| read_noteA | Read a note's full contents by vault-relative path, e.g. 'People/Alice.md'. |
| write_noteA | Create a new note or OVERWRITE an existing one at the given vault-relative path. |
| append_noteA | Append text to the end of a note (creates the note if it doesn't exist). |
| search_notesA | Full-text search the vault; returns matching filenames ranked by relevance. |
| active_noteA | Return the contents of the note currently open in Obsidian. |
| delete_noteA | Permanently delete a note. Use with care — this is irreversible. |
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 7 tools
Each tool maps to a distinct file operation: listing, reading, writing, appending, searching, accessing the active note, and deleting. There is no meaningful overlap between tool purposes.
Most tools follow a clear verb_note pattern: read_note, write_note, append_note, delete_note, and search_notes. The deviations are minor: list_notes uses plural and active_note is adjective_noun, but the overall convention is still predictable.
Seven tools is a well-scoped set for an Obsidian vault server. Each tool covers a necessary note operation without unnecessary bloat.
The core note lifecycle is covered: list, read, write, append, search, and delete. Missing operations like rename, move, or folder management are minor gaps that agents can usually work around by writing to a new path.