How do I install Sync82?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Sync82 need an API key?

No required environment variable is listed on this record.

What transport does Sync82 use?

Sync82 runs locally over stdio.

When was Sync82 last checked?

Last checked 2026-11-10. Persistent, structured project memory for AI coding agents, stored locally in SQLite.

Sync82 MCP server

Power your agent

Add this server

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code Run on PlugMCP

Host a copy with our keys and logs.

Local command

mcpb https://github.com/oito2/mcp-sync82/releases/download/v1.3.1/sync82.mcpb

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add io.github.oito2-mcp-sync82 -- mcpb https://github.com/oito2/mcp-sync82/releases/download/v1.3.1/sync82.mcpb

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "io.github.oito2-mcp-sync82": {4      "command": "mcpb",5      "args": [6        "https://github.com/oito2/mcp-sync82/releases/download/v1.3.1/sync82.mcpb"7      ]8    }9  }10}

claude_desktop_config.json

Local · mcpbPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
Version: 1.3.1
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

sync82

🌐 Language: English · Português

sync82 is a Model Context Protocol (MCP) server that gives an AI coding agent persistent, structured memory of a software project across sessions — goals, architecture, tech stack, decisions, and progress, all stored locally and recalled automatically the next time the agent opens the project.

Overview
Prerequisites & Quick Installation
Client Setup
Update & Maintenance
Documentation
AI Usage in This Project
License

Overview

Memory is stored in an embedded SQLite database and ships as a single self-contained binary — no runtime toolchain, no npm package, just sync82 on your PATH. The agent reads and writes it through MCP tools; you talk to the agent in plain language.

Six standard memory files per project, plus any custom file, for projects and their subprojects (monorepos, plugin ecosystems).
Automatic project discovery — a .sync82.json in the workspace means the agent never has to name the project again.
19 MCP tools — load a whole project's context in one call, save a session in one call, search the whole vault, archive old history, export/import plain Markdown — plus read-only MCP resources with each project's memory and start_session/end_session prompts.
One-step client setup — sync82 install registers sync82 in Claude Code, Claude Desktop, Antigravity, Codex, OpenCode, Cursor, Zed and Cline; sync82 uninstall removes it.
Local and private — stdio transport only, no network service, one SQLite file per vault.
Verifiable releases — SHA-256 checksums, a Sigstore signature and GitHub build provenance attestations; a Claude Desktop extension (sync82.mcpb) and an MCP Registry entry.

File	Kind	Purpose
`memory`	overwrite	Project overview: name, description, goal
`architecture`	overwrite	Components and how they fit together
`stack`	overwrite	Languages, frameworks, infrastructure
`decisions`	append-only, dated	Decisions made and why
`progress`	append-only, dated	Work completed, session by session
`next_steps`	overwrite	What to do next

Tools (19)

The AI agent calls these over MCP — it never touches the database directly. Full parameter reference in Tools Reference.

Tool	What it does
`list_projects`	List every project and subproject in the vault
`create_project`	Create a new project or subproject
`delete_project`	Permanently delete a project or subproject (requires confirmation)
`rename_project`	Rename a project or subproject in place
`get_vault_config`	Report the active vault path and config
`list_files`	List every memory file recorded for a project
`read_memory`	Read a memory file's content
`write_memory`	Overwrite a memory file's entire content
`append_memory`	Append a dated entry to `progress`, `decisions`, or a custom append kind
`delete_memory`	Delete a custom memory file (the six standard files are protected)
`edit_entry`	Replace, supersede or delete one entry of `progress`, `decisions`, or a custom append kind
`archive_memory`	Archive old dated entries, keeping only the last N days active, optionally with a summary of them
`search_memory`	Search memory files by words (accents and case ignored, best matches first), phrase or exact text
`load_project_context`	Load a project's memory (current state plus recent history) into one context block
`check_project_health`	Report which of the six standard files exist, and warn about files that look out of date
`init_project_memory`	Guided initialization, with optional auto-detection from the codebase
`update_project_memory`	Save a session's work (progress, decisions, next steps, etc.) in one call
`export_memory`	Export a project's memory to plain `.md` files on disk

