chore: move MCP server to @pcmstack/mcp and stop hardcoding its version - #13
Merged
Conversation
The bundled MCP server is renamed from `pcm-mcp` to the scoped `@pcmstack/mcp` (pinned to 0.5.0) and its `.mcp.json` key becomes `pcmstack`. Docs are updated so the next rename or bump touches one file: - AGENTS.md no longer quotes a version number; it points at .mcp.json as the single source of truth for the pin. - SKILL.md and database-constraints.md identify the route by the `pcm_*` tool prefix an agent actually sees, instead of naming the server or npm package. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Updates the db-editor plugin’s bundled MCP server configuration and documentation to reflect the rename to the scoped @pcmstack/mcp, while reducing future maintenance by avoiding hardcoded version mentions in prose.
Changes:
- Renames the bundled MCP server package reference to
@pcmstack/mcpand updates.mcp.jsonto use a new server key (pcmstack) with a pinned version. - Updates repository docs to reference the new package name and to avoid hardcoding MCP server version numbers in prose.
- Tweaks skill/references wording to describe Route A via the stable
pcm_*tool prefix rather than the MCP server key/package name.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| README.md | Updates docs/diagram and related-projects links to @pcmstack/mcp. |
| plugins/db-editor/skills/pcm-database/SKILL.md | Removes hard dependency on package/server-key naming; keeps Route A described generically. |
| plugins/db-editor/skills/pcm-database/references/database-constraints.md | Rewords guidance to refer to pcm_* tool parameters rather than the old package name. |
| plugins/db-editor/.mcp.json | Switches MCP server key to pcmstack and pins @pcmstack/mcp@0.5.0. |
| plugins/db-editor/.codex-plugin/plugin.json | Updates Codex longDescription to reference @pcmstack/mcp. |
| AGENTS.md | Updates repo guidance to point to .mcp.json as the single source of truth and references @pcmstack/mcp. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.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
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
The bundled MCP server is renamed from
pcm-mcpto the scoped@pcmstack/mcp(pinned to0.5.0), and the.mcp.jsonserver key becomespcmstack.The rest of the diff makes the docs survive the next rename or version bump:
AGENTS.mdno longer quotes a version number at all. The Security section points at.mcp.jsonas the single source of truth for the pin, with an explicit "never quote a version number here" so a bump stays a one-file change.SKILL.mdandreferences/database-constraints.mdidentify Route A by thepcm_*tool prefix an agent actually sees in its tool list, rather than by the server key or npm package name. That prefix is stable; the package name has now changed twice.README.mdand the CodexlongDescriptionpick up the new package name.No skill behaviour changes — the routing rule, the read-only invariant and the tool flow are untouched.