Changelog
Back to All
Improved

MCP Server v0.0.1-beta.12

about 1 month ago by ReadMe API

Release target: replacement for withdrawn 0.0.1-beta.11, with the npm/npx binary startup fix, refreshed knowledge/vector package, and the internal staging/dev auth foundations from beta.11.

Why beta.12

0.0.1-beta.11 was published and then withdrawn after Claude failed to start the server through the npm package binary path (npx -y @convertcom/mcp-server@latest). npm package versions are immutable after publish/unpublish, so the replacement release must use a new version: 0.0.1-beta.12.

Highlights

  • Fixed npm package binary startup by resolving real paths before deciding whether src/index.ts is the main entrypoint.
  • Extended package smoke to launch the installed package binary (node_modules/.bin/convert-mcp, or convert-mcp.cmd on Windows), matching the npx/Claude failure mode instead of only testing node build/index.js.
  • Added durable operator notes for npm immutability, rollback/dist-tag handling, and binary-shim startup testing.
  • Refreshed packages/server/data/convert-kb.json from the canonical assistant HubSpot export.
  • Rebuilt the semantic vector store for 5,797 knowledge chunks.
  • Preserved required empty Zvec segment directories with tracked .gitkeep files so git/npm packaging keeps the vector store openable.
  • Tightened yarn test:vectors and package smoke so missing packaged vector segment directories fail release validation instead of shipping a broken search index.
  • Retains beta.11's internal CONVERT_BASE_URL support, typed auth-context plumbing, private remote runtime scaffolding, and public npm package boundary.

Release Readiness Evidence

Run before tagging:

yarn install --immutable
yarn build
yarn workspace @convertcom/mcp-server test --runInBand
yarn test:smoke
yarn test:conformance
yarn test:package
yarn test:vectors
CONVERT_DISABLE_SEMANTIC_KB=1 yarn test:release
yarn test:real
CONVERT_BASE_URL=https://api.app-staging.convert.com/api/v2 yarn test:real

Manual pre-release check must use the npm-style binary path that failed in beta.11:

  1. Pack and install the local tarball into a temporary project.
  2. Launch node_modules/.bin/convert-mcp or Windows convert-mcp.cmd.
  3. Verify MCP initialize, tools/list, docs search / fetch, and accounts.list with Convert credentials.

Release Plan

  1. Keep npm latest on 0.0.1-beta.10 until all validation and manual package-bin testing pass.
  2. Commit beta.12 version metadata, release docs, binary fix, and refreshed knowledge/vector artifacts to main.
  3. Wait for the GitHub Release Gate push workflow to pass on main.
  4. Create and push the annotated tag: 
    git tag -a v0.0.1-beta.12 -m "v0.0.1-beta.12"
git push origin v0.0.1-beta.12
  5. Create a normal GitHub Release for v0.0.1-beta.12 using these notes. Do not mark it as draft or prerelease.
  6. The Publish Package to npmjs workflow will run on release publication, validate the tag/version match, run yarn test:release, and publish @convertcom/[email protected] to npm with the latest tag.
  7. Verify after publish: 
    npm view @convertcom/mcp-server dist-tags versions --json