Recap AI coding sessions (Claude Code, Codex, dsh, OpenCode): intent, decisions, open threads.
MCPpedia last refreshed this data
io.github.BruceXcluding/session-recap is an MCP server that recap AI coding sessions (Claude Code, Codex, dsh, OpenCode): intent, decisions, open threads. Its tool list has not been published yet over stdio, requires no API key, and scores 89/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"io-github-brucexcluding-session-recap": {
"args": [
"-y",
"session-recap"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Recap AI coding sessions (Claude Code, Codex, dsh, OpenCode): intent, decisions, open threads.
Run this in your terminal to verify the server starts. Then let us know if it worked - your result helps other developers.
npx -y 'session-recap' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked session-recap against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in ai-ml
A cross-platform desktop application for managing AI Agents and MCP Servers. 一款用于管理AI智能体与MCP服务器的跨平台桌面应用程序。
An open-source AI agent that brings the power of Gemini directly into your terminal.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
🛡️ BLA (Blind LLM Agents) — Adversarial defense shield that protects binaries, Electron apps, JS bundles, Python, and WebAssembly against AI reverse-engineering agents like REA. Poison -> Exhaust -> Hallucinate.
MCP Security Weekly
Get CVE alerts and security updates for io.github.BruceXcluding/session-recap and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Remember what every AI coding session was for.
intent · key decisions · what changed · open threads · where to resume, for sessions of any length, from any agent, through MCP, a local viewer or a plugin
Projects grow, and so does the number of sessions in each one, often across several agents. After a few weeks a session is a 100 MB transcript you no longer remember: why you started it, what you decided, what was left half done.
session-recap reads a session's whole transcript and writes a short, structured recap. Use it from any MCP client (Codex, Cursor, Zed, Cline, Gemini CLI, OpenCode, Claude Code…), in a local viewer for every agent's sessions, from the command line, or through native plugins for Claude Code, dsh and Codex.
| Section | What it answers |
|---|---|
| Intent | What was I ultimately trying to achieve? |
| Key ideas and decisions | What did we choose, and why? Which alternatives were rejected? |
| What changed | Files, features, documents, commits, PRs |
| Open threads | What is unfinished, unverified or still a question |
| Where to resume | The most sensible next step today |
Every recap also has a Map: the phases the work went through (pivots marked) down to "you are here", the key decisions with what was turned down, and lists of what shipped, what is open and what was dropped. Recaps are written in the language you mostly write in.
npm install -g session-recap
session-recap mcp-config # prints the MCP entry for your client
session-recap serve # opens the local viewer
Then, in your agent: "Recap this session", "What was my last session in this project about?", "总结一下这个会话".
No API key needed. Through MCP, the agent you are talking to writes the recap with its own model; session-recap only reads and condenses the transcript. A model of session-