mcpb-bundle

Migrate legacy .dxt bundles to .mcpb with manifest verification and reference updates.

30|6|Updated May 25, 2026

Search Tags:#migration #packaging #manifest #bundle #mcpb #tdmcp

Ready to run

npx skills add https://github.com/Pantani/tdmcp --skill mcpb-bundle

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: mcpb-bundle
Source: https://github.com/Pantani/tdmcp/tree/main/.agents/skills/mcpb-bundle
Command: npx skills add https://github.com/Pantani/tdmcp --skill mcpb-bundle

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers migrate the MCP Desktop bundle from the legacy .dxt format to the newer .mcpb format, ensuring continuity of builds and compatibility with the packer and manifest schema.

Core Features & Use Cases

Migration guidance for .dxt to .mcpb bundles, including manifest verification, output naming updates, and npm script alignment.
Cross-reference sweep: updating docs, release notes, and asset references to reflect the new .mcpb format.
Use Case: Upgrading an existing tdmcp desktop bundle to the MCPB packaging standard to enable modern deployment workflows.

Quick Start

Migrate your legacy .dxt bundle to .mcpb by validating the manifest, renaming outputs, updating npm scripts, and sweeping references, then verify the build.

Frequently Asked Questions about mcpb-bundle

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I migrate an MCP bundle from .dxt to .mcpb?▼

Migrating an MCP bundle from .dxt to .mcpb requires validating the manifest schema, renaming output files, updating npm scripts, and sweeping cross-document references to ensure packer compatibility and safe, auditable changes.

What is the .mcpb format used for in desktop bundles?▼

The .mcpb format is the modern packaging standard for MCP desktop bundles, replacing the legacy .dxt format to enable modern deployment workflows and ensure continuity of builds with the packer and manifest schema.

Do I need MCPB tooling to verify the manifest during migration?▼

Yes, MCPB tooling is required to validate manifests, rename outputs, and sweep references during the .dxt to .mcpb migration, ensuring safe, auditable changes and compatibility with the packer and manifest schema.

What does a cross-reference sweep involve when upgrading to .mcpb?▼

A cross-reference sweep involves updating docs, release notes, and asset references to reflect the new .mcpb format, ensuring all cross-document references are aligned after renaming outputs and updating npm scripts.

How do I update npm scripts for a tdmcp desktop bundle migration?▼

Updating npm scripts for a tdmcp desktop bundle migration involves aligning script commands with the new .mcpb output naming and manifest schema, ensuring the build process validates correctly after the format change.

Can I migrate a .dxt bundle without updating cross-document references?▼

No, migrating a .dxt bundle to .mcpb requires sweeping cross-document references in docs, release notes, and assets, as leaving legacy .dxt references can break build continuity and packer compatibility.