Labsco
MCP SERVER

Give an assistant a memory of your ongoing projects, kept as plain markdown in a folder you own.

Agent Memory
Summary
Project memory you can read without the assistant.

State lives as markdown files in a folder you own, shaped as projects, tasks, sessions and notes rather than an opaque memory dump. The practical effect is that a new conversation starts with a project brief instead of five minutes of re-explanation.

What it is

An MCP server that stores projects, tasks, sessions and notes as markdown files on your own machine, so an assistant can pick up a months-long effort — a job search, a side project, a course — without being re-briefed. The workspace is a folder you can open in VS Code, Obsidian or vim.

What you get
  • Projects created and listed, filterable by status (project_create, project_list)
  • Full context for one project in a single call — description, open tasks, recent sessions (project_brief)
  • Tasks with priority, due date and notes, updatable and removable (task_add, task_list, task_update, task_delete)
  • A structured session entry: what you worked on, what you decided, what is next (session_log)
  • Timestamped notes dropped into a project as they occur to you (quick_note)
  • Six starter templates — generic, job-search, side-project, learning, writing, moving — that seed a project with tasks and a knowledge file
  • MIT licensed, with the workspace staying on your machine
Requirements

A current Node.js. One command — npx recap-mcp init — creates the workspace at ~/recap-workspace/, adds the entry to your Claude Desktop config and backs up the old one; then quit and reopen Claude Desktop.

Setup effort

One command — npx recap-mcp init