list_projects, list_files, check_project_health and search_memory also return JSON (format: "json"). Besides tools, sync82 serves each project's memory as MCP resources (sync82://projects/<project>/context) and two MCP prompts, start_session and end_session. Not sure what to type to your agent? See Example Prompts.

CLI commands

Command	What it does
`sync82` (no args)	Start the MCP server over stdio — this is what your client launches
`sync82 install [target]`	Wire sync82 into one or all supported MCP clients
`sync82 uninstall [target] [--purge]`	Remove sync82 from one or all clients; `--purge` also deletes `~/.sync82` files after a separate confirmation
`sync82 config set-vault\|get-vault\|unset-vault`	Manage the global vault path override
`sync82 self-update [--check] [--yes] [--require-signature] \| --rollback`	Check GitHub Releases and update the binary in place, verifying the signature when `cosign` is installed (`--rollback` restores the previous version)
`sync82 export <project> [subproject] <output-dir>`	Dump a project's memory to plain `.md` files (`--all` for the whole vault)
`sync82 import <project> [subproject] <input-dir> [--dry-run]`	Restore a project's memory from plain `.md` files (the inverse of `export`); `--dry-run` only reports what would change
`sync82 search <query> [--project P] [--json]`	Search the memory, like the `search_memory` tool
`sync82 context <project> [subproject] [--full]`	Print a project's memory, like the `load_project_context` tool
`sync82 health <project> [subproject] \| --all`	Check a project, or every project, for missing files and out-of-date memory
`sync82 help` / `--help` / `-h`	Print the list of subcommands
`sync82 version` / `--version` / `-v`	Print the installed version

Full flags, exit codes, and examples for every command: CLI Reference.

Prerequisites & Quick Installation

Prerequisites: Linux, macOS, or Windows (amd64/arm64) — a release binary needs nothing else; building from source needs a Go toolchain matching go.mod (1.26+). You'll also need an MCP client (see Client Setup). Claude Desktop users can skip this section and install the .mcpb extension instead.

Two ways to get the binary on any OS — either works, but don't mix update mechanisms (see CLI Reference — self-update).

Linux

Prebuilt binary (no Go toolchain needed):

curl -LO https://github.com/oito2/mcp-sync82/releases/latest/download/sync82_linux_amd64   # or sync82_linux_arm64
curl -LO https://github.com/oito2/mcp-sync82/releases/latest/download/checksums.txt
sha256sum -c checksums.txt --ignore-missing   # must print "sync82_linux_amd64: OK"
chmod +x sync82_linux_amd64
sudo mv sync82_linux_amd64 /usr/local/bin/sync82

