CodeRecoder 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 |
|---|---|
| activate_projectA | Activate one project for this MCP process, create a verified baseline, and optionally start automatic checkpoints. Use storageRoot to keep all backup data outside a protected project. |
| deactivate_projectA | Create a final checkpoint by default, stop automatic monitoring, and clear this process-local active project. |
| get_backup_statusA | Report active-project storage, integrity evidence, pending changes, and automatic-checkpoint health. |
| create_project_snapshotA | Create an independently restorable, SHA-256-verified backup of the active project. Unchanged files may be deduplicated in storage. |
| list_project_snapshotsB | List verified backups newest first, including hashes, triggers, sizes, and change counts. |
| preview_project_restoreA | Verify a backup and calculate the restore change set. Returns a short-lived token; present the preview to the user before requesting confirmation. |
| restore_project_snapshotA | Destructively apply a previously previewed restore. Requires the matching unexpired confirmation token. A verified pre-restore safety backup and automatic rollback are mandatory. |
| verify_project_snapshotB | Re-hash the selected backup and validate entry types, paths, modes, and manifest integrity. |
| delete_project_snapshotA | Permanently delete one backup. Call only after explicit user approval and repeat the exact snapshot ID in confirmSnapshotId. |
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 9 tools
Each tool maps to a distinct lifecycle action (activate, deactivate, create, list, delete, verify, status, preview, restore). The only mild overlap is verify_project_snapshot versus preview_project_restore, since both re-hash/verify a backup, but the preview tool's added change-set and token behavior clarifies the boundary.
All tools follow a consistent snake_case verb_noun pattern (verify/delete/create/list/restore/preview_project_snapshot, activate/deactivate_project, get_backup_status). The noun shifts to the appropriate resource (project, snapshot, backup_status) without breaking the convention.
Nine tools is a well-scoped set for snapshot/backup management, with each tool earning its place across the full lifecycle without redundant operations.
The surface covers complete lifecycle coverage: activation/deactivation, snapshot creation, listing, verification, deletion, status inspection, and a safety-gated preview-plus-restore flow. No obvious dead ends or missing core operations for the backup domain.