sap-abap-mcp 0.4.0 → 0.4.1

package/CHANGELOG.md

@@ -3,6 +3,23 @@
 All notable changes to **SAP ABAP MCP** (npm + VS Code extension — same
 codebase, same version).
 
+## 0.4.1 — 2026-05-22
+
+### Documentation
+- **README — npm smoke-test section**: explains how to verify the
+  published npm package end-to-end from a terminal, and warns that
+  running `npx -y sap-abap-mcp` from inside the source repo itself
+  produces a misleading `sh: sap-abap-mcp: command not found`. Reason:
+  the repo's own `package.json` declares the same package name, so
+  `npx` resolves the local package (which has no `node_modules/.bin/`
+  linkage) instead of fetching from the registry. Running from any
+  other directory (e.g. `/tmp`) avoids the name-shadowing. Real MCP
+  clients (Claude Desktop, Claude Code, Cursor) spawn from their own
+  working directory and never hit this — the quirk only shows up during
+  manual smoke tests inside the source checkout.
+
+No code changes vs 0.4.0; the bundled `mcp-server.js` is byte-identical.
+
 ## 0.4.0 — 2026-05-22
 
 ### Added

package/README.md

@@ -156,6 +156,37 @@ npx-based config above, so the registration survives extension upgrades).
    provider.
 5. Ask Copilot: *"Ping my SAP system."*
 
+### Smoke-test the npm package from the command line
+
+If you want to verify the published `sap-abap-mcp` npm package runs on
+your machine (independent of any MCP client), run this from a directory
+**other than this repo's source checkout** — see the warning below:
+
+```bash
+cd /tmp     # any directory that is NOT the sap-abap-vscode-mcp source repo
+echo '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"t","version":"1"}}}' \
+  | SAP_HOST="https://sap.example.com:44300" SAP_CLIENT="800" \
+    SAP_USER="YOURUSER" SAP_PASSWORD="yourpassword" SAP_VERIFY_SSL=false \
+    npx -y sap-abap-mcp
+```
+
+Expected output (single line):
+
+```json
+{"result":{"protocolVersion":"2024-11-05","capabilities":{"tools":{}},"serverInfo":{"name":"sap-abap-mcp","version":"0.1.0"}},"jsonrpc":"2.0","id":1}
+```
+
+> **⚠️ Why "not in the source repo":** the source repo's own
+> `package.json` declares `"name": "sap-abap-mcp"`, so `npx` inside that
+> directory tries to resolve the *local* package instead of fetching
+> from the registry. Since the local repo has no `node_modules/.bin/`
+> linkage for its own bin entry, you get `sh: sap-abap-mcp: command not
+> found`. Running from `/tmp` (or any other directory) avoids the
+> name-shadowing and `npx` cleanly downloads + executes the published
+> package. This is a quirk of npm's resolution, not a bug in the
+> package. Real MCP clients (Claude Desktop, Claude Code, Cursor) spawn
+> from their own working directory and never hit this.
+
 ## VS Code extension commands
 
 All available from the command palette (`⇧⌘P` / `Ctrl+Shift+P`) — these

package/package.json

@@ -2,7 +2,7 @@
   "name": "sap-abap-mcp",
   "displayName": "SAP ABAP MCP",
   "description": "AI-powered ABAP development. Registers an MCP server that lets Copilot Chat (and other MCP clients) read, search, and edit ABAP objects on any on-premise SAP system via the ADT REST API.",
-  "version": "0.4.0",
+  "version": "0.4.1",
   "publisher": "lom-ali-imadaev",
   "license": "Apache-2.0",
   "bin": {