@dynatrace-oss/dynatrace-mcp-server 1.8.4-dev.20260428131521 → 1.8.4

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
@@ -1,5 +1,11 @@
1
1
  # @dynatrace-oss/dynatrace-mcp-server
2
2
 
3
+ ## 1.8.4
4
+
5
+ - This repository is now in Maintenance Mode. Active development has moved to the [Remote Dynatrace MCP Server](https://www.dynatrace.com/hub/detail/dynatrace-mcp-server/). See [#496](https://github.com/dynatrace-oss/dynatrace-mcp/issues/496) for details.
6
+ - Added a Cursor Marketplace plugin under `plugins/dynatrace-mcp/`, enabling the Dynatrace MCP Server to be listed and installed directly from the Cursor Marketplace.
7
+ - Updated `@dynatrace/strato-components` (3.2.1 → 3.3.0) and `@dynatrace/strato-icons` (2.1.1 → 2.2.0).
8
+
3
9
  ## 1.8.3
4
10
 
5
11
  - Fixed privacy notice URL in MCPB manifest
package/README.md CHANGED
@@ -26,7 +26,7 @@
26
26
 
27
27
  > 🚀 **Try out our brand new [Remote Dynatrace MCP Server](https://www.dynatrace.com/hub/detail/dynatrace-mcp-server/)!** Now available - no local setup required, connect instantly to your Dynatrace environment from any MCP-compatible client. See our [migration guide](docs/remote-mcp-migration.md) for a comparison and step-by-step instructions.
28
28
 
29
- **MAINTENANCE MODE** - Please note, that this repository is currently in [*Maintenance Mode*](https://github.com/dynatrace-oss/dynatrace-mcp/issues/496).
29
+ **MAINTENANCE MODE** - Please note, that this repository is currently in [_Maintenance Mode_](https://github.com/dynatrace-oss/dynatrace-mcp/issues/496).
30
30
 
31
31
  The local _Dynatrace MCP server_ allows AI Assistants to interact with the [Dynatrace](https://www.dynatrace.com/) observability platform,
32
32
  bringing real-time observability data directly into your development workflow.
package/index.js CHANGED
@@ -121739,7 +121739,7 @@ var {
121739
121739
  } = import_index2.default;
121740
121740
 
121741
121741
  // package.json
121742
- var version2 = "1.8.4-dev.20260428131521";
121742
+ var version2 = "1.8.4";
121743
121743
 
121744
121744
  // src/utils/version.ts
121745
121745
  function getPackageJsonVersion() {
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@dynatrace-oss/dynatrace-mcp-server",
3
- "version": "1.8.4-dev.20260428131521",
3
+ "version": "1.8.4",
4
4
  "mcpName": "io.github.dynatrace-oss/Dynatrace-mcp",
5
5
  "description": "Model Context Protocol (MCP) server for Dynatrace",
6
6
  "keywords": [
package/server.json CHANGED
@@ -6,13 +6,13 @@
6
6
  "url": "https://github.com/dynatrace-oss/Dynatrace-mcp",
7
7
  "source": "github"
8
8
  },
9
- "version": "1.8.3",
9
+ "version": "1.8.4",
10
10
  "packages": [
11
11
  {
12
12
  "registryType": "npm",
13
13
  "registryBaseUrl": "https://registry.npmjs.org",
14
14
  "identifier": "@dynatrace-oss/dynatrace-mcp-server",
15
- "version": "1.8.3",
15
+ "version": "1.8.4",
16
16
  "runtimeHint": "npx",
17
17
  "transport": {
18
18
  "type": "stdio"