chore: rename DXT -> MCP Bundle (MCPB) - #92
Conversation
joan-anthropic
changed the title
| ```json | ||
| { | ||
| "dxt_version": "0.1", // DXT spec version this manifest conforms to | ||
| "mcpb_version": "0.1", // MCPB spec version this manifest conforms to |
There was a problem hiding this comment.
This is the only breaking schema change
There was a problem hiding this comment.
Possibly to avoid another breaking change, you could do the same thing we're doing in modelcontextprotocol/registry#308
tldr: instead of mcpb_version, use $schema pointing at a versioned JSON schema. This:
- makes it more obvious what exactly the file is for
- gives people nice IDE typehinting
- provides very clear versioning support
- is standards compliant
I think given we're moving this all to the MCP org anyway, happy for you to host on https://github.com/modelcontextprotocol/static (e.g. raise a PR like modelcontextprotocol/static#1). You can also just use a URL like https://static.modelcontextprotocol.io/schemas/2025-07-09/mcpb.schema.json then we can add the actual file later.
There was a problem hiding this comment.
Thanks @domdomegg for the suggestion! That makes the schema validation workflow a lot clearer, actually. Opened a PR here: modelcontextprotocol/static#2.
I'll update this PR to reflect the updated schema before merging
There was a problem hiding this comment.
Oh also - I'll call out that diff is slightly outdated, it's been updated mpcb_version -> manifest_version
This section was added alongside the rename but is not necessary for the dxt -> mcpb rename itself. Removing to keep the rename commit focused on just the naming changes.
There was a problem hiding this comment.
nice 🚀
maybe we should deprecate the @anthropic-ai/dxt package on NPM? if you don't have the creds, felix should have them.
also flagging this comment!
- Replace manifest_version with $schema field pointing to official schema URL - Support backward compatibility with legacy dxt_version field - Update all examples and tests to use new $schema field - Mark dxt_version as deprecated but still functional - Require either $schema or dxt_version (at least one must be present)
…e-dxt-mcpb chore: rename DXT -> MCP Bundle (MCPB)
4 participants
Context here
In order to achieve better semantic alignment between this project and its generated artifacts, we are planning on renaming dxt (desktop extensions) -> mcpb (mcp bundle).
The command-line utilities and zip archive output will largely functionally remain the same, with the following breaking changes:
.dxtextension becomes.mcpbdxt_versionin favor of [TBD]manifest_json/$schemaTested CLI commands: