@mcp-abap-adt/proxy 0.1.3 → 0.1.4

package/CHANGELOG.md

@@ -7,6 +7,29 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.1.4] - 2025-12-02
+
+### Added
+- **Documentation for BTP-Only authentication mode**
+  - Added "Scenario 2: BTP Authentication Only (No SAP Configuration)" in `doc/USAGE.md`
+  - Documented use case for connecting to any BTP service without SAP ABAP configuration
+  - Explained that `x-mcp-destination` is optional when using `x-btp-destination` or `--btp`
+  - Updated README.md with "BTP-Only Mode" section explaining behavior when only `--btp` is provided
+- **Enhanced help text in `bin/mcp-abap-adt-proxy.js`**
+  - Added detailed "Usage Modes" section with three modes:
+    1. BTP Authentication Mode (with `--btp` only)
+    2. BTP + SAP Configuration Mode (`--btp + --mcp`)
+    3. Local Testing Mode (only `--mcp` or `--mcp-url`)
+  - Added examples for each usage mode
+  - Added information about headers for HTTP/SSE transports
+  - Added service keys location and structure documentation
+  - Clarified that `abap.url` in service key is used as MCP server URL (even for non-SAP services)
+
+### Documentation
+- Improved clarity on when to use each authentication mode
+- Added examples showing BTP-only usage (without SAP configuration)
+- Documented that proxy works with any BTP service, not just SAP ABAP
+
 ## [0.1.3] - 2025-12-02
 
 ### Fixed

package/README.md

@@ -81,9 +81,15 @@ The proxy uses two service keys (URLs are obtained from service keys):
 
 **BTP Authentication Mode** (with `x-btp-destination` or `--btp`):
 1. `x-btp-destination` (or `--btp`) → Gets JWT token from auth-broker → Adds `Authorization: Bearer <token>` header
-2. `x-mcp-destination` (or `--mcp`) → Gets JWT token and SAP config from auth-broker → Adds SAP headers (`x-sap-jwt-token`, `x-sap-url`, etc.)
+2. `x-mcp-destination` (or `--mcp`) → Gets JWT token and SAP config from auth-broker → Adds SAP headers (`x-sap-jwt-token`, `x-sap-url`, etc.) - **optional**
 3. MCP server URL obtained from service key for `x-btp-destination`
 
+**BTP-Only Mode** (with only `x-btp-destination`/`--btp`, without `x-mcp-destination`):
+- Works with any BTP service, not just SAP ABAP
+- Only adds `Authorization: Bearer <token>` header (no SAP headers)
+- MCP server URL obtained from BTP destination service key
+- Suitable for BTP services that don't require SAP ABAP configuration
+
 **Local Testing Mode** (with only `x-mcp-destination`/`--mcp` or `x-mcp-url`/`--mcp-url`):
 1. `x-mcp-url` (or `--mcp-url`) → Direct URL to MCP server (no authentication)
 2. `x-mcp-destination` (or `--mcp`) → Gets MCP server URL from service key for MCP destination (optional token)

package/bin/mcp-abap-adt-proxy.js

@@ -94,6 +94,49 @@ Transport Modes:
   - http / streamable-http: HTTP server (default if stdin is TTY, port 3001)
   - sse: Server-Sent Events server (port 3002)
 
+Usage Modes:
+
+1. BTP Authentication Mode (with --btp):
+   - Adds Authorization: Bearer <token> header from BTP destination
+   - Gets MCP server URL from BTP destination service key
+   - Works with any BTP service, not just SAP ABAP
+   Example: mcp-abap-adt-proxy --btp=ai
+
+2. BTP + SAP Configuration Mode (--btp + --mcp):
+   - Adds Authorization: Bearer <token> header from BTP destination
+   - Adds SAP headers (x-sap-jwt-token, x-sap-url, etc.) from MCP destination
+   - Gets MCP server URL from BTP destination service key
+   - Suitable for SAP ABAP systems that require both BTP and SAP authentication
+   Example: mcp-abap-adt-proxy --btp=ai --mcp=trial
+
+3. Local Testing Mode (only --mcp or --mcp-url):
+   - No BTP authentication required
+   - Gets MCP server URL from MCP destination service key (--mcp) or uses direct URL (--mcp-url)
+   - Optional SAP token (won't fail if unavailable)
+   - Enables local integration testing without BTP authentication
+   Example: mcp-abap-adt-proxy --mcp=trial
+   Example: mcp-abap-adt-proxy --mcp-url=http://localhost:3000/mcp
+
+Headers (for HTTP/SSE transports):
+  - x-btp-destination: Destination for BTP Cloud authorization (optional if --btp is used)
+  - x-mcp-destination: Destination for SAP ABAP connection (optional if --mcp is used)
+  - x-mcp-url: Direct MCP server URL (optional if --mcp-url is used)
+  
+  At least one of the above headers (or corresponding --btp/--mcp/--mcp-url parameter) is required.
+
+Service Keys:
+  Service keys should be placed in:
+  - Unix: ~/.config/mcp-abap-adt/service-keys/<destination>.json
+  - Windows: %USERPROFILE%\\Documents\\mcp-abap-adt\\service-keys\\<destination>.json
+  
+  For BTP destination, service key should contain:
+  {
+    "uaa": { "url": "...", "clientid": "...", "clientsecret": "..." },
+    "abap": { "url": "https://your-mcp-server.com" }
+  }
+  
+  The "abap.url" field is used as the MCP server URL (even for non-SAP services).
+
 For more information, see: https://github.com/fr0ster/mcp-abap-adt-proxy
 `);
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mcp-abap-adt/proxy",
-  "version": "0.1.3",
+  "version": "0.1.4",
   "description": "MCP proxy server for SAP ABAP ADT - proxies local requests to cloud-llm-hub with JWT authentication",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",