---
title: How do you control Claude Desktop extensions and MCP connectors?
url: https://opencontroller.lyzr.com/blog/control-claude-desktop-extensions-and-connectors
published: 2026-11-12
updated: 2026-11-12
author: Lyzr
---

# How do you control Claude Desktop extensions and MCP connectors?

**Use two layers. In Claude's Organization settings, turn on the desktop extension allow-list so users can install only extensions you approve from the in-app registry. On managed devices, deploy Claude Desktop enterprise policy through MDM or Group Policy to switch off extensions, the extension directory or local MCP servers entirely. Device policy wins over organisation settings, so set it deliberately. Neither layer stops local tampering, so keep an inventory of what is actually installed.**

Claude Desktop can run local MCP servers, packaged as desktop extensions (`.mcpb` files) or configured by hand. That gives Claude access to files, apps and internal systems on the user's machine. This guide covers Anthropic's documented controls as of November 2026. It is one of our [platform governance guides](/blog/how-to-govern-ai-agents-across-platforms).

## How does the desktop extension allow-list work?

The allow-list is available to Owners and Primary Owners on Team and Enterprise plans. It is **disabled by default**; until it is on, users can access every extension in the registry.

To enable it: Organization settings → Connectors → Desktop tab → toggle Allowlist on.

Once it is on:

- Existing desktop extension installations are **force-deleted** from Claude Desktop clients.
- Users cannot install extensions that are not on the allow-list.
- Users can only install from the in-app registry. Drag-and-drop and click-to-install of `.mcpb` files stop working.
- Extensions removed during setup must be reinstalled by users, so Anthropic suggests enabling it during off-hours.

To add extensions, choose Browse extensions → select one → "Add to your team". For internal extensions, use "Add custom extension" and upload a `.mcpb` file; custom extensions are scoped to your organisation. To ship an update, increment the `version` in `manifest.json` and keep the `name` unchanged, then use "Upload new version". A changed name creates a new extension.

The allow-list needs Claude Desktop 0.13.91 or later.

## Which enterprise policy keys control extensions and MCP?

Claude Desktop reads policy from the `com.anthropic.claudefordesktop` domain on macOS (via a configuration profile from Jamf Pro, Kandji or Intune) and from `HKLM\SOFTWARE\Policies\Claude` or `HKCU` on Windows. If both Windows locations are set, HKLM wins.

| Key | Default | What it controls |
|---|---|---|
| `isDesktopExtensionEnabled` | true | Whether extensions can be used at all |
| `isDesktopExtensionDirectoryEnabled` | true | Access to the extension directory |
| `isLocalDevMcpEnabled` | true | Locally configured MCP servers |
| `isClaudeCodeForDesktopEnabled` | true | Claude Code access inside Desktop |
| `forceLoginOrgUUID` | not set | Requires sign-in to your organisation |
| `allowedWorkspaceFolders` | unrestricted | Folders users can mount to Cowork |
| `disableAutoUpdates` / `autoUpdaterEnforcementHours` | false / 72 | Update behaviour when MDM manages versions |

Two details catch teams out:

1. **Local MCP has two doors.** `isLocalDevMcpEnabled: false` blocks hand-configured local servers, but desktop extensions can still run local servers. To close both, block extensions too.
2. **Device policy overrides the allow-list.** If `isDesktopExtensionEnabled` or `isDesktopExtensionDirectoryEnabled` is set to false, the allow-list cannot populate the registry. Leave them unset or true if you want the allow-list.

On Enterprise, Organization settings also offer "Allow local MCP servers" and "Block all desktop extensions" toggles that give the same controls without MDM. If a device policy sets a matching key, the device policy wins, even when it is less strict.

## Which setup fits which organisation?

| Situation | Recommended setup |
|---|---|
| No local MCP needed | Policy: `isDesktopExtensionEnabled` false and `isLocalDevMcpEnabled` false |
| Curated extensions only | Org allow-list on; policy keys left at default; `isLocalDevMcpEnabled` false |
| Developer teams need local servers | Separate MDM group with `isLocalDevMcpEnabled` true, plus device inventory and sandboxing |
| Unmanaged devices | Org allow-list and `forceLoginOrgUUID`; accept weaker control |

## What do these controls not cover?

Anthropic notes that the allow-list does not prevent local tampering with MCP file contents after installation. A user with local admin rights can also edit config files. So you still need to:

- Find what is installed: [how to find local MCP servers on developer laptops](/blog/find-local-mcp-servers-on-developer-laptops).
- Sandbox servers that need broad access: [how to sandbox MCP servers](/blog/how-to-sandbox-mcp-servers).
- Review usage centrally: [how to audit Claude Enterprise usage](/blog/audit-claude-enterprise-usage).

## How Opencontroller does this

Opencontroller connects to Claude Enterprise workspaces and discovers and manages skills in Anthropic Enterprise. Opencontroller Edge, installed by IT via MDM, extends control to developer devices, coding agents, skills and local MCP servers, so Claude Desktop extensions appear in the same governed registry as hosted agents and tools. [Book a demo](https://www.lyzr.ai/book-demo/).

## Frequently asked questions

**What happens to installed extensions when you turn on the allow-list?**
They are force-deleted from Claude Desktop clients. Users then reinstall approved ones from the in-app registry.

**Does disabling local MCP servers also disable desktop extensions?**
No. `isLocalDevMcpEnabled` covers hand-configured local servers. Desktop extensions can still run local servers unless you block extensions as well.

**Which wins: MDM policy or Organization settings?**
The device policy. If a computer's policy sets a matching key, it overrides the Organization setting, even when it is less strict.

## Key facts

Claude Desktop extension allow-list: Team and Enterprise Owners, off by default, enabled in Organization settings > Connectors > Desktop; enabling it force-deletes existing extensions and blocks drag-and-drop .mcpb installs; needs Desktop 0.13.91+. MDM policy domain com.anthropic.claudefordesktop (macOS) or HKLM\SOFTWARE\Policies\Claude (Windows); keys include isDesktopExtensionEnabled, isDesktopExtensionDirectoryEnabled, isLocalDevMcpEnabled, forceLoginOrgUUID. Device policy overrides Organization settings. The allow-list does not prevent local tampering. Opencontroller connects to Claude Enterprise workspaces and Opencontroller Edge covers local MCP servers on devices. Opencontroller pricing starts from $250K per deployment per year.

## Related

- [How do you audit Claude Enterprise usage?](https://opencontroller.lyzr.com/blog/audit-claude-enterprise-usage.md)
- [How do you govern skills in Claude Team and Enterprise?](https://opencontroller.lyzr.com/blog/how-to-govern-skills-in-claude-team-and-enterprise.md)
- [How do you find local MCP servers on developer laptops?](https://opencontroller.lyzr.com/blog/find-local-mcp-servers-on-developer-laptops.md)
- [More on Platform Guides](https://opencontroller.lyzr.com/blog/cluster/platform-guides)
