chore(release): 0.12.0 — ship MCP SDK with the bin - #43
Merged
Conversation
The published 0.11.0 tarball can't even start: it has @modelcontextprotocol/sdk in peerDependenciesMeta as optional, so consumers who install via `npx -y` or plain `npm i` never get the SDK, and the bin crashes immediately with `Cannot find module '@modelcontextprotocol/sdk/server/index.js'`. It was never really optional — the only thing this package ships is an MCP server. Move it to dependencies so it's always installed alongside the bin, and bump to 0.12.0 to reflect the new CLI surface that landed in #38–#42 (install/setup/uninstall/doctor subcommands + npx setup alias). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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
@modelcontextprotocol/sdkfrom optional peerDep → requireddependenciesso the published bin actually starts.agentmark-mcp install— auto-wire detected AI clients #38–feat(cli): npx-friendly setup —npx -y @thinkfleet/agentmark setup#42's new CLI surface:install/setup/uninstall/doctor).Why this is urgent
@thinkfleet/agentmark@0.11.0on npm is currently unusable. Smoke test:The SDK was listed in
peerDependenciesMetawithoptional: true, which meansnpm iandnpx -yskip it. But the only thing this package ships is anMCP server — the SDK is not optional in practice.
Fold the dep into
dependencies, drop the duplicate fromdevDependencies,clean up the meta entry. The MCP SDK has minimal transitive deps so package
size barely changes.
After merge
Tag +
npm publish0.12.0. Once it's live, ThinkFleet desktop's "AM" statuspill will flip from red → green because its
npx -y @thinkfleet/agentmark agentmark-mcp install --dry-runprobe will start working end-to-end.
Tests
npm run build— cleannpm test— 519 passed, 10 skipped (42 files)node dist/src/mcp/cli.js --help— full subcommand help rendersnode dist/src/mcp/cli.js install --dry-run— successfully detected & dry-wired Claude Code, Claude Desktop, Cursor, Windsurf on this machineFollow-up bug noticed
Codex CLI errors in dry-run because its config file is TOML, not JSON:
PR #38's
clients.tstreats every client config as JSON. I'll open a follow-upto either (a) skip Codex when its config is TOML or (b) teach the writer to
handle TOML. Not blocking this release.
🤖 Generated with Claude Code