Desktop Extensions (DXT)

One-click local MCP server installation in desktop apps.

Rehe

anthropics

Other

Calculator (Rust Binary)

Model Context Protocol

A simple calculator MCP server compiled from Rust

Developer Tools

Hello World MCP Server (Reference Extension)

Model Context Protocol

A reference MCP extension demonstrating best practices and all available features

Developer Tools

Filesystem

Anthropic

Let Claude access your filesystem to read and write files.

Developer Tools

Control Chrome with AppleScript

Anthropic

Control Google Chrome browser tabs, windows, and navigation

Developer Tools

Python File Manager MCP

Anthropic

A Python MCP server for file operations

Developer Tools

Hello World (UV Runtime)

Anthropic

Simple MCP server using UV runtime

Developer Tools

FAQ

Frequently asked questions about MCP DXT and Desktop Extensions

What are Desktop Extensions (DXT) and how do they work with MCP servers?

Desktop Extensions (DXT) are a packaging format that bundles an entire MCP server — including all dependencies — into a single .dxt file. DXT solves the complex installation process by providing one-click installation in Claude Desktop and other MCP-enabled applications. A .dxt file contains a manifest.json for configuration, the server implementation files, and bundled dependencies, eliminating manual setup, developer tools, or dependency management.

How do Desktop Extensions (DXT) improve the MCP server installation experience?

DXT dramatically simplifies MCP server installation by eliminating common friction points: no developer tools required (Node.js is built into Claude Desktop), automatic configuration through manifest.json instead of manual JSON editing, bundled dependencies to avoid version conflicts, one-click installation, automatic updates, and secure storage of sensitive data in the OS keychain. Users simply download a .dxt file and double-click to install.

What types of MCP servers can be packaged as Desktop Extensions (DXT)?

DXT supports three main types of MCP servers: Node.js extensions (with bundled node_modules), Python extensions (with bundled lib packages), and classic binary/executable extensions. All types use the same manifest.json format for configuration and metadata, with cross-platform support for Windows and macOS and platform-specific overrides where needed.

What is the manifest.json file and how does it configure a DXT extension?

The manifest.json is the core configuration file for a Desktop Extension. It contains extension metadata, server configuration, user configuration requirements, and feature declarations, and supports template variables such as __dirname for the extension directory and user_config.key for user-provided settings. manifest.json is the only required file in a Desktop Extension.

How can developers create and package an MCP server as a Desktop Extension (DXT)?

Developers can create a DXT extension with the official toolchain: install with 'npm install -g @anthropic-ai/dxt', run 'dxt init' to scaffold the extension structure, implement the MCP server with @modelcontextprotocol/sdk, write a manifest.json with metadata and configuration, then run 'dxt pack' to produce the final .dxt file. The toolchain validates the manifest and produces a distributable package ready for one-click installation.

What are the security and enterprise considerations for Desktop Extensions (DXT)?

DXT includes several safeguards: sensitive data is stored in the OS keychain, automatic updates ship security patches, and users can audit installed extensions. For enterprises, DXT supports Group Policy (Windows) and MDM (macOS) management, pre-installing approved extensions, blocklisting specific extensions or publishers, disabling the extension directory entirely, and deploying private extension directories.