Claude Code

Claude Desktop v6.28899.2 rolls back the MCP block for Chat and Cowork

2 min read AI-generated

A new setting called desktopMcpServersListScope now decides whether admin lists reach local servers. Plus Claude Code 2.1.329 and managed settings in the Admin API.

Featured image for "Claude Desktop v6.28899.2 rolls back the MCP block for Chat and Cowork"

Shortly after v6.6395.0 comes the next desktop release, and it reverses a change I wrote about on Wednesday. Back then, the managed lists allowedMcpServers and deniedMcpServers suddenly applied to local MCP servers under Settings > Developer as well, in Chat and Cowork. A denied server stopped after the update.

What v6.28899.2 changes

According to the changelog dated November 19, the old behavior is back: in Chat and Cowork the lists don’t apply to servers under Settings > Developer, and stopped servers run again. Admins who want the stricter version set desktopMcpServersListScope to all wherever they define the lists.

More for admins:

  • PostToolUse hooks from managed settings no longer run for tool calls that were refused before the tool started. Logs written by those hooks lose those entries.
  • Plugins turned on in managed settings that have their own git repository now actually install. That adds git and npm traffic unless nonessential traffic is turned off.
  • On Windows, the app can take about six hours instead of 30 minutes to notice new registry settings, unless it’s fully restarted.
  • After a long outage such as a dropped VPN, the app keeps retrying remote MCP servers in the background for about a day.

The bundled Claude Code version is 2.1.328.

Claude Code 2.1.329 and the Admin API

Claude Code 2.1.329 landed on npm the same day, and it’s also heavy on managed settings. If hooks from managed settings fail to load, Claude Code now shows a warning in the conversation in Claude Desktop and other non-interactive hosts. The folder trust dialog tells you where that folder’s hooks are declared. /tasks now also lists scheduled tasks, /loop wakeups and forks of the conversation. Among the fixes: ~/.claude.json could reset to defaults after a network stall, and /code-review <pr number> now reads the pull request through gh pr diff.

At the same time, the Python (2.11.0) and TypeScript (1.11.0) SDKs add a new Admin API feature: Claude Code managed settings.

Managed settings are becoming an admin tool

The rollback shows how touchy these lists are. A rule an admin wrote for Claude Code turned off local servers in Chat and Cowork for a while. Now the admin has to opt in to that. With the Admin API, these settings can also be managed programmatically. If you roll out Claude across an organization, check after this update that your lists still do what you think they do.

Sources

Claude DesktopClaude CodeCoworkMCPAdmin