refactor: rename package and related files from pcm-mcp to pcmstack - #57
Merged
Conversation
Rename the npm package to @pcmstack/mcp and the bin entry to pcmstack. Scoped packages are private by default, so publishConfig.access is set to public for the release workflow. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR renames the project from pcm-mcp to PCMStack, moving the npm package to @pcmstack/mcp, renaming the executable to pcmstack, and updating bundle/release naming to match.
Changes:
- Rename MCP server name and update installation/config examples to use
pcmstack/@pcmstack/mcp. - Update packaging outputs from
pcm-mcp.mcpbtopcmstack.mcpb, including the release workflow artifact. - Update the MCP bundle manifest metadata to use
pcmstack+ aPCMStackdisplay name.
Reviewed changes
Copilot reviewed 5 out of 6 changed files in this pull request and generated 3 comments.
Show a summary per file
| File | Description |
|---|---|
| src/index.ts | Renames the MCP server identifier to pcmstack. |
| README.md | Updates npm links/config snippets and bundle filename references for the new scoped package and name. |
| package.json | Moves package to @pcmstack/mcp, renames the bin, and updates the pack output plus public publish config. |
| manifest.json | Renames the bundle/server metadata (name, display_name) to PCMStack. |
| .github/workflows/publish.yml | Updates the release artifact filename to dist/pcmstack.mcpb. |
💡 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.
Summary
Renames the project from
pcm-mcpto PCMStack, and moves the npm package under the@pcmstack/mcpscope.@pcmstack/mcp, withpublishConfig.access: publicsince scoped packages are private by defaultbinentry renamed frompcm-mcptopcmstackpcmstack; the bundle manifest gains aPCMStackdisplay name.mcpbbundle is built and released aspcmstack.mcpbFollow-up needed before releasing
Publishing a new tag will fail until both of these are done on npmjs.com:
pcmstacknpm organization exists and this account can publish to it@pcmstack/mcpis registered as a trusted publisher for this repository's workflow (the release job authenticates through OIDC)Once published,
pcm-mcpshould be deprecated pointing at the new name. Already published versions do not carry over: the new package starts empty, so it is worth publishing it at the next version number rather than restarting the numbering.Note on compatibility
Configs using
npx -y pcm-mcpkeep working until the old package is deprecated, but they need updating to@pcmstack/mcpto receive further versions. Any config invoking thepcm-mcpbinary directly breaks, as the command is nowpcmstack.