Skip to content

Commit 7eb441b

Browse files
committed
docs: address Copilot review feedback
1 parent b1723df commit 7eb441b

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

AGENTS.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -11,7 +11,7 @@ This document is a comprehensive guide for an AI agent tasked with developing an
1111
| Topic | Details |
1212
| --- | --- |
1313
| **Purpose** | Expose vetted Sysdig Monitor workflows (plus shared SysQL tooling) to LLMs through MCP tools. |
14-
| **Tech Stack** | Go 1.25+, `mcp-go`, Cobra CLI, Ginkgo/Gomega, `golangci-lint`, Nix. |
14+
| **Tech Stack** | Go 1.26+, `mcp-go`, Cobra CLI, Ginkgo/Gomega, `golangci-lint`, Nix. |
1515
| **Entry Point** | `cmd/server/main.go` (Cobra CLI that wires config, Sysdig client, etc.). |
1616
| **Dev Shell** | `nix develop` provides a consistent development environment. |
1717
| **Key Commands** | `just fmt`, `just lint`, `just test`, `just check`, `just update`. |

README.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ For Sysdig Secure-specific workflows, use the dedicated [@sysdig/secure-mcp-serv
4444
Get up and running with the Sysdig MCP Server quickly using our pre-built Docker image.
4545

4646
1. **Get your API Token**:
47-
Go to your Sysdig instance and navigate to **Settings > Sysdig Monitor API**. This token is required to authenticate requests to the Sysdig Platform (See the [Configuration](#configuration) section for more details).
47+
Go to your Sysdig instance and navigate to **Settings > Sysdig Monitor API** (or **Sysdig Secure API** — either works, since SysQL tools accept both). This token is required to authenticate requests to the Sysdig Platform (See the [Configuration](#configuration) section for more details).
4848

4949
2. **Configure your MCP client**:
5050

@@ -209,7 +209,7 @@ SYSDIG_MCP_MOUNT_PATH=/sysdig-mcp-server
209209

210210
### API Permissions
211211

212-
To use the MCP server tools, your API token needs specific permissions in Sysdig Secure. We recommend creating a dedicated Service Account (SA) with a custom role containing only the required permissions.
212+
To use the MCP server tools, your API token needs specific permissions on the Sysdig platform. We recommend creating a dedicated Service Account (SA) with a custom role containing only the required permissions.
213213

214214
**Permissions Mapping:**
215215

@@ -225,7 +225,7 @@ To use the MCP server tools, your API token needs specific permissions in Sysdig
225225

226226
**Setting up Permissions:**
227227

228-
1. Go to **Settings > Users & Teams > Roles** in your Sysdig Secure instance
228+
1. Go to **Settings > Users & Teams > Roles** in your Sysdig instance
229229
2. Create a new role with the permissions listed above
230230
3. Assign this role to a Service Account or user
231231
4. Use the API token from that account with the MCP server

0 commit comments

Comments
 (0)