Back to search
project-continuity-mcp
MCP serverGitHub
Versioned project memory for agents across sessions, built as an MCP server.
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Badge for your README
Markdown
[](/listings/rayfzliu--project-continuity-mcp)HTML
<a href="/listings/rayfzliu--project-continuity-mcp"><img src="/api/listings/rayfzliu--project-continuity-mcp/badge.svg" alt="findsafeskills safety rating" /></a>Install
i
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 61 lines
- # Project Continuity MCP
- Local project continuity for agents: read the current project overview, resume an existing task workspace, find reviewed experience and versioned tools, and trace decisions back to changes and Git commits.
- **v0.2.0 is an open-source preview.** The Go executable embeds SQLite. Running the MCP service requires no Python, Go or separate SQLite installation. Git 2.31+ is required for repository operations. Individual toolbox assets may have their own dependencies; the service does not execute them automatically.
- ## Start
- 1. Extract the package for Windows amd64 or Linux amd64. Verify `SHA256SUMS`. On Linux, `chmod +x continuity-linux-amd64` if using the raw binary.
- 2. Run `continuity version`. Choose a persistent data directory outside your source repository.
- 3. Configure your client once; follow [INSTALL.md](INSTALL.md) for Codex, VS Code and SSH.
- 4. A maintainer explicitly registers a Git repository, reviews a meaningful initial overview proposal, and publishes C0 through the administrator CLI. Reading an overview never registers a project or creates a task workspace.
- ## A completely fictional example: Acorn Notes
- Acorn Notes is a made-up note importer used only to illustrate continuity. All IDs and paths below are placeholders, not records from a real project. Tests create their own synthetic repositories in temporary directories; no example database is distributed.
- **New agent reads the overview.** Ask the agent:
- ```text
- Use continuity.get_project_overview with cwd=/work/acorn-notes.
- Explain the current plan, verified progress, open questions and version boundaries.
- Do not create a task workspace merely because this is a new conversation.
- ```
- The overview might say: “Acorn Notes imports CSV notes; duplicate headers must be rejected; encoding detection remains unverified.” A fresh agent should distinguish those statements instead of interpreting a roadmap as implemented functionality.
- **Resume an existing workspace.** If the overview identifies a registered task, call `get_workspace(workspace_id)` and read its local README. Its workspace ID belongs to the task, not the conversation. A second session reuses that ID. If the workspace is archived, explicitly create a new task rather than silently reactivating it.
- **Find reusable experience and a tool.** Ask a differently worded question:
- ```text
- Which previous case explains ambiguous CSV column names?
- Search reviewed experience, retrieve the referenced csv-header-checklist@1,
- and explain its assumptions and dependencies before using it.
- ```
- An experience records the failure of accepting duplicate headers, the successful rejection rule, its scope, and source change/workspace IDs. `get_tool` returns the exact reviewed template version and SHA-256, not an automatically executed command. A newer tool version does not rewrite the old case's reference.
- **Trace the change.** Follow the experience's `source_change_ids` using `get_history`, then the source workspace. Compare the original selected commit, the integration mapping and validation evidence. Work notes and temporary tools are committed separately; only selected product commits enter integration.
- The executable tests this lifecycle with fictional `policy.txt` and `checklist.md` files: `go test ./internal/continuity -run TestFictionalLifecycle -v`.
- ## Two different version lines
- | Version | Meaning |
- |---|---|
- | Cluster C0, C1… | Reviewed overview tied to the local `integration` commit. It can lead the product release. |
- | Release R1, R2… | A separately confirmed exact commit and overview snapshot, frozen only after the service queries the specified remote ref and verifies equality. |
- C5 does not mean “release 5.” An agent proposal is not an integration or release. This project's GitHub package version `v0.2.0` is also separate from each managed project's C/R versions.
- ## Boundaries
- - Stdio JSON-RPC, local Git worktrees, SQLite schema v1 and versioned file toolbox. Compatible data layout with the preceding Python implementation; back up before switching versions. Git requires its own backup.
- - Maintainer CLI only: project registration, accepting integration, publishing overview, release confirmation, candidate review and workspace archive. Self-reported `actor` labels never grant permissions.
- - Same-OS-account deployment provides workflow and audit separation, not security isolation. Use separate accounts/storage permissions when stronger isolation is needed.
- - No automatic code execution on retrieval, no conversation capture, no cloud sync, no trading functionality and no knowledge graph.
- - Windows amd64 and WSL Ubuntu amd64 have been exercised. VS Code GUI and a real SSH server connection remain unverified; see [VERIFICATION.md](docs/VERIFICATION.md).
- Build with Go >=1.26: [BUILD.md](BUILD.md). API inventory: [API.md](docs/API.md). License: [MIT](LICENSE); dependencies retain their own [notices](THIRD_PARTY_NOTICES.md).
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.