Obsidian MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_CALENDAR_ID | No | Google Calendar ID to use (default: primary) | primary |
| OBSIDIAN_VAULT_PATH | Yes | Path to your Obsidian vault | |
| OBSIDIAN_MAX_RESULTS | No | Maximum number of results to return | 100 |
| OBSIDIAN_SNIPPET_LENGTH | No | Length of content snippets in search results | 200 |
| OBSIDIAN_VAULT_URL_BASE | No | Base URL for Obsidian deep links (e.g., obsidian://open?vault=YourVaultName&file=) | |
| GOOGLE_CALENDAR_CREDENTIALS_PATH | No | Path to the Google Calendar credentials.json file |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| read_noteB | Read the full content of a note from the vault |
| search_notesC | Search the vault by content, title, tags, or all |
| list_notesC | List notes in the vault with optional filters |
| get_backlinksA | Get all notes that link to a specific note (incoming links) |
| get_outgoing_linksB | Get all links from a note to other notes (outgoing links) |
| list_all_tagsB | Get all tags in the vault with usage counts |
| get_notes_by_tagB | Find all notes with a specific tag |
| get_vault_statsB | Get statistics about the vault |
| get_orphaned_notesA | Find notes with no incoming or outgoing links |
| search_by_propertyB | Search for notes by frontmatter property (metadata field) |
| create_noteC | Create a new note in the vault |
| update_noteC | Update an existing note's content |
| append_to_noteC | Append content to an existing note |
| delete_noteB | Delete a note (moves to .trash by default) |
| update_frontmatterB | Update frontmatter fields in a note (preserves content) |
| get_daily_noteC | Get or create a daily note for a specific date |
| list_daily_notesC | List recent daily notes |
| list_templatesB | List available note templates |
| create_from_templateC | Create a new note from a template |
| get_link_graphB | Get the link graph for the vault |
| get_related_notesC | Find notes related to a specific note |
| create_calendar_eventC | Create a Google Calendar event linked to an Obsidian note |
| list_calendar_eventsB | List upcoming Google Calendar events |
| get_calendar_eventB | Get details of a specific calendar event by ID |
| update_calendar_eventC | Update/move a calendar event (change date, time, title, or description) |
| search_calendar_eventsC | Search calendar events by text query or date range |
| delete_calendar_eventC | Delete a Google Calendar event |
| batch_update_notesB | Update multiple notes atomically with automatic backup and rollback |
| batch_append_notesC | Append content to multiple notes atomically |
| restore_batch_backupB | Restore notes from a batch backup (undo batch operation) |
| list_batch_backupsB | List available batch backups |
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 31 tools
Most tools have distinct purposes, such as note operations (create, read, update, delete), calendar event management, and search functions. However, some overlap exists between 'search_notes' and 'search_by_property', and between 'get_backlinks' and 'get_outgoing_links', which could cause minor confusion for agents.
Tool names follow a consistent verb_noun pattern throughout, such as 'create_note', 'list_notes', 'update_note', and 'search_notes'. This predictability makes it easy for agents to understand and use the toolset effectively.
With 31 tools, the count is on the high side for an Obsidian server, which may feel heavy and potentially overwhelming. While it covers many features, a more streamlined set might improve usability without sacrificing functionality.
The toolset provides comprehensive coverage for Obsidian vault management, including full CRUD for notes and calendar events, advanced search capabilities, link analysis, batch operations with backup/restore, and vault statistics. No significant gaps are apparent for the domain.