You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
CLI has no concept of .mcpb extensions or the Extensions management UI
There's no built-in mechanism for organizations to auto-update managed .mcpb extensions — orgs have to build their own update infrastructure (e.g., scheduled scripts that compare SHA256 digests against a release and re-extract into the Extensions directory)
Request
Unify both systems so that organizations get a single, complete management plane:
CLI should support .mcpb extensions the same way Desktop does
Built-in auto-update for managed extensions — when an organization distributes .mcpb files, there should be a native mechanism to check for and apply updates without requiring custom deployment scripts
Single config surface — one place where orgs can define which MCPs are installed, what permissions they get, and how they're updated
Problem
Claude Code Desktop and Claude Code CLI each have half of a great enterprise MCP management story, but they don't share capabilities:
Claude Code Desktop has excellent
.mcpbextension support:extensions-installations.jsonwith version hashesClaude Extensions Settings/.mcpbfiles to usersClaude Code CLI has
managed-settings.json:/Library/Application Support/ClaudeCode/managed-settings.jsonBut neither product has access to the other's capabilities:
managed-settings.jsonfor permissions (see Claude Code Desktop should honor managed-settings.json for all permissions #30953).mcpbextensions or the Extensions management UI.mcpbextensions — orgs have to build their own update infrastructure (e.g., scheduled scripts that compare SHA256 digests against a release and re-extract into the Extensions directory)Request
Unify both systems so that organizations get a single, complete management plane:
managed-settings.jsonfor permissions (already filed as Claude Code Desktop should honor managed-settings.json for all permissions #30953).mcpbextensions the same way Desktop does.mcpbfiles, there should be a native mechanism to check for and apply updates without requiring custom deployment scriptsRelated Issues