KeepGoing MCP Server
Automatically captures development checkpoints, branch context, and session history based on git commits and branch switches to provide AI assistants with persistent project memory.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@KeepGoing MCP ServerGive me a re-entry briefing on where I left off"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
@keepgoingdev/mcp-server
MCP server for KeepGoing.dev - a momentum companion for developers. KeepGoing helps you keep going on projects when you return after time away.
KeepGoing auto-captures checkpoints (what you were doing, what's next, which files matter) on git commits, branch switches, and inactivity. When you start a new session, your AI assistant reads your last checkpoint instead of re-inferring everything from scratch. Local-first, no account required.
Quick Setup
The easiest way to get started is with the installer, which installs the CLI globally and runs the setup wizard:
curl -fsSL https://keepgoing.dev/install.sh | bashFor a specific tool:
curl -fsSL https://keepgoing.dev/install.sh | bash -s -- claude
curl -fsSL https://keepgoing.dev/install.sh | bash -s -- vscodeClaude Code (manual)
Global (recommended) — works across all your projects:
claude mcp add keepgoing --scope user -- npx -y @keepgoingdev/mcp-serverPer-project — scoped to a single project:
claude mcp add keepgoing --scope project -- npx -y @keepgoingdev/mcp-serverThen run keepgoing setup claude to configure hooks and rules.
Cursor, Windsurf, and other tools
Add to your MCP config file (~/.cursor/mcp.json for Cursor, or the equivalent for your tool):
{
"mcpServers": {
"keepgoing": {
"command": "npx",
"args": ["-y", "@keepgoingdev/mcp-server"]
}
}
}Related MCP server: Heimdall MCP Server
Tools
Core
Tool | Description |
| Get your last checkpoint, next step, blockers, and branch context. Quick snapshot of where you left off. Accepts optional |
| Get a synthesized re-entry briefing with focus, recent activity, and suggested next steps. Accepts optional |
| Get recent session checkpoints in chronological order. Supports branch filtering and configurable limit. |
| See recently active files and branches across sessions. |
| Export your development context as a formatted prompt for another AI tool (chatgpt, gemini, copilot, claude, general). |
| Save a development checkpoint after completing a task or meaningful piece of work. |
Paid Add-ons
Tool | Add-on | Description |
| Decision Detection | Get recent high-signal commits with their category, confidence, and rationale. |
| Session Awareness | Get current live session tasks across multiple concurrent AI agent sessions. |
| Activate a KeepGoing license on this device. | |
| Deactivate the KeepGoing license on this device. |
How It Works
Add this MCP server to your AI coding assistant (Claude Code, Cursor, Windsurf, etc.)
Start coding. Use
save_checkpointfrom your AI assistant to capture what you did, what's next, and any blockersCome back anytime. Your AI assistant calls
get_momentumorget_reentry_briefingto pick up exactly where you left offOptionally, install the KeepGoing VS Code extension for automatic checkpoint capture on inactivity, git commits, and branch switches — no manual saves needed
All data is stored locally in a .keepgoing/ directory at your git root.
Requirements
Node.js 18+
The KeepGoing VS Code extension is optional — useful for auto-capturing checkpoints on git commits, branch switches, and inactivity, but the MCP server works standalone via
save_checkpoint
Links
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Shared project memory that keeps teammates and AI agents aligned across sessions.
- MayaMemoOAuthcom.mayamemo
Evidence-backed project memory and checkpoints for AI coding agents.
Shared memory for coding agents. Stop re-explaining your codebase every session.
One memory for every AI you work with: your rules, notes and decisions in your own Git repo.
Related MCP Servers
- AlicenseBqualityCmaintenanceProvides AI assistants with persistent memory of your project architecture, development history, and technical decisions, allowing them to give context-aware coding help without needing repeated explanations.1661 npm2MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI coding assistants with persistent, context-rich memory of a codebase, including documentation and git history, enabling recall across sessions.105Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to persist and restore context across sessions, preserving decisions, progress, files, and checkpoints. It supports topic-based channels, search, change tracking, git-aware correlation, batch operations, and shared memory across parallel sessions.143 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding assistants to persistently save, search, checkpoint, and restore project context across sessions, including decisions, progress, and file state. It supports shared channels, git-aware organization, and batch operations for long-running or parallel development workflows.143 npmMIT