@mcp-abap-adt/proxy 0.2.0 → 1.0.0

package/CHANGELOG.md

@@ -7,6 +7,34 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [1.0.0] - 2026-04-07
+
+### Breaking Changes
+- **Header renamed: `x-btp-destination` → `x-sap-destination`**
+  - The proxy now uses `x-sap-destination` header (same as MCP server) instead of the proxy-specific `x-btp-destination`
+  - The `--btp` CLI parameter is unchanged
+  - Clients sending `x-btp-destination` header must update to `x-sap-destination`
+
+### Added
+- **Transparent reverse proxy for BTP request forwarding**
+  - Replaced buffered axios-based proxy with Node.js native HTTP streaming reverse proxy
+  - Supports any HTTP API including OpenAI-compatible streaming endpoints
+  - `targetUrl` parameter for explicit target URL override (`--target-url`/`--url` or `x-target-url` header)
+- **Interactive configuration wizard (TUI)**
+  - `npx @mcp-abap-adt/proxy --tui` launches interactive setup wizard
+  - Service key existence checker validates BTP destination before configuration
+  - Generates YAML config files with inline comments
+  - Supports BTP and Direct URL scenarios with advanced settings
+- **Dependencies updated**
+  - `@mcp-abap-adt/interfaces` bumped to v5
+  - `@mcp-abap-adt/auth-stores` bumped to v1.0.4
+  - Added `@inquirer/prompts` for TUI wizard
+
+### Fixed
+- **Header validation skipped in reverse proxy mode** when config provides destination
+- **YAML config file now correctly loads transport/port settings** (`--config` flag)
+- **targetUrl loading from YAML config** now works correctly
+
 ## [0.1.9] - 2026-02-12
 
 ### Changed
@@ -45,7 +73,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 - **Separate AuthBroker instances for BTP and ABAP destinations**
-  - `btpAuthBroker` with `XsuaaTokenProvider` for BTP destinations (`--btp` or `x-btp-destination`)
+  - `btpAuthBroker` with `XsuaaTokenProvider` for BTP destinations (`--btp` or `x-sap-destination`)
   - `abapAuthBroker` with `BtpTokenProvider` for ABAP destinations (`--mcp` or `x-mcp-destination`)
   - Proper separation ensures correct token provider is used for each destination type
 - **Client Setup Guide** (`docs/CLIENT_SETUP.md`)
@@ -89,7 +117,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 - **Documentation for BTP-Only authentication mode**
   - Added "Scenario 2: BTP Authentication Only (No SAP Configuration)" in `docs/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`
+  - Explained that `x-mcp-destination` is optional when using `x-sap-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:
@@ -111,7 +139,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 ### Fixed
 - **Unit tests updated to match new routing logic**
   - Fixed tests that expected `UNKNOWN` strategy when only `x-mcp-destination` or `x-mcp-url` is provided
-  - Updated test expectations to reflect that `x-btp-destination` is now optional
+  - Updated test expectations to reflect that `x-sap-destination` is now optional
   - Added tests for `x-mcp-url` header support
   - Updated `shouldProxy` function tests to cover all routing scenarios (BTP, MCP destination, MCP URL)
   - All 51 unit tests now pass successfully
@@ -134,7 +162,7 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ### Added
 - **Local testing mode without BTP authentication**
-  - Proxy can now run with only `--mcp` or `x-mcp-destination` (without `--btp` or `x-btp-destination`)
+  - Proxy can now run with only `--mcp` or `x-mcp-destination` (without `--btp` or `x-sap-destination`)
   - Enables local integration testing without BTP authentication
   - MCP server URL can be obtained from MCP destination service key or specified directly via `--mcp-url`
 - **`--mcp-url` parameter support**
@@ -149,16 +177,16 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   - Default configuration: ADT on port 3000 (HTTP), Proxy on port 3001 (HTTP)
   - Available via `npm run test:servers`
 - **Flexible routing requirements**
-  - Proxy accepts either `x-btp-destination/--btp`, `x-mcp-destination/--mcp`, or `x-mcp-url/--mcp-url`
+  - Proxy accepts either `x-sap-destination/--btp`, `x-mcp-destination/--mcp`, or `x-mcp-url/--mcp-url`
   - Removed strict requirement for BTP destination when using MCP destination or URL
 
 ### Changed
 - **Routing logic updated**
-  - `x-btp-destination` is now optional (was required)
+  - `x-sap-destination` is now optional (was required)
   - Proxy can work with only `x-mcp-destination` or `x-mcp-url` for local testing
   - MCP URL can be obtained from multiple sources (priority order):
     1. `x-mcp-url` header or `--mcp-url` parameter (direct URL)
-    2. Service key for `x-btp-destination` (if provided)
+    2. Service key for `x-sap-destination` (if provided)
     3. Service key for `x-mcp-destination` (if only MCP destination is provided)
 - **Token retrieval made optional for MCP destination**
   - Token retrieval for `mcpDestination` is now optional (won't fail if token unavailable)

package/README.md

@@ -76,7 +76,7 @@ For detailed setup instructions for Cline and GitHub Copilot, see the **[Client
       "type": "streamableHttp",
       "url": "http://localhost:3001/mcp/stream/http",
       "headers": {
-        "x-btp-destination": "btp-cloud"
+        "x-sap-destination": "btp-cloud"
       }
     }
   }
@@ -84,10 +84,10 @@ For detailed setup instructions for Cline and GitHub Copilot, see the **[Client
 ```
 
 **Required Headers:**
-- `x-btp-destination` - Destination name for BTP Cloud authorization token and MCP server URL
+- `x-sap-destination` - Destination name for BTP Cloud authorization token and MCP server URL
 
 **Command Line Overrides:**
-- `--btp=<destination>` - Overrides `x-btp-destination` header (takes precedence)
+- `--btp=<destination>` - Overrides `x-sap-destination` header (takes precedence)
 - `--url=<url>` - Overrides MCP server URL (required if service key lacks URL)
 - `--browser=<browser>` - Browser to use: `system` (default), `chrome`, `edge`, `firefox`, `headless`
 - `--browser-auth-port=<port>` - Port for OAuth2 callback (default: 3333)
@@ -97,7 +97,7 @@ For detailed setup instructions for Cline and GitHub Copilot, see the **[Client
 
 The proxy uses BTP/XSUAA authentication:
 
-1. **BTP Authentication** (if `--btp` or `x-btp-destination` is present):
+1. **BTP Authentication** (if `--btp` or `x-sap-destination` is present):
    - Uses `AuthorizationCodeProvider` (browser-based OAuth2 flow)
    - **Eager Authentication**: Opens browser immediately on startup to get token
    - Injects/overwrites `Authorization: Bearer <token>` header
@@ -106,7 +106,7 @@ The proxy uses BTP/XSUAA authentication:
 
 **BTP Authentication Mode** (with `--btp`):
 1. Proxy starts → Opens browser for login (Eager Auth) → Gets/Refreshes JWT token
-2. `x-btp-destination` (or `--btp`) → Adds `Authorization: Bearer <token>` header
+2. `x-sap-destination` (or `--btp`) → Adds `Authorization: Bearer <token>` header
 3. MCP server URL obtained from service key OR `--url` parameter
 
 ## Documentation
@@ -126,16 +126,16 @@ The proxy uses BTP/XSUAA authentication:
 
 The proxy performs the following steps for each request:
 
-1. **Extract Headers**: Reads `x-btp-destination` header
+1. **Extract Headers**: Reads `x-sap-destination` header
 2. **Apply Command Line Overrides**: `--btp` parameter overrides header (if provided)
-3. **Validate Routing Requirements**: Requires `x-btp-destination/--btp`
-4. **BTP Authentication** (if `x-btp-destination` or `--btp` is provided):
+3. **Validate Routing Requirements**: Requires `x-sap-destination/--btp`
+4. **BTP Authentication** (if `x-sap-destination` or `--btp` is provided):
    - Uses `AuthorizationCodeProvider` (browser-based login)
    - **Eagerly** obtains token on startup (if configured via `--btp`)
    - Retrieves JWT token using cached refresh token or opens browser
    - Injects/overwrites `Authorization: Bearer <token>` header
 5. **Get MCP Server URL**:
-   - From service key for `x-btp-destination`
+   - From service key for `x-sap-destination`
 6. **Forward Request**: Sends request to MCP server URL with all injected headers
 7. **Return Response**: Forwards the response back to the client
 

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

@@ -55,7 +55,7 @@ Options:
   --sse-port=<port>       SSE server port (default: 3002)
   --http-host=<host>      HTTP server host (default: 0.0.0.0)
   --sse-host=<host>       SSE server host (default: 0.0.0.0)
-  --btp=<destination>     Override x-btp-destination header (for BTP Cloud authorization)
+  --btp=<destination>     Override x-sap-destination header (for BTP Cloud authorization)
                            Required for stdio/SSE transports unless provided in headers
   --target-url=<url>      Override target URL (separates Auth from Connection)
                            Useful for direct OData service testing or non-standard MCP URLs
@@ -100,7 +100,7 @@ Usage Modes:
    Example: mcp-abap-adt-proxy --btp=ai
 
 Headers (for HTTP/SSE transports):
-  - x-btp-destination: Destination for BTP Cloud authorization (optional if --btp is used)
+  - x-sap-destination: Destination for BTP Cloud authorization (optional if --btp is used)
 
   At least one of the above headers (or corresponding --btp parameter) is required.
 

package/dist/lib/config.js

@@ -217,7 +217,7 @@ function validateConfig(config) {
     // Check if BTP destination is provided
     const hasDestination = config.btpDestination;
     if (!hasDestination) {
-        warnings.push('No BTP destination provided (--btp). Proxy will not work unless requests include x-btp-destination header.');
+        warnings.push('No BTP destination provided (--btp). Proxy will not work unless requests include x-sap-destination header.');
     }
     if (config.httpPort < 1 || config.httpPort > 65535) {
         errors.push('MCP_HTTP_PORT must be between 1 and 65535');

package/dist/proxy/btpProxy.d.ts

@@ -1,7 +1,7 @@
 /**
  * BTP Proxy - Proxies requests to MCP servers with JWT authentication
  *
- * For requests with x-btp-destination, proxies to target MCP server
+ * For requests with x-sap-destination, proxies to target MCP server
  * with JWT token from auth-broker (XSUAA/BTP)
  */
 import { AuthBroker } from '@mcp-abap-adt/auth-broker';
@@ -79,7 +79,7 @@ export declare class BtpProxy {
      * Process flow:
      *
      * 1. BTP Authentication (XSUAA):
-     *    1.1 If x-btp-destination header exists:
+     *    1.1 If x-sap-destination header exists:
      *        - Check map for broker with key = destination, get or create, save to map
      *        - Get token from xsuaa broker
      *        - Add/replace Authorization: Bearer <token> header

package/dist/proxy/btpProxy.js

@@ -2,7 +2,7 @@
 /**
  * BTP Proxy - Proxies requests to MCP servers with JWT authentication
  *
- * For requests with x-btp-destination, proxies to target MCP server
+ * For requests with x-sap-destination, proxies to target MCP server
  * with JWT token from auth-broker (XSUAA/BTP)
  */
 var __importDefault = (this && this.__importDefault) || function (mod) {
@@ -437,7 +437,7 @@ class BtpProxy {
      * Process flow:
      *
      * 1. BTP Authentication (XSUAA):
-     *    1.1 If x-btp-destination header exists:
+     *    1.1 If x-sap-destination header exists:
      *        - Check map for broker with key = destination, get or create, save to map
      *        - Get token from xsuaa broker
      *        - Add/replace Authorization: Bearer <token> header
@@ -464,21 +464,21 @@ class BtpProxy {
         // ============================================
         // BTP Authentication (XSUAA)
         // ============================================
-        const btpDestinationHeader = this.getHeaderValue(originalHeaders[interfaces_1.HEADER_BTP_DESTINATION]);
+        const btpDestinationHeader = this.getHeaderValue(originalHeaders[interfaces_1.HEADER_SAP_DESTINATION]);
         const btpDestinationFromParam = routingDecision.btpDestination && !btpDestinationHeader
             ? routingDecision.btpDestination
             : undefined;
         let btpDestination;
         if (btpDestinationHeader) {
             btpDestination = btpDestinationHeader;
-            logger_js_1.logger?.debug('Using x-btp-destination from header', {
+            logger_js_1.logger?.debug('Using x-sap-destination from header', {
                 type: 'BTP_DESTINATION_FROM_HEADER',
                 destination: btpDestination,
             });
         }
         else if (btpDestinationFromParam) {
             btpDestination = btpDestinationFromParam;
-            logger_js_1.logger?.debug('Using x-btp-destination from parameter', {
+            logger_js_1.logger?.debug('Using x-sap-destination from parameter', {
                 type: 'BTP_DESTINATION_FROM_PARAM',
                 destination: btpDestination,
             });

package/dist/router/headerAnalyzer.d.ts

@@ -18,17 +18,17 @@ export interface RoutingDecision {
  * Analyze headers and extract routing information
  *
  * Proxy validates only one header for authentication:
- * - x-btp-destination (or --btp): destination for BTP Cloud authorization token (Authorization: Bearer) and MCP server URL
+ * - x-sap-destination (or --btp): destination for BTP Cloud authorization token (Authorization: Bearer) and MCP server URL
  *
 
  *
  * Command-line overrides (take precedence over headers):
- * - --btp=<destination>: overrides x-btp-destination header
+ * - --btp=<destination>: overrides x-sap-destination header
  *
  * Other headers are passed directly to MCP server without validation.
  *
  * MPC server URL is obtained from:
- * - service key for x-btp-destination (via auth-broker)
+ * - service key for x-sap-destination (via auth-broker)
  *
  *
  * Note: Proxy does NOT use .env files for connection configuration. Only destinations via auth-broker (service key files) are used.

package/dist/router/headerAnalyzer.js

@@ -19,17 +19,17 @@ var RoutingStrategy;
  * Analyze headers and extract routing information
  *
  * Proxy validates only one header for authentication:
- * - x-btp-destination (or --btp): destination for BTP Cloud authorization token (Authorization: Bearer) and MCP server URL
+ * - x-sap-destination (or --btp): destination for BTP Cloud authorization token (Authorization: Bearer) and MCP server URL
  *
 
  *
  * Command-line overrides (take precedence over headers):
- * - --btp=<destination>: overrides x-btp-destination header
+ * - --btp=<destination>: overrides x-sap-destination header
  *
  * Other headers are passed directly to MCP server without validation.
  *
  * MPC server URL is obtained from:
- * - service key for x-btp-destination (via auth-broker)
+ * - service key for x-sap-destination (via auth-broker)
  *
  *
  * Note: Proxy does NOT use .env files for connection configuration. Only destinations via auth-broker (service key files) are used.
@@ -48,9 +48,9 @@ function analyzeHeaders(headers, configOverrides) {
         }
         return typeof headerValue === 'string' ? headerValue.trim() : undefined;
     };
-    // Extract authorization destination for BTP Cloud (x-btp-destination)
+    // Extract authorization destination for BTP Cloud (x-sap-destination)
     // Command-line parameter --btp takes precedence over header
-    const btpDestinationHeader = getHeaderValue(interfaces_1.HEADER_BTP_DESTINATION);
+    const btpDestinationHeader = getHeaderValue(interfaces_1.HEADER_SAP_DESTINATION);
     const extractedBtpDestination = configOverrides?.btpDestination
         ? configOverrides.btpDestination
         : btpDestinationHeader;
@@ -72,10 +72,10 @@ function analyzeHeaders(headers, configOverrides) {
     if (!extractedBtpDestination) {
         return {
             strategy: RoutingStrategy.UNKNOWN,
-            reason: 'No BTP destination provided (missing x-btp-destination or --btp)',
+            reason: 'No BTP destination provided (missing x-sap-destination or --btp)',
         };
     }
-    // If x-btp-destination is present, we can proxy with BTP authentication (URL will be obtained from service key)
+    // If x-sap-destination is present, we can proxy with BTP authentication (URL will be obtained from service key)
     // If x-mcp-url is provided, we can use it directly (for local testing)
     logger_js_1.logger?.debug('Routing decision: PROXY', {
         btpDestination: extractedBtpDestination,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mcp-abap-adt/proxy",
-  "version": "0.2.0",
+  "version": "1.0.0",
   "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",