AI makes mistakes! Undisk makes recovery instant: every write is versioned, every file is reversible.
See it heal →

​
SDK & Registry Integrations

Undisk publishes and syncs integrations across multiple ecosystems so teams can use the same versioned workspace semantics from their preferred runtime.
EcosystemPackage / ArtifactInstall / UseAutomation Status
npm@undisk-mcp/* (TypeScript SDK + clients)npm i @undisk-mcp/sdk or npx @undisk-mcp/setup-claudePublished from vX.Y.Z release workflow with strict drift checks
PyPIundisk-mcppip install undisk-mcpPublished by publish-python.yml (tag or workflow dispatch)
crates.ioundisk-mcpcargo add undisk-mcpPublished by publish-rust.yml with version-match enforcement
Go mirrorgithub.com/kiarashplusplus/undisk-mcp-gogo get github.com/kiarashplusplus/undisk-mcp-goSynced and auto-tagged (vX.Y.Z) by sync-go-sdk.yml
Docker MCP registrydocker/mcp-registry/server.yaml metadata bundleConsumed by external MCP registry indexersSynced to external registry repo by sync-docker-mcp-registry.yml
CI enforces release integrity with npm + cross-registry drift checks (PyPI, crates, and Go mirror tag presence) before deployment.

​
Release automation model

  • release.yml creates semver tag vX.Y.Z and dispatches publish workflows.
  • publish.yml handles npm workspace packages (affected-only or full).
  • publish-python.yml and publish-rust.yml enforce version parity before upload.
  • sync-go-sdk.yml mirrors Go SDK files and pushes matching vX.Y.Z tags in the mirror repo.
  • sync-docker-mcp-registry.yml syncs MCP registry metadata to an external repository.

​
Drift enforcement

CI fails when latest semver-tag versions are missing in required registries:
  • npm packages expected for release tags
  • PyPI package undisk-mcp
  • crates package undisk-mcp
  • Go mirror semver tag presence
Use this page as the source of truth when validating package distribution after each release.