mem-sync
Sign up free

Walkthrough

Set up mem-sync for your team.

Seven steps on a hosted hub, about ten minutes. Each step has a short video. The text says the same thing, so you can skip the videos.

The hosted path

  1. Step 1

    Sign up and create your team

    Go to getmemsync.com/app. Enter your email and click Email me a sign-in link. Open the link in the same browser.

    Under Create a team, enter a Team name and a Hub address, like northwind.getmemsync.com. You can't change the address later. Click Create team.

    You are the team's first admin. The Overview page shows your hub address, the Connect Claude Code steps and a Create a machine key button.

    Your team starts with a 30-day free trial. See pricing for what comes after.

  2. Step 2

    Install the plugin

    Use Claude Code in a terminal, or the Code tab of the Claude desktop app. The desktop app's chat plugin screen won't work. Send each line as its own message:

    /plugin marketplace add thedotmack/claude-mem
/plugin marketplace add devplusopsllc/mem-sync-plugin
/plugin install mem-sync@devplusopsllc

    The last line also installs claude-mem. Then start a new Claude Code session.

    You need Node 18 or later. mem-sync runs on Bun and offers to install it if it's missing.

    Install and connect a machine (steps 2 and 3).

  3. Step 3

    Connect a machine

    In Claude Code, ask:

    connect mem-sync to https://northwind.getmemsync.com

    mem-sync opens its settings page in your browser, at 127.0.0.1:37778. It asks for a machine key. On the portal's Overview, click Create a machine key, copy it, paste it and click Connect.

    If your hub is behind Cloudflare Access, the Cloudflare sign-in opens instead. Sign in with your work email. There is no key.

    One machine, several hubs

    On the settings page, open Hubs and click Add hub. Or ask Claude to connect to another address. Each folder belongs to one hub. Linking it to a space on another hub asks first, then moves it.

    Add a second hub and move a folder to it.

  4. Step 5

    Catch up

    On the settings page, open Catch up. Pick a space and a range, like Since my last visit. You get a card for each teammate.

    A card shows the branch, the commit and the pull request, like PR #42 · Open. The PR state is as of the last check, not live. Other branches show as +2 more. Each note has a branch · commit line. File paths start at the project folder.

    When your plan includes Ask, an admin turns it on in Settings. Then ask the space a question. The answer cites the notes it used.

    The PR needs the GitHub CLI (gh) signed in on the writer's machine.

    Catch up on a space, with branch and PR chips.
    Branch, commit and PR on a note, and the per-folder switch.

  5. Step 6

    Invite people

    In the portal, open People. Enter a Name and Email, pick Member or Admin, and click Add person.

    Use the email they sign in with. A Cloudflare sign-in from an email that isn't on People is refused.

    Then click Open hub admin on the Overview. Give each person the projects they work on. To give someone a machine key, use People there and click Issue key.

    Add a teammate and give them access.

  6. Step 7

    Use it in any Claude chat

    People also work in Claude desktop, claude.ai and the mobile app, where plugins don't run. The mem-sync connector brings your team's memory there. Nothing to install.

    1. On the portal's Overview, copy the address under Use in Claude desktop and claude.ai. It looks like https://northwind.getmemsync.com/mcp.
    2. In Claude, open Settings, Connectors, Add custom connector, and paste the address.
    3. Sign in with your work email and allow access.

    Now any chat can read your spaces' recent notes, search them, open a note, read the team standards, ask, and save a note. You see only the spaces you see on your machine. Notes you save reach your teammates on their next sync.

    In Claude Code, the same connector: claude mcp add --transport http mem-sync https://northwind.getmemsync.com/mcp

    Admins turn the connector on or off in the portal's Settings. It starts on, unless your team uses Cloudflare Access.

    Add the connector, ask in a chat, and save a note for the team.

For admins: projects, access and standards

These live in the hub admin. Open it with Open hub admin on the portal's Overview.

Projects and spaces

Create a project, add a space for each repo, and mark the main one.

Who sees which spaces

Give people all of a project's spaces, or only the ones they need.

Team standards

Write rules once in the hub admin. Every teammate's Claude follows them.

Bring your own domain and Cloudflare Access

Serve your hub on your own hostname, like mem-sync.northwind.dev. Then your own Cloudflare Access can protect it, and your team signs in with the login it already has. northwind.getmemsync.com keeps working for machine keys.

Add your domain

In the portal, open Settings. Under Custom domain, enter the Hostname and click Add domain. Add the records it shows at your DNS provider.

If your domain is on Cloudflare, make the CNAME proxied. The _acme-challenge records appear once Cloudflare creates them. There may be one or two.

Custom domain: records, Pending, then Verified.
TypeNameValue
CNAMEmem-sync.northwind.devfallback.getmemsync.com
TXT_cf-custom-hostname.mem-sync.northwind.devThe value shown in Settings
TXT_acme-challenge.mem-sync.northwind.devThe value shown in Settings, once Cloudflare creates it

Wait for Verified

The domain shows Pending with two lines. Each says what Cloudflare is waiting for. The page checks again every 30 seconds while it is Pending. Click Check again to check now.

When both lines are done, the domain shows Verified. Your hub address, the connect command and Open hub admin all use the new address.

mem-sync.northwind.devPending

Domain ownership: Waiting for the TXT record

Certificate: Waiting for Cloudflare to issue it (add the _acme-challenge TXT records; usually a few minutes)

mem-sync.northwind.devVerified

Domain ownership: Verified

Certificate: Issued

Put your own Cloudflare Access in front

The same steps are in the portal under Settings, How to set up Cloudflare Access, with your hostname filled in.

  1. 1

    Create the hub application

    In Cloudflare, open Zero Trust → Access controls → Applications → Create new application → Self-hosted and private. Destination: mem-sync.northwind.dev, no path. Use your policy for your people, or create one: Action Allow, Include Emails ending in @northwind.dev. Name it mem-sync hub, then Create.

  2. 2

    Create the discovery application

    Create a second Self-hosted application. Destination: mem-sync.northwind.dev, path .well-known/mem-sync. Add a policy named mem-sync discovery: Action Bypass, Include Everyone. Name the app mem-sync discovery. Machines read this small public file before signing in. It holds no notes.

  3. 3

    Copy the AUD tag

    Open the mem-sync hub application → Additional settings. Copy the Application Audience (AUD) Tag.

  4. 4

    Find your team domain

    Zero Trust → Settings → Team name and domain. It looks like northwind.cloudflareaccess.com.

  5. 5

    Turn it on in mem-sync

    In the portal's Settings, under Cloudflare Access, tick Sign in through your Cloudflare Access application. Paste the Team domain and the Application audience (AUD) tag. Click Save sign-in methods.

  6. 6

    Connect machines

    Add each teammate on People, with the email they use for Cloudflare. They ask Claude Code to connect mem-sync to https://mem-sync.northwind.dev and sign in with Cloudflare in the browser.

Cloudflare decides who reaches the hub, so keep the hub policy narrow. mem-sync then lets in only people on People.

The six Access steps. The Zero Trust screens are a labelled mock.
Why Cloudflare Access, and how teammates sign in.
Sign up freeBook an onboarding call