Obsidian Dictionary MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| glossary-path | No | The path to the technical glossary markdown file within the Obsidian vault (e.g., /path/to/your/ObsidianVault/Glossary/개발용어사전.md). If set, the file_path parameter can be omitted when calling tools. |
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 |
|---|---|
| append_entryA | Append a new glossary entry to the dictionary file. Use this to add new technical terms to the Obsidian glossary. |
| search_entryA | Check if a term already exists in the glossary. Returns true/false and the entry content if found. |
| get_entryA | Retrieve a specific entry from the glossary by term name. Returns only that entry, not the whole file. |
| list_termsA | List all terms currently in the glossary (returns only term names, not full content). |
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 4 tools
Each tool has a clearly distinct purpose: adding, retrieving, listing, and searching entries. There is no overlap in functionality.
All tool names follow a consistent verb_noun pattern with underscores (append_entry, get_entry, list_terms, search_entry), making them predictable and easy to understand.
With 4 tools, the set is appropriately scoped for a dictionary server. It covers essential operations (add, read, list, search) though it misses update and delete, which would be natural additions.
The tool surface covers adding, retrieving, listing, and checking existence, but notably lacks update and delete operations, which are common in dictionary management. This may be intentional but leaves gaps for full lifecycle management.