From source (requires Go 1.26+ — download it from go.dev/dl; distribution packages such as Debian/Ubuntu's golang-go are usually older):

go install github.com/oito2/mcp-sync82/cmd/sync82@latest

macOS

Prebuilt binary (no Go toolchain needed):

curl -LO https://github.com/oito2/mcp-sync82/releases/latest/download/sync82_darwin_arm64   # Intel: sync82_darwin_amd64
curl -LO https://github.com/oito2/mcp-sync82/releases/latest/download/checksums.txt
grep ' sync82_darwin_arm64$' checksums.txt | shasum -a 256 -c   # must print "sync82_darwin_arm64: OK"
chmod +x sync82_darwin_arm64
sudo mv sync82_darwin_arm64 /usr/local/bin/sync82

From source (requires a Go toolchain — brew install go):

go install github.com/oito2/mcp-sync82/cmd/sync82@latest

Windows

Prebuilt binary (no Go toolchain needed — PowerShell):

$base = "https://github.com/oito2/mcp-sync82/releases/latest/download"
Invoke-WebRequest -Uri "$base/sync82_windows_amd64.exe" -OutFile sync82_windows_amd64.exe
Invoke-WebRequest -Uri "$base/checksums.txt" -OutFile checksums.txt
$expected = ((Select-String -Path checksums.txt -SimpleMatch "sync82_windows_amd64.exe").Line -split '\s+')[0]
if ((Get-FileHash sync82_windows_amd64.exe -Algorithm SHA256).Hash -ne $expected) { throw "checksum mismatch" }
New-Item -ItemType Directory -Force "$env:LOCALAPPDATA\sync82" | Out-Null
Move-Item sync82_windows_amd64.exe "$env:LOCALAPPDATA\sync82\sync82.exe"
# add $env:LOCALAPPDATA\sync82 to PATH: System Properties > Environment Variables

From source (requires a Go toolchain — installer):

go install github.com/oito2/mcp-sync82/cmd/sync82@latest

Every release ships a checksums.txt (verified in the steps above), a Sigstore bundle signing it (checksums.txt.sigstore.json), and a GitHub build provenance attestation for every binary and the .mcpb bundle (gh attestation verify <file> --repo oito2/mcp-sync82) — see the Installation Guide.

go install/go build produces the final binary directly, ready to run — make sure $(go env GOPATH)/bin (or %GOBIN%/$GOBIN) is on your PATH; check with which sync82 (where sync82 on Windows).

Client Setup

sync82 install            # lists the detected clients, asks to confirm, configures each of them
sync82 install claude     # configure a single client instead

Targets: claude, claude-desktop, antigravity, codex, opencode, cursor, zed, cline. Each client is registered with the absolute path of the sync82 binary you ran, so run sync82 install again if you move the binary. Each target prints configured. or updated.; a client that isn't detected (its command on PATH or its config directory) is skipped.

Claude Code by hand (user scope, every project):

claude mcp add --scope user sync82 -- /usr/local/bin/sync82   # the path printed by `which sync82`
claude mcp list

Claude Desktop — no binary needed: download sync82.mcpb and install it from Claude Desktop's Settings → Extensions → Advanced settings → Extension Developer → Install Extension…. sync82 is also listed in the MCP Registry as io.github.oito2/mcp-sync82.

Per-client guides, with manual configuration and troubleshooting: Claude Code · Claude Desktop · Antigravity · Codex · OpenCode · Cursor · Zed · Cline. Any other client just needs command set to the binary's absolute path — see Installer.

Update & Maintenance

sync82 self-update --check   # report whether a newer release exists (exit code 10 when one does)
sync82 self-update           # download, verify (signature with cosign, SHA-256) and install the latest release
sync82 self-update --rollback   # restore the previous version, kept as <binary>.bak

self-update works on a release binary or a go install .../[email protected] build. If you installed with go install, update with go install github.com/oito2/mcp-sync82/cmd/sync82@latest instead — don't mix the two. The Claude Desktop extension is updated by installing a newer sync82.mcpb. A release can upgrade the vault schema (1.1.0 and 1.2.0 do); once the new version has opened a vault, the previous binary — including one restored by --rollback — refuses that vault, so update every client that shares it and don't roll back past such a release (see Troubleshooting).

To remove sync82 from every detected client, run sync82 uninstall (add --purge to also delete the default vault and config in ~/.sync82) — see Uninstallation for the complete removal, binary included.

Documentation

The documentation site has the full detail (also in Portuguese):

Installation · Quickstart · Uninstallation
Concepts — Architecture and internals
Reference: Tools · Resources · MCP Prompts · CLI · Configuration
Example Prompts · Usage Examples
Troubleshooting · Changelog

Contributing: see CONTRIBUTING.md for the development workflow, the checks CI runs (go build ./..., go vet ./..., gofmt -l ., golangci-lint, go test ./... -race, govulncheck), and how releases are published. Everyone participating is expected to follow the Code of Conduct.

AI Usage in This Project

This project was developed with the assistance of generative AI tools:

Scope: Generation of boilerplate, unit tests and refactoring of helper functions.
Oversight: All generated code was manually reviewed, tested and validated before integration.

License

GPL-3.0 — see LICENSE.

Add this server

Host a copy with our keys and logs.

Server facts

Tools

Questions

How do I install Sync82?

Does Sync82 need an API key?

What transport does Sync82 use?

When was Sync82 last checked?

Documentation

sync82

Table of Contents

Overview

Tools (19)

CLI commands

Prerequisites & Quick Installation

Linux

macOS

Windows

Client Setup

Update & Maintenance

Documentation

AI Usage in This Project

License