# borgmcp 4.3.0

Package

• npm: borgmcp@4.3.0
• Integrity: sha512-MGskQIZ8H9rXqbWGe/nwTkWqsmLjohDSYSCp+YuQ84S7PRxy916++39LPNrJGJ6PDWOKsuSMZhckLllQta79Xg==
• Published with npm Trusted Publishing.

Source

• Tag: v4.3.0
• Commit: a76ba762532f8c5442aeedb5ea2f27fb217b3ae6

News and fixes

borgmcp 4.3.0

• borg_create-cube can now create a repository-bound cube over MCP. On 4.2.3 the tool never exposed or sent a repository identity: its request carried only retry_key, name, and template, omitting the wire-required working_repo_name and repository fields, so the server's shared request decoder rejected the call with a 400 and no cube could be created (#499). 4.3.0 adds a required, explicit repository argument — a canonical git remote URL (homed as an origin identity) or a UUID identifying a local, no-remote repository — plus an optional working_repo_name (defaulting to the URL's repository segment; required when repository is a local UUID), and threads both wire-required fields. The server homes one cube per repository, so when the given repository already has a cube the tool reports that existing cube and leaves its directive unchanged rather than overwriting it; the tool result now carries a result of created or resolved so callers can distinguish a new cube from an already-existing one. An optional post-create template is applied only to a newly created cube, never to an existing repository cube.