agent-checkpoint-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_CHECKPOINT_HOME | No | Override the default directory for the SQLite database (default: platform-specific data directory). |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| save_checkpointA | Save a progress checkpoint so any future agent session can resume exactly here. Call this after EVERY concrete sub-task (a file edited, a test passing, a command run) — not only when a numbered step finishes. Frequent, small checkpoints are the point: if the session dies mid-step, the next agent resumes from the last sub-task instead of redoing the whole step. Args: plan: The full numbered plan being executed (all steps, verbatim). current_step: 1-based number of the step currently being worked on. total_steps: Total number of steps in the plan. step_status: "in_progress", "done", or "blocked" — status of current_step. what_was_done: Everything completed so far, across all steps, specific enough that another agent will not redo any of it. what_remains: What is still missing IN THE CURRENT STEP, specific enough to be the very next action (plus any known remaining steps). project_dir: Optional project directory override; defaults to the server's working directory (walking up to the nearest .git root). |
| get_checkpointA | Get the latest checkpoint for this project — where to resume from. Call this FIRST when a task looks like a continuation of earlier work (e.g. after a session was cut off). It returns the plan, the current step, what was already done (do not redo it), and the exact next action. Args: project_dir: Optional project directory override; defaults to the server's working directory (walking up to the nearest .git root). |
| list_checkpointsA | List the checkpoint history for this project, newest first, with timestamps. Args: limit: Maximum number of checkpoints to return (default 20). project_dir: Optional project directory override; defaults to the server's working directory (walking up to the nearest .git root). |
| clear_checkpointsA | Delete all checkpoints for this project. Requires confirm=true. Called without confirm, it only reports how many checkpoints would be deleted; ask the user before calling again with confirm=true. Args: confirm: Must be true to actually delete. False = dry run. project_dir: Optional project directory override; defaults to the server's working directory (walking up to the nearest .git root). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/DiegoWare/agent-checkpoint-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server