UVCS MCP 1.4.1

UVCS MCP 1.4.1

UVCS MCP 1.4.1 publishes the server to the official MCP Registry as io.github.ProAnima/uvcs-mcp. MCP clients and directories that read the registry can now find and install it. The server, its tools, and its behavior are unchanged from 1.4.0.

MCP Registry

• server.json describes the npm package @proanima/uvcs-mcp, its stdio transport, and the environment variables a client should ask for: UVCS_WORKSPACE (required), UVCS_MCP_MODE, UVCS_ALLOWED_WORKSPACES, UVCS_ALLOWED_REPOS, and UVCS_CM_PATH.
• package.json declares the matching mcpName, which the registry checks in the published package.
• Releases publish the registry entry automatically: the Publish workflow waits until npm serves the new version, verifies a pinned mcp-publisher with Sigstore, and publishes through GitHub OIDC.

Release tooling

• npm run release:check and a test fail when server.json drifts from package.json (name, versions, npm identifier, description length, icon, documented environment variables).
• The npm job skips npm publish when the version already exists, so the workflow can be re-run after a failed registry step.

Documentation

• docs/configuration.md describes UVCS_CHECKIN_MAX_FILES for path-scoped checkins and lists checkout and release checkout among the write timeouts.
• docs/publishing.md documents the registry job and how to check the entry.

Quality gate

• 171 automated tests (one POSIX-only test skipped on Windows), ESLint, syntax validation, release metadata check, fake and fleet smoke flows, and the packed-tarball smoke.
• server.json validated against the official schema and with mcp-publisher validate against the registry.

Upgrade

No action is needed for existing installations. To pin the new version:

npx -y @proanima/uvcs-mcp@1.4.1 init --client=claude-code --workspace="D:/Repositories/YourWorkspace" --safety=guarded

See the changelog and the publishing guide.