Obsidian Vault API
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DATA_DIR | No | Path for persistent config file | /data |
| VAULT_PATH | No | Path to the vault directory inside the container | /vault |
| VAULT_API_KEY | No | API key for MCP authentication. If empty, one is generated and saved | |
| VAULT_API_BIND | No | Bind address (0.0.0.0 for Docker / network access) | 0.0.0.0 |
| VAULT_API_HOST | No | Host reported in image URLs (set to your external address if behind a proxy) | 127.0.0.1:2768 |
| VAULT_API_PORT | No | Port to listen on | 2768 |
| VAULT_API_AUTO_UPDATE | No | Enable daily GitHub update checks on first boot. The Web UI setting is saved in /data/config.json | false |
| VAULT_API_ALLOWED_COMMANDS | No | Glob patterns for allowed shell commands (comma-separated). * = all | * |
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 |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues