Obsidian Dictionary MCP

🚀 Obsidian Dictionary MCP Server

This is an MCP server for managing a technical term dictionary within an Obsidian vault.

🚀 Quick Start

📦 Installation

1. Build

cd obsidian-dictionary-mcp
npm install
npm run build

2. Configure Claude Desktop

Open the ~/Library/Application Support/Claude/claude_desktop_config.json file and add the following:

{
  "mcpServers": {
    "dict": {
      "command": "node",
      "args": [
        "/path/to/obsidian-dictionary-mcp/dist/index.js",
        "--glossary-path",
        "/path/to/your/ObsidianVault/Glossary/개발용어사전.md"
      ]
    }
  }
}

3. Configure Claude Code (CLI)

To use it in the Claude Code CLI, choose one of the two methods:

Method A: Project-specific Configuration (Recommended)

Create a .mcp.json file in the project root:

{
  "mcpServers": {
    "dict": {
      "command": "node",
      "args": [
        "/path/to/obsidian-dictionary-mcp/dist/index.js",
        "--glossary-path",
        "/path/to/your/ObsidianVault/Glossary/개발용어사전.md"
      ]
    }
  }
}

Method B: Global Configuration

Add the following to the ~/.claude/settings.json file:

{
  "mcpServers": {
    "dict": {
      "command": "node",
      "args": [
        "/path/to/obsidian-dictionary-mcp/dist/index.js",
        "--glossary-path",
        "/path/to/your/ObsidianVault/Glossary/개발용어사전.md"
      ]
    }
  }
}

⚠️ Important Note

After creating or modifying the configuration file, you must restart Claude Code for the changes to take effect. This is because the MCP server reads the configuration when Claude Code starts.

The --glossary-path Option

If you set the default glossary path with the --glossary-path option:

• You can omit the file_path parameter when calling the tool.
• If not set, you must specify the file_path every time.

💻 Usage Examples

Available Tools

append_entry

Add a new term to the dictionary. Parameters:

• file_path (optional): The path to the dictionary file (can be omitted if the default path is set).
• term: The term to be added.
• dev_explanation: Explanation for developers (in Korean, 1 - 2 sentences).
• simple_explanation: Explanation for non - developers (in Korean, 1 sentence).
• example: Example (in Korean, 1 line).

search_entry

Check if a term already exists. Parameters:

• file_path (optional): The path to the dictionary file (can be omitted if the default path is set).
• term: The term to search for.

get_entry

Retrieve only the content of a specific term (not the entire file). Parameters:

• file_path (optional): The path to the dictionary file (can be omitted if the default path is set).
• term: The term to retrieve.

list_terms

Return a list of all terms in the dictionary (only term names, no content). Parameters:

• file_path (optional): The path to the dictionary file (can be omitted if the default path is set).

📚 Documentation

Dictionary Entry Format

### {term}
- Explanation for developers: {Explanation from a developer's perspective}
- Explanation for non - developers: {Simple explanation}
- Example: {Short example}

Obsidian Vault Path

Example of the dictionary file path:

/path/to/your/ObsidianVault/Glossary/개발용어사전.md