Obsidian Semantic MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| vaultC | File and folder operations - list, read, create, update, delete, search |
| editC | Smart editing operations - window (auto-buffers content), append, patch, at_line, from_buffer |
| viewC | Content viewing and navigation - file, window, active, open_in_obsidian |
| workflowC | Workflow guidance and suggestions based on current context |
| systemC | System operations - info, commands, fetch_web |
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 5 tools
Each tool has a clearly distinct purpose: edit handles content modifications, system manages system-level operations, vault deals with file management, view focuses on content display and navigation, and workflow provides contextual suggestions. There is no overlap in functionality that would cause confusion for an agent.
All tool names follow a consistent, simple noun-based pattern (edit, system, vault, view, workflow) without mixing conventions like camelCase or snake_case. This predictability makes it easy for an agent to understand and select tools.
With 5 tools, the server is well-scoped for an Obsidian integration, covering key areas like file operations, content editing, system interactions, viewing, and workflow assistance. Each tool earns its place without feeling excessive or insufficient.
The tool set provides comprehensive coverage for core Obsidian workflows, including CRUD operations via vault, editing capabilities, and navigation. A minor gap might be the lack of explicit tools for plugin management or advanced search, but agents can likely work around this with existing tools like system and vault.