claude-vigil-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| vigil_saveA | Create a named checkpoint of the entire project. Runs in background — returns immediately. If slots are full, DO NOT auto-retry — ask the user whether to delete an existing checkpoint or increase capacity. |
| vigil_listA | List all checkpoints and disk usage. With name: list files inside that checkpoint. |
| vigil_diffA | Search and investigate previous versions of your codebase. Compare checkpoint vs current working directory (with full unified diffs), compare two checkpoints against each other, retrieve any file's content from any checkpoint, or search for a string across all checkpoints to find when code existed. Use this to find previous versions of files or functions, understand what changed, and pull out whatever snippets or diffs are needed — then apply selectively with Edit. |
| vigil_restoreA | Restore project to a checkpoint state. Quicksaves current state first. Displaced files (modified + new) are preserved in .claude/vigil/artifacts/ — nothing is ever deleted. For individual file/function restores, use vigil_diff to get the content and apply with Edit. |
| vigil_deleteA | Delete a checkpoint and reclaim disk space. Use all=true to delete all checkpoints. Note: artifact directories from previous restores are NOT deleted — ask the user if they want you to clean those up separately. |
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 5 tools
Each tool targets a distinct operation on checkpoints: save, list, diff, restore, delete. There is no functional overlap, and descriptions clearly differentiate them.
All tools follow the 'vigil_verb' pattern with snake_case (e.g., vigil_save, vigil_list). The naming convention is uniform and predictable.
With 5 tools, the server is well-scoped for checkpoint management. Each tool covers a core function without redundancy or missing essential operations.
The tool set provides full lifecycle coverage: create (save), read (list), inspect (diff), update (restore), and delete. No obvious gaps for the domain of checkpoint management.