Obsidian Translation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | The execution environment for the Node.js application, e.g., 'production'. | |
| ANTHROPIC_API_KEY | Yes | Anthropic API key required for performing note translations. | |
| OBSIDIAN_VAULT_PATH | Yes | The absolute path to the Obsidian vault. | |
| BACKUP_RETENTION_DAYS | No | Number of days to retain automatic backups before they are cleared. | 30 |
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 |
|---|---|
| translate_obsidian_noteB | Translate an Obsidian note from obsidian:// URL and update the original file |
| create_obsidian_noteC | Create a new Obsidian note with optional frontmatter and tags |
| read_obsidian_noteB | Read content of an existing Obsidian note |
| update_obsidian_noteB | Update an existing Obsidian note |
| search_obsidian_notesC | Search for notes in Obsidian vault by content or title |
| search_obsidian_notes_by_tagsC | Search for notes by tags |
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 6 tools
Each tool targets a distinct action: create, read, search (by content/title), search by tags, translate, and update. No two tools have overlapping purposes; the two search tools are clearly differentiated by their search method.
All tool names follow a consistent verb_noun pattern (e.g., create_obsidian_note, search_obsidian_notes, translate_obsidian_note). The naming is uniform and predictable.
With 6 tools, the server is well-scoped for managing Obsidian notes with translation capabilities. Each tool serves a distinct purpose, and the count is neither too sparse nor overwhelming.
The tool set covers core note operations (create, read, update, search) and adds translation. A delete tool is missing, but otherwise the surface is adequate for the stated purpose.