Sync82

What the sync82 MCP server does

The sync82 MCP server stores structured memory for software projects and subprojects in an embedded SQLite database. It is intended for AI coding agents that need to retain context between sessions, including a project's purpose, architecture, technology stack, decisions, completed work, and next steps.

Each project can contain six standard memory files: memory, architecture, stack, decisions, progress, and next_steps. The first three and next_steps are overwrite-oriented files, while decisions and progress hold dated entries. Custom memory files are also supported. A .sync82.json file in a workspace can identify the project automatically.

How it works

The sync82 MCP server is delivered as a single binary and communicates with an MCP client over stdio. The agent interacts through MCP tools rather than accessing SQLite directly. It can load a project's current state and recent history as one context block, save session updates in one operation, search memory by words or phrases, and archive older dated entries while retaining a selected period of active history.

The server also exposes each project's memory through MCP resources and provides start_session and end_session prompts. JSON output is available for project listing, file listing, health checks, and memory searches. Projects may be nested, which supports repositories with subprojects such as monorepos or plugin collections.

Setup and configuration

Install a release binary on Linux, macOS, or Windows for amd64 or arm64 systems, or build it with Go 1.26 or newer. No runtime toolchain or npm package is required when using a release binary. Starting sync82 with no arguments launches the MCP server over stdio.

The sync82 install command can register the server with Claude Code, Claude Desktop, Antigravity, Codex, OpenCode, Cursor, Zed, and Cline. sync82 uninstall removes a client registration, with an optional purge operation for local sync82 files. The CLI can also set, read, or remove a global vault path override. The repository does not specify environment variables required to run the server.

Tools and capabilities

The sync82 MCP server provides tools for:

• Creating, renaming, listing, and deleting projects and subprojects.
• Reading, replacing, appending to, editing, deleting, and archiving memory files.
• Initializing project memory with optional codebase detection.
• Saving progress, decisions, and next steps from a session.
• Loading project context and checking standard-file health.
• Searching memory with case- and accent-insensitive matching, phrase search, or exact text.
• Exporting memory to Markdown files and importing it back.

The six standard memory files cannot be deleted through the custom-memory deletion operation. Project deletion is permanent and requires confirmation.

Limitations and notes

The sync82 MCP server uses stdio only and does not provide a network service. Its memory is local to the configured SQLite vault, so sharing or synchronizing that vault is outside the stated server behavior. Export and import use plain Markdown files, which provides a filesystem-based transfer path. Releases include checksums and signing or provenance information according to the project documentation.