@dynatrace-oss/dynatrace-mcp-server 2.0.0 → 2.1.0

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -2,6 +2,15 @@
2
2
 
3
3
  ## Unreleased
4
4
 
5
+ ## 2.1.0
6
+
7
+ - **Breaking**: `MCP_BEARER_TOKEN` is now required when running in `--http` mode. The server will refuse to start if this environment variable is not set. This follows the deprecation notice introduced in `2.0.0`. Set `MCP_BEARER_TOKEN` to a secure random value before starting the server (e.g. `export MCP_BEARER_TOKEN=$(openssl rand -base64 32)`).
8
+ - Updated `undici` (8.1.0 → 8.5.0), `@dynatrace-sdk/client-classic-environment-v2` (5.2.3 → 6.1.0), `@dynatrace-sdk/client-platform-management-service` (1.7.0 → 1.8.0), and `@dynatrace/strato-components` (3.6.0 → 3.7.0).
9
+
10
+ ## 2.0.1
11
+
12
+ - Fixed: Human approval elicitation now defaults to `true`, so users only need to press Accept instead of having to toggle the value first.
13
+
5
14
  ## 2.0.0
6
15
 
7
16
  - **Breaking**: Raised the minimum supported Node.js version from `22.10.0` to `24.0.0`.
package/README.md CHANGED
@@ -313,12 +313,9 @@ npx -y @dynatrace-oss/dynatrace-mcp-server@latest --version
313
313
 
314
314
  #### Bearer Token Authentication (`MCP_BEARER_TOKEN`)
315
315
 
316
- When running in HTTP mode you can protect the server with a bearer token:
316
+ `MCP_BEARER_TOKEN` is **required** when running in HTTP mode. The server will refuse to start if this variable is not set.
317
317
 
318
- | Behavior | Detail |
319
- | ------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
320
- | `MCP_BEARER_TOKEN` **set** | Every HTTP request must include an `Authorization: Bearer <token>` header. Requests without a valid token receive `401 Unauthorized`. |
321
- | `MCP_BEARER_TOKEN` **not set** | **Deprecated** The server starts with a warning printed to stderr and accepts all requests without authentication. **Not recommended for production or any network-exposed deployment.** |
318
+ Every HTTP request must include an `Authorization: Bearer <token>` header. Requests without a valid token receive `401 Unauthorized`.
322
319
 
323
320
  **Generating a secure token:**
324
321