Obsidian MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OBSIDIAN_API_KEY | No | API key for Obsidian Local REST API | |
| OBSIDIAN_API_URL | No | URL for Obsidian Local REST API | |
| OBSIDIAN_REMOTE_URL | No | URL for remote vault API | |
| OBSIDIAN_VAULT_NAME | No | Name of the local vault | |
| OBSIDIAN_VAULT_PATH | No | Path to the local Obsidian vault | |
| OBSIDIAN_REMOTE_NAME | No | Name of the remote vault | |
| OBSIDIAN_SYNC_INTERVAL | No | Sync interval for remote vault in milliseconds | |
| OBSIDIAN_REMOTE_API_KEY | No | API key for remote vault access |
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 |
|---|---|
| get_noteC | Get a note by its path |
| search_notesC | Search for notes in a vault |
| create_noteC | Create a new note |
| update_noteC | Update an existing note |
| delete_noteC | Delete a note |
| get_vault_statsC | Get statistics about a vault |
| list_tagsC | List all tags in a vault |
| list_foldersC | List all folders in a vault |
| get_knowledge_graphB | Get the complete knowledge graph for a vault |
| get_related_notesC | Get notes related to a specific note |
| analyze_graphC | Analyze the knowledge graph structure |
| suggest_linksC | Suggest related notes for linking |
| get_canvasC | Get canvas file contents |
| create_canvasC | Create a new canvas file |
| add_canvas_nodeC | Add a node to canvas (file, text, link, or group) |
| add_canvas_edgeC | Add an edge between nodes in canvas |
| list_canvas_filesC | List all canvas files in vault |
| dataview_queryC | Execute a Dataview-style query on notes |
| get_note_metadataC | Get metadata for a specific note |
| get_unique_valuesC | Get all unique values for a metadata field |
| list_templatesC | List all available templates |
| render_templateC | Render a template with variables |
| create_from_templateC | Create a new note from a template |
| create_daily_noteC | Create a daily note for a specific date |
| create_weekly_noteC | Create a weekly note for a specific date |
| create_monthly_noteC | Create a monthly note for a specific date |
| create_yearly_noteC | Create a yearly note for a specific year |
| get_periodic_note_infoC | Get info about a periodic note |
| list_periodic_notesC | List periodic notes of a specific type |
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 29 tools
Most tools have distinct purposes, but there is some overlap between 'get_related_notes' and 'suggest_links' (both involve finding related notes), and 'analyze_graph' and 'get_knowledge_graph' both deal with graph analysis. Descriptions help clarify differences, but agents might occasionally confuse these pairs.
Tool names follow a consistent verb_noun pattern throughout, such as 'create_note', 'get_note', 'list_tags', and 'update_note'. There are no deviations in naming conventions, making the set predictable and readable.
With 29 tools, the count is borderline high for a note-taking and knowledge management server. While it covers many features, it feels heavy and could overwhelm agents, suggesting some tools might be redundant or overly specialized.
The tool set provides comprehensive coverage for Obsidian's domain, including CRUD operations for notes and canvases, periodic notes, templates, queries, graph analysis, and vault management. There are no obvious gaps, and agents can handle full workflows without dead ends.