BEK / WorkspaceClaude pilot
Your work. A recoverable copy.

Keep building in Claude.
Keep your app versions here.

Use the connectors you already know. BEK adds a private place to save app source, exported records and earlier versions.

Microsoft sign-in setup pending

Connect once

  1. In Claude, add a custom connector named BEK Workspace. Your Claude team owner may need to add it first.
  2. Use this connector address:
    https://bek.ziptech.ai/mcp
  3. Sign in with your BEK Microsoft account and allow the backup tools.
  4. Add the BEK instructions to your Claude project.

For Claude Code: claude mcp add --transport http bek https://bek.ziptech.ai/mcp, then use /mcp to sign in.

Then ask normally

“Make a little travel request app and save a backup to BEK.”

“Show me the last version and undo that change.”

Claude should return a version number and say exactly what was saved. Your existing Expedia, Outlook and file connectors remain in Claude.

Know what your backup contains

Source + data includes supplied app files and a JSON export of its records. Source only preserves the app code but does not include its business records.

Only saves made through this connector are captured. Saved versions are private to your Microsoft identity. Restoring a BEK version preserves later versions; applying it to the running Claude artifact is a separate Claude step. This pilot does not automatically copy every artifact, publish apps, expose srOS administrator tools or back up external mailboxes and file shares.