Repository navigation
Pin am integrate to mcp-server 0.1.6 for cli-v0.4.0 - #76
Merged
Merged
Conversation
ethanj
approved these changes
Sep 30, 2026
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
2 participants
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.
Summary
Now that
@atomicmemory/mcp-server@0.1.6is live on npm (published from #75 at 15569c8), this moves theam integratepin from 0.1.5 to 0.1.6 so host MCP configs written by the CLI get hosted mode and the new default API URL resolution.This is the pin bump the comment in
crates/cli/src/integrate/spec.rscalls for: it lands after the matching npm publish, never ahead of it.Changes
crates/cli/src/integrate/spec.rs:MCP_SERVER_PACKAGEis now@atomicmemory/mcp-server@0.1.6crates/cli/tests/integrate_opencode.rs: expected pin updatedcrates/cli/README.mdandCHANGELOG.md: pin references updatedRelease plan
After merge, tag
cli-v0.4.0on the merge commit.release-cli.ymlpreflight re-checks that 0.1.6 resolves on npm before building. Cargo workspace version is already 0.4.0.