Team Vault MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TEAM_VAULT_URL | Yes | URL of the Team Vault server, e.g. https://obsidian.artillect.pro | |
| TEAM_VAULT_API_KEY | Yes | API key for Team Vault (from web UI → API keys) | |
| TEAM_VAULT_READ_ONLY | No | Set to '1' or 'true' to disable write tools (read-only mode) | |
| TEAM_VAULT_PROJECT_ID | No | Default project ID for tools that don't specify a projectId |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| whoamiA | Return the user the configured API key belongs to (id, email, name). |
| list_projectsA | List the Team Vault projects the API key can access (id, slug, name). |
| list_notesA | List file paths in a project. |
| read_noteA | Read a text file's content by its vault path. Binary files are not returned (use the web/REST download). |
| list_note_versionsA | List the saved version history of a file by path (newest first). |
| write_noteA | Create a new text note, or overwrite an existing one, at the given vault path. Returns whether it was created or updated. |
| move_noteC | Move or rename a file within the project. |
| delete_noteA | Soft-delete a file by path (recoverable on the server as a tombstone). |
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 8 tools
Each tool has a distinct purpose: note CRUD, versioning, project listing, user info, and file moves. No two tools overlap in function.
Most tools follow a consistent 'verb_note' pattern (delete_note, list_notes, move_note etc.), with the exception of 'whoami', which deviates slightly but is a common convention.
Eight tools is well-scoped for a note management system, covering creation, reading, deletion, listing, moving, versioning, project enumeration, and user info.
CRUD and versioning are covered, but there is no explicit restore for soft-deleted notes or support for binary file operations, which are noted as server-side recoverable or external respectively.