Skip to content

Commit ea9fbb1

Browse files
patch: Added google-gemini-cli in README (#160)
1 parent 8e2cb4c commit ea9fbb1

File tree

3 files changed

+51
-5
lines changed

3 files changed

+51
-5
lines changed

.github/prompts/release.prompt.md

Lines changed: 4 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -11,8 +11,7 @@ When preparing a release, follow these steps to ensure everything is in order:
1111
3. Work on a release branch, typically named `chore/prepare-release-<version>`.
1212
4. Create a new section in CHANGELOG.md for the version below "Unreleased Changes".
1313
5. Move all entries from "Unreleased Changes" to this new section. Reword them in the process to fit the content guidelines specified in `.github/instructions/changelog.instructions.md`.
14-
6. Update the version number in `package.json`.
15-
7. Update the version number in `server.json`.
16-
8. Run `npm install --package-lock-only` to sync the lock file.
17-
9. Let the user verify the release notes and version number before proceeding.
18-
10. Commit the changes with a message like `chore(release): prepare for <version> release`.
14+
6. Update the version number in `package.json`, `server.json`, and `gemini-extension.json`.
15+
7. Run `npm install --package-lock-only` to sync the lock file.
16+
8. Let the user verify the release notes and version number before proceeding.
17+
9. Commit the changes with a message like `chore(release): prepare for <version> release`.

README.md

Lines changed: 37 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -277,6 +277,43 @@ The [Amazon Q Developer CLI](https://docs.aws.amazon.com/amazonq/latest/qdevelop
277277

278278
This configuration should be stored in `<your-repo>/.amazonq/mcp.json`.
279279

280+
**Google Gemini CLI**
281+
282+
The [Google Gemini CLI](https://github.com/google-gemini/gemini-cli) is Google's official command-line AI assistant that supports MCP server integration. You can add the Dynatrace MCP server using either the built-in management commands or manual configuration.
283+
284+
Using `gemini` CLI directly (recommended):
285+
286+
```bash
287+
gemini extensions install https://github.com/dynatrace-oss/dynatrace-mcp
288+
export DT_PLATFORM_TOKEN=...
289+
export DT_ENVIRONMENT=https://...
290+
```
291+
292+
and verify that the server is running via
293+
294+
```bash
295+
gemini mcp list
296+
```
297+
298+
Or manually in your `~/.gemini/settings.json` or `.gemini/settings.json`:
299+
300+
```json
301+
{
302+
"mcpServers": {
303+
"dynatrace": {
304+
"command": "npx",
305+
"args": ["@dynatrace-oss/dynatrace-mcp-server@latest"],
306+
"env": {
307+
"DT_PLATFORM_TOKEN": "",
308+
"DT_ENVIRONMENT": ""
309+
},
310+
"timeout": 30000,
311+
"trust": false
312+
}
313+
}
314+
}
315+
```
316+
280317
### HTTP Server Mode (Alternative)
281318

282319
For scenarios where you need to run the MCP server as an HTTP service instead of using stdio (e.g., for stateful sessions, load balancing, or integration with web clients), you can use the HTTP server mode:

gemini-extension.json

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,10 @@
1+
{
2+
"name": "dynatrace-mcp-server",
3+
"version": "0.6.0",
4+
"mcpServers": {
5+
"dynatrace": {
6+
"command": "npx",
7+
"args": ["-y", "@dynatrace-oss/dynatrace-mcp-server@latest"]
8+
}
9+
}
10+
}

0 commit comments

Comments
 (0)