Skip to content

Become mcp-server, in the package name too - #21

Merged
oblomov-dev merged 1 commit into
mainfrom
claude/rename-to-mcp-server
Aug 18, 2026
Merged

Become mcp-server, in the package name too#21
oblomov-dev merged 1 commit into
mainfrom
claude/rename-to-mcp-server

Conversation

@oblomov-dev

Copy link
Copy Markdown
Member

Follows the repository rename from ai-mcp to mcp-server. Merge this firstabap2UI5/vscode-extension#62 regenerates a snapshot from this repository's main.

The package name

@abap2ui5/mcp@abap2ui5/mcp-server, and the timing is the whole point. RELEASING.md says it itself: the package name is the one thing a release cannot take back. Nothing is published yet, so the change costs four files today and nothing downstream; after the first publish it would cost a deprecation and a second name to explain forever. A repository whose name differs from its only package is exactly the discrepancy the rename was meant to remove.

mcp names a protocol, mcp-server names the thing — which is what somebody scanning the organisation's repository list needs to read without clicking.

The rename history gets an entry for this repository

lib/repo-dirs.json exists so this server can find its neighbours. It now also carries a server entry listing mcp-server and ai-mcp, because abap2UI5/vscode-extension looks for a local checkout of this repository by directory name before falling back to npx — and after a rename it would have looked for the wrong one, silently starting the network copy instead of the clone the user pointed at. That entry is what the extension's fix consumes.

Deliberately unchanged

The npx spec stays github:abap2UI5/mcp-server rather than moving to the npm package, because the package does not exist yet. Moving it is the last step of the first release, and RELEASING.md says where. The bin name stays abap2ui5-mcp, matching the linter's @abap2ui5/linterabap2ui5lint pattern.

npm test: 54/54.


🤖 Generated with Claude Code

https://claude.ai/code/session_01PLDFPfAK1MGq6qHeC6KKWH


Generated by Claude Code

The repository was renamed from ai-mcp to mcp-server: `mcp` names a
protocol, `mcp-server` names the thing, and somebody scanning the
organisation's repository list should not have to click to find out which
it is. The package follows - `@abap2ui5/mcp-server`, not `@abap2ui5/mcp`.

The timing is the point. RELEASING.md says it itself: the package name is
the one thing a release cannot take back. Nothing is published yet, so the
name costs four files today and nothing downstream; after the first
publish it would cost a deprecation and a second name to explain forever.
A repository whose name differs from its only package is exactly the
discrepancy the rename was for.

lib/repo-dirs.json gains an entry for this server itself. It resolves
nothing for its own sake - the file exists so the server can find its
NEIGHBOURS - but abap2UI5/vscode-extension looks for a local checkout of
this repository by directory name before falling back to npx, and after a
rename it would look for the wrong one. Listing both names there is what
that file is for: the ecosystem's rename history, in one place.

The npx spec stays on `github:abap2UI5/mcp-server` rather than moving to
the npm package, because the package does not exist yet. Moving it is the
last step of the first release, and RELEASING.md says where.

Co-Authored-By: Claude <noreply@anthropic.com>
Copilot AI lite review requested due to automatic review settings August 18, 2026 10:57

Copilot AI left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

@oblomov-dev
oblomov-dev merged commit 6bc0c38 into main Aug 18, 2026
2 checks passed
@oblomov-dev
oblomov-dev deleted the claude/rename-to-mcp-server branch August 18, 2026 10:59
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants