datadog-mcp 1.0.0 → 1.0.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/README.md CHANGED
@@ -1,8 +1,10 @@
1
1
  # Datadog MCP Server
2
2
 
3
+ [![Quality gate](https://sonarcloud.io/api/project_badges/quality_gate?project=TANTIOPE_datadog-mcp-server)](https://sonarcloud.io/summary/new_code?id=TANTIOPE_datadog-mcp-server)
3
4
  [![CI](https://github.com/tantiope/datadog-mcp-server/actions/workflows/ci.yml/badge.svg)](https://github.com/tantiope/datadog-mcp-server/actions/workflows/ci.yml)
4
5
  [![npm](https://img.shields.io/npm/v/datadog-mcp)](https://www.npmjs.com/package/datadog-mcp)
5
6
  [![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
7
+ [![Coverage](https://sonarcloud.io/api/project_badges/measure?project=TANTIOPE_datadog-mcp-server&metric=coverage)](https://sonarcloud.io/summary/new_code?id=TANTIOPE_datadog-mcp-server)
6
8
 
7
9
  > **DISCLAIMER**: This is a community-maintained project and is not officially affiliated with, endorsed by, or supported by Datadog, Inc. This MCP server utilizes the Datadog API but is developed independently.
8
10
 
@@ -78,6 +80,26 @@ DD_SITE=datadoghq.com # Default. Use datadoghq.eu for EU, etc.
78
80
  }
79
81
  ```
80
82
 
83
+ ### Kubernetes
84
+
85
+ **Use environment variables instead of container args:**
86
+
87
+ ```yaml
88
+ env:
89
+ - name: DD_API_KEY
90
+ value: "your-api-key"
91
+ - name: DD_APP_KEY
92
+ value: "your-app-key"
93
+ - name: MCP_TRANSPORT
94
+ value: "http"
95
+ - name: MCP_PORT
96
+ value: "3000"
97
+ - name: MCP_HOST
98
+ value: "0.0.0.0"
99
+ ```
100
+
101
+ > **Note:** Kubernetes `args:` replaces the entire Dockerfile CMD, causing Node.js to receive the flags instead of your application. Environment variables avoid this issue.
102
+
81
103
  ### HTTP Transport
82
104
 
83
105
  When running with `--transport=http`: