Copilot that knows your project context
Connect the KeepGoing MCP server to GitHub Copilot. It gains access to your momentum, session history, and re-entry briefings, right inside VS Code.
Ask Copilot about your project context:
You:
What was I working on in this project?
Copilot:
Based on your KeepGoing data, you were last working on this project 3 days ago. You were refactoring the middleware to support JWT rotation. Your next step was to implement the verifyRefreshToken helper in auth.ts.
You touched 4 files on the feature/auth-refresh branch.
What Copilot can do with your context
Check your momentum
Ask "what was I working on?" and Copilot calls get_momentum to show your last checkpoint, next step, and branch context.
Browse session history
Ask "show my recent sessions" and Copilot calls get_session_history to display a timeline of your past work.
Get a re-entry briefing
Ask "help me pick up where I left off" and Copilot calls get_reentry_briefing to synthesize a complete briefing with a suggested first action.
Setup
Option A: From VS Code
If you have the KeepGoing extension installed, open the command palette and run:
KeepGoing: Set up GitHub Copilot MCP
This writes the MCP configuration to .vscode/mcp.json automatically.
Option B: Manual setup
Create or update .vscode/mcp.json in your project:
{
"servers": {
"keepgoing": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@keepgoingdev/mcp-server"
]
}
}
}How it works
The VS Code extension captures your coding context and writes it to .keepgoing/ in your project. This is the write side.
The MCP server reads that directory and exposes it to Copilot as tools. This is the read side. Copilot discovers the tools automatically and can call them during chat.
Both run locally. No cloud dependency, no accounts, no data leaves your machine.
Get started
Install the VS Code extension to start capturing context, then connect Copilot.