Publish Deed through the official MCP Registry - #982
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
Prepares Deed 0.2.12 for publication via the official MCP Registry by adding Registry metadata (server.json) and ensuring the published deed-lang Cargo package exposes the expected README ownership marker and correct minimum Rust version metadata.
Changes:
- Added
server.jsondescribingdeed mcpas a Cargo-installed stdio MCP server for the official Registry. - Shipped a crate-level README for
deed-lang(with themcp-name:ownership marker) and wired it into crates.io metadata. - Bumped workspace and lockfile versions to
0.2.12and updated documentation/changelog accordingly.
Reviewed changes
Copilot reviewed 7 out of 8 changed files in this pull request and generated no comments.
Show a summary per file
| File | Description |
|---|---|
| server.json | Adds official MCP Registry server metadata pointing at the deed-lang Cargo package and deed mcp entrypoint. |
| README.md | Updates install/version examples and documents the official Registry name. |
| crates/deed-cli/tests/registry.rs | Adds an integration test to keep Registry metadata + README ownership marker in sync with published crate metadata. |
| crates/deed-cli/README.md | Adds the crate README including the mcp-name: ownership marker required by the Registry. |
| crates/deed-cli/Cargo.toml | Sets readme = "README.md" so crates.io metadata points at the shipped crate README. |
| CHANGELOG.md | Adds the 0.2.12 release entry describing the Registry/README changes and Rust 1.88 minimum. |
| Cargo.toml | Bumps workspace version and internal dependency versions to 0.2.12. |
| Cargo.lock | Updates locked package versions to 0.2.12. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What this changes
Prepares
0.2.12for the official MCP Registry.server.jsondescribes the existingdeed mcpstdio command through thedeed-langCargo package, and the package now ships a short README with the visible ownership marker the Registry validates.The patch release also puts the corrected Rust 1.88 minimum into crates.io metadata. The published
0.2.11package still reports 1.85.Why this way
The Registry now supports crates.io directly. Deed already ships there, so a Cargo package plus the fixed
mcpargument is the smallest honest distribution path. A focused test keeps the Registry name, package name, version, transport, argument, and README marker together.What it still does not do
The Registry entry cannot be published until
deed-lang 0.2.12exists on crates.io. That happens after this release commit merges.Checks
cargo fmt --checkcargo clippy --workspace --all-targets -- -D warningscargo nextest run --workspace --profile ci --no-fail-fast(2522 passed, 4 skipped)cargo test --doc --workspace(11 passed)cargo check --workspace --lockedcargo publish --workspace --dry-run --locked(20 packages)mcp-publisher validate --file server.json