MCP in Claude Desktop is currently a beta feature.
The Model Context Protocol (MCP) is an open protocol that enables seamless integration between LLM applications and external data sources and tools. With the introduction of desktop extensions (DXT), installing and managing local MCP servers has become significantly easier.
Desktop Extensions
Desktop extensions provide a streamlined way to install and manage local MCP servers through single-click installable packages. Instead of manually configuring JSON files and managing dependencies, you can now install local MCP servers on your computer as easily as browser extensions.
Note: We’re building a directory of desktop extensions – if you’re a developer hoping to add an extension you built to the directory, complete our desktop extensions interest form to share more information with us.
Installing Desktop Extensions
Navigate to Settings > Extensions within Claude Desktop.
Browse the extension directory or install from a .dxt file.
Click "Install" on your desired extension.
Configure any required settings (like API keys) through the user-friendly interface.
The extension will automatically be available in your conversations.
Desktop Extension Installation Troubleshooting
Extension won't install
Ensure you're running the latest version of Claude Desktop.
Check that the extension file isn't corrupted by re-downloading it.
Verify you have sufficient disk space for the installation.
Extension appears installed but tools aren't available
Restart Claude Desktop to refresh the extension registry.
Check the extension's configuration settings for missing required fields.
Verify any API keys or authentication credentials are entered correctly.
Extension configuration issues
Navigate to Settings > Extensions and click on the extension to review its settings.
Ensure all required configuration fields are completed.
Check that file paths (if applicable) point to existing directories you have access to.
Permission or security errors
On macOS, check System Preferences > Security & Privacy if you receive security warnings.
On Windows, ensure Claude Desktop has necessary permissions to access required directories.
For enterprise environments, verify that desktop extensions are enabled through your organization's policies.
Developer FAQ
How do I convert my existing MCP server to a DXT extension?
Add a manifest.json file to your MCP server directory with the required metadata.
Package it using the dxt pack command.
See the DXT documentation for detailed instructions.
What programming languages are supported for DXT extensions?
DXT extensions support Node.js, Python, and binary MCP servers. Claude Desktop includes a built-in Node.js environment, so Node.js installation isn't required.
How do I handle sensitive configuration like API keys?
Mark configuration fields as "sensitive": true in your manifest.json. Claude Desktop will automatically encrypt these values using the operating system's secure storage (Keychain on macOS, Credential Manager on Windows).
Can I distribute my DXT extension privately?
Yes, you can share .dxt files directly with specific users or teams. For broader distribution, you can submit extensions to the official directory.
How do I debug issues with my DXT extension?
Enable debug logging in Claude Desktop settings, check the extension logs in the Extensions settings panel, and refer to the MCP debugging guide for protocol-specific troubleshooting.
What happens when my extension needs updates?
Extensions from the official directory update automatically by default. For privately distributed extensions, users will need to install updated .dxt files manually.
Enterprise Policy Controls
Enterprise administrators can control desktop extensions through system policies:
macOS Enterprise Configuration
Configure desktop extensions through a property list file at
~/Library/Preferences/com.anthropic.Claude.plist:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
<key>isDxtEnabled</key>
<true/>
<key>isDxtDirectoryEnabled</key>
<false/>
<key>isDxtSignatureRequired</key>
<true/>
<key>dxtRegistry</key>
<string>https://registry.example.com</string>
</dict>
</plist>
Windows Enterprise Configuration
Configure desktop extensions through Windows Registry policies at HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Claude or HKEY_CURRENT_USER\SOFTWARE\Policies\Claude:
# Set machine-wide settings (requires admin privileges)
New-Item -Path "HKLM:\SOFTWARE\Policies\Claude" -Force
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Claude" -Name "isDxtEnabled" -Value 1 -Type DWord
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Claude" -Name "isDxtDirectoryEnabled" -Value 0 -Type DWord
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Claude" -Name "isDxtSignatureRequired" -Value 1 -Type DWord
Set-ItemProperty -Path "HKLM:\SOFTWARE\Policies\Claude" -Name "dxtRegistry" -Value "https://registry.example.com" -Type String
Enterprise Policy Options
isDxtEnabled (boolean): Enables or disables desktop extensions functionality
isDxtDirectoryEnabled (boolean): Controls access to the public extension directory
isDxtSignatureRequired (boolean): Requires cryptographic signatures for extension installation
dxtRegistry (string): Specifies a custom extension registry URL for internal distribution
Note: Machine-wide settings take priority over user-specific settings when both are present.
Interested in learning more about MCP?
For more in-depth information on building your own MCP clients and servers, we recommend reviewing the following resources:
MCP Quickstart Guide - A step-by-step tutorial perfect for getting started with basic MCP integration
Model Context Protocol Github - Contains the complete technical documentation, code examples, and implementation guides
Guide to debugging MCP integrations - Troubleshooting tips and solutions for common implementation challenges
If you need further guidance, visit our guide on How to Get Support for additional support options.