Python File Manager MCP
A Python MCP server for file operations
Hello World MCP Server (Reference Extension)
A reference MCP extension demonstrating best practices and all available features
Control Chrome with AppleScript
Control Google Chrome browser tabs, windows, and navigation
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 new packaging format that bundles entire MCP servers—including all dependencies—into single .dxt files. MCP DXT solves the complex installation process by providing one-click installation in Claude Desktop and other MCP-enabled applications. DXT files contain a manifest.json for configuration, server implementation files, and bundled dependencies, eliminating the need for manual setup, developer tools, or dependency management. MCP DXT represents a fundamental shift in how users interact with local AI tools.
How do Desktop Extensions (DXT) improve the MCP server installation experience?
Desktop Extensions (DXT) dramatically simplify 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 process, automatic updates, and secure storage of sensitive data in the OS keychain. MCP DXT users simply download a .dxt file and double-click to install. The DXT format makes powerful MCP servers accessible to everyone—not just developers.
What types of MCP servers can be packaged as Desktop Extensions (DXT)?
Desktop Extensions (DXT) support three main types of MCP servers: Node.js MCP extensions (with bundled node_modules), Python MCP extensions (with bundled lib packages), and classic binary/executable MCP extensions. All MCP DXT types use the same manifest.json format for consistent configuration and metadata. The DXT specification ensures cross-platform compatibility across Windows and macOS, with platform-specific overrides available for different operating systems. MCP DXT enables package once, run anywhere that supports the DXT format.
What is the manifest.json file and how does it configure MCP DXT extensions?
The manifest.json is the core configuration file for Desktop Extensions (DXT) that contains MCP DXT extension metadata, server configuration, user configuration requirements, and feature declarations. It supports template literals like ${__dirname} for the extension directory and ${user_config.key} for user-provided settings. The MCP DXT manifest enables automatic server configuration, declares available tools and prompts, and provides human-readable information about the DXT extension's capabilities and requirements. MCP DXT manifest.json is the only required file in a Desktop Extension.
How can developers create and package MCP servers as Desktop Extensions (DXT)?
Developers can create Desktop Extensions (DXT) using the official DXT toolchain: install with 'npm install -g @anthropic-ai/dxt', use 'dxt init' to create the MCP DXT extension structure, implement the MCP server with proper tool definitions using @modelcontextprotocol/sdk, create a manifest.json for your MCP DXT extension with metadata and configuration, and use 'dxt pack' to generate the final .dxt file. The MCP DXT toolchain validates the manifest and creates a distributable package ready for one-click installation. MCP DXT extensions can be submitted to extension directories for community discovery.
What are the security and enterprise considerations for Desktop Extensions (DXT)?
Desktop Extensions (DXT) include several security safeguards: sensitive data is stored in the OS keychain, automatic updates ensure security patches, and users can audit installed MCP DXT extensions. For enterprises, DXT supports Group Policy (Windows) and MDM (macOS) management, ability to pre-install approved MCP DXT extensions, blocklist specific extensions or publishers, disable the extension directory entirely, and deploy private extension directories. The open-source MCP DXT specification and toolchain enable transparency and community review. MCP DXT extensions are designed with enterprise security in mind.