Skip to content

Conversation

tuannvm
Copy link

@tuannvm tuannvm commented Aug 19, 2025

Summary

This PR adds DXT packaging support to mcp-remote, enabling single-click installation of remote MCP servers in compatible AI desktop applications.

Changes

  • Added manifest.json - DXT specification-compliant manifest for packaging mcp-remote as a desktop extension
  • Added Makefile - Simple build process with make dxt command to create .dxt packages
  • User Configuration - Single required field for remote MCP server URL with validation

Features

  • ✅ One-click installation - Users can install remote MCP servers without manual configuration
  • ✅ Universal compatibility - Works with Claude Desktop, Cursor, Windsurf, and other MCP clients
  • ✅ No local dependencies - Uses npx to fetch mcp-remote dynamically, no bundled code required
  • ✅ URL validation - Built-in validation ensures users enter valid HTTP/HTTPS URLs
  • ✅ Cross-platform support - Compatible with macOS, Windows, and Linux

Usage

For developers:

make dxt # Creates mcp-remote.dxt package

For end users:

  1. Install the .dxt file in their MCP client
  2. Enter their remote MCP server URL
  3. Start using remote tools immediately

Technical Details

  • Uses DXT schema version 1.0 specification
  • Leverages npx mcp-remote for dynamic package fetching
  • Minimal package size (only manifest + docs, no code bundling)
  • Follows DXT best practices for Node.js extensions

This change significantly improves the distribution and adoption of remote MCP servers by providing a standardized, user-friendly installation method.

@tuannvm tuannvm changed the title Generic DXT Package Support Add DXT (Desktop Extensions) support for easy MCP server distribution Aug 19, 2025
Signed-off-by: Tommy Nguyen <[email protected]>
@tuannvm
Copy link
Author

tuannvm commented Aug 19, 2025

image

@geelen
Copy link
Owner

geelen commented Aug 27, 2025

Hey, nice idea, but how would you provide any of the CLI arguments required to configure a remote server with this method?

I'd have thought that any client modern enough to support DXT would also support remote MCP servers directly, no?

Finally, I'm not keen on adding the makefile, as I think people will expect that all the build flows are defined there. Maybe move the manifest to a /dxt subdirectory and add a build.sh script there, then invoke it from a script defined in package.json (like the rest of the build actions)

Copy link

pkg-pr-new bot commented Aug 27, 2025

Open in StackBlitz

npx https://pkg.pr.new/mcp-remote@140

commit: b15dd9d

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants