Skip to content

Conversation

@joan-anthropic
Copy link
Contributor

@joan-anthropic joan-anthropic commented Aug 21, 2025

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:

  • .dxt extension becomes .mcpb
  • the manifest.json schema deprecates dxt_version in favor of [TBD] manifest_json / $schema

Tested CLI commands:

  • Help
  • Validate (accepts both dxt_version (deprecated) and manifest_version)
  • Pack / unpack
  • Info
  • Clean
  • Init

alicelovescake
alicelovescake previously approved these changes Aug 21, 2025
Copy link

@alicelovescake alicelovescake left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Exciting changes!

@joan-anthropic joan-anthropic changed the title rename dxt -> mcpb chore: rename DXT -> MCP Bundle (MCPB) Aug 22, 2025
MANIFEST.md Outdated
```json
{
"dxt_version": "0.1", // DXT spec version this manifest conforms to
"mcpb_version": "0.1", // MCPB spec version this manifest conforms to
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the only breaking schema change

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.
alicelovescake
alicelovescake previously approved these changes Aug 26, 2025
domdomegg
domdomegg previously approved these changes Aug 27, 2025
Copy link
Member

@domdomegg domdomegg left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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)
@joan-anthropic joan-anthropic merged commit 241c65b into main Aug 28, 2025
6 checks passed
bthompson-sys pushed a commit to bthompson-sys/mcpb that referenced this pull request Oct 28, 2025
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.

5 participants