May 2026 MCP guide

MCP Desktop Extensions Guide: DXT, MCPB, Claude Desktop, and MCP Apps

Desktop extensions make local MCP servers easier to install, but the naming and support model changed. Use this guide to decide when a package should be a desktop extension, when manual MCP config is enough, and when you are really building an MCP App.

What Is an MCP Desktop Extension?

An MCP desktop extension is a packaged local MCP server that a desktop client can install through a user interface. The practical benefit is simple: users do not need to manually edit configuration files, install developer dependencies, or guess which environment variables belong where. The extension packages metadata, configuration prompts, and server startup details into a repeatable install path.

In early documentation, these packages were commonly called DXT extensions. Anthropic later updated the naming convention so new Claude Desktop Extensions use the .mcpb file extension, short for MCP Bundle. Existing .dxt extensions can still work, but new pages should mention the current bundle naming to avoid sending readers down a stale setup path.

Naming check

DXT vs MCPB vs MCP Apps

TermCurrent useUse it when
DXTLegacy name that still appears in help docs and older packages.You are explaining older Claude Desktop extension packages or migration context.
MCPBCurrent Claude Desktop Extension bundle naming for new packages.You are documenting a new desktop extension package.
MCP AppsMCP extension for interactive views rendered by supporting clients.Your server needs a richer UI, not only easier local installation.

How to Calculate Extension Fit

Score each factor from 0 to 2. A package scoring 8 or higher is worth turning into a desktop extension. A package under 6 should usually stay as a manual MCP config until the workflow is proven.

Factor 1

Install friction

Score 2 when the extension removes manual JSON editing, dependency setup, and unclear restart steps for non-developer users.

Factor 2

Permission clarity

Score 2 when the package explains every filesystem, network, credential, and tool permission before the user installs it.

Factor 3

Support matrix fit

Score 2 when the target client officially supports the extension capability and your package has been tested there.

Factor 4

Update and rollback path

Score 2 when the team can update, disable, and remove the extension without editing hidden config by hand.

Factor 5

Debug visibility

Score 2 when logs, install errors, and protocol failures are visible enough for an operator to troubleshoot.

Decision matrix

SituationBest pathWhy
A single developer wants to test a trusted local MCP server.Manual MCP config can be enough.A one-off local test does not always justify packaging overhead.
A non-technical teammate needs the same local MCP server.Package it as a desktop extension or MCP Bundle.One-click install and UI-based settings reduce setup mistakes.
A team wants to distribute a vetted server internally.Use admin-controlled desktop extensions.Admins can control public extensions and make custom packages available to approved users.
The server needs an interactive UI inside the chat client.Evaluate MCP Apps, not only desktop packaging.MCP Apps are the extension path for interactive views, while desktop extensions package local MCP servers.

Worked Examples

Solo local server test

A developer wants to test a filesystem or database MCP server for one project. Manual MCP config is enough because the user can inspect the command, restart the client, and debug directly. Packaging can wait until the server proves useful.

Team install package

A support team needs the same internal docs MCP server. A desktop extension is the better path because install prompts can collect settings, admins can vet the package, and users do not need to copy JSON into hidden config files.

Failed install debug

An extension appears installed but tools do not show up. The operator should check extension logs, enable debug logging, confirm required settings, test the underlying server command, and verify the client still supports the extension capability.

Security and admin checklist

  • Review source ownership. Confirm the extension and underlying MCP server come from a trusted maintainer.
  • Map permissions. Document filesystem, network, credential, and command execution access before rollout.
  • Use least privilege. Create scoped API keys and avoid personal all-access tokens.
  • Check client support. Use official client matrix and client-specific docs before distributing a package.
  • Test uninstall and rollback. A safe package should be easy to disable without leaving stale server state.
  • Keep logs accessible. Operators need extension logs and MCP protocol errors for support.

Frequently Asked Questions

What is an MCP desktop extension?

An MCP desktop extension packages a local MCP server so users can install and configure it through a desktop client UI instead of manually editing MCP JSON config files and managing dependencies.

Is DXT still the right file extension?

DXT is still a recognized legacy term, but Anthropic updated Claude Desktop Extensions to use .mcpb, or MCP Bundle, for new packages. Existing .dxt extensions can still work, but new documentation should mention the current naming.

Are MCP desktop extensions the same as MCP Apps?

No. Desktop extensions primarily package local MCP servers for easier installation. MCP Apps are an extension to the MCP specification for interactive views and richer UI experiences inside supporting clients.

Do all MCP clients support desktop extensions?

No. Host support varies by client. Check the official MCP client matrix and the target client documentation before promising support.

Are desktop extensions safe by default?

No. They can run local code and may access credentials, files, or network services depending on the server. Teams should review source, permissions, install prompts, logs, and admin controls before rollout.

When should I package an MCP server as a desktop extension?

Package it when repeated setup friction is slowing users down, when non-developers need the server, or when a team wants a vetted internal install path with fewer manual steps.

How do I debug a failed desktop extension install?

Start with the client extension panel, enable debug logging if available, inspect extension logs, confirm required settings and dependencies, then test the underlying MCP server separately with a minimal local config.

Related resources

MCP Apps directory

Check interactive MCP app support and official-source links.

Best MCP servers

Shortlist servers before packaging one for desktop users.

Security guide

Use this when extension risk, proxy signals, or unknown-domain warnings appear.

Private catalog setup

Plan team-level MCP and skill catalog governance.

AE
AgentSkillsHub Editorial TeamAI Agent Infrastructure Reviewers

The AgentSkillsHub editorial team evaluates MCP servers, Claude skills, and AI agent integrations for security, reliability, and practical deployment readiness. Every listing undergoes permission audit, README analysis, and operational risk triage before publication.

  • Reviewed 450+ MCP server repositories
  • Developed security grading methodology (A-F)
  • Published agent deployment safety guidelines
Updated: 2026-05-22github