session-vault
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SESSION_VAULT_CONFIG | No | Override config file path | |
| SESSION_VAULT_PROVIDER | No | Override session provider (ocsm/native) | |
| BAIDU_NETDISK_CLIENT_ID | No | Optional OAuth client ID | |
| SESSION_VAULT_OPENCODE_DB | No | Override OpenCode DB path | |
| BAIDU_NETDISK_ACCESS_TOKEN | No | Baidu access token bootstrap | |
| BAIDU_NETDISK_CLIENT_SECRET | No | Optional OAuth client secret | |
| BAIDU_NETDISK_REFRESH_TOKEN | No | Optional refresh token |
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
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 10 tools
Each tool targets a distinct resource-action pair (project, session, archive, remote_copy, tag), with no overlapping functionality. Agents can clearly differentiate between tools.
All tools follow a consistent snake_case pattern: 'session_vault_<resource>_<action>'. The naming convention is uniform and predictable.
With 10 tools covering multiple resources (projects, sessions, archives, remote copies, tags), the count is well-scoped and appropriate for a focused session vault management server.
The tool set lacks essential CRUD operations for core resources. Projects and sessions only have list functionality, and archives are missing update/delete. These gaps hinder full lifecycle management.