From a6dc69a6b129ac8340d23e0f4e7136b75a446f13 Mon Sep 17 00:00:00 2001 From: Fede Barcelona Date: Tue, 21 Apr 2026 17:17:43 +0200 Subject: [PATCH 1/2] docs: clarify API token can be Secure or Monitor --- README.md | 34 +++++++++++++++++----------------- 1 file changed, 17 insertions(+), 17 deletions(-) diff --git a/README.md b/README.md index fc667ed..3e68ace 100644 --- a/README.md +++ b/README.md @@ -35,15 +35,15 @@ This is an implementation of an [MCP (Model Context Protocol) Server](https://mo Get up and running with the Sysdig MCP Server quickly using our pre-built Docker image. 1. **Get your API Token**: - Go to your Sysdig Secure instance and navigate to **Settings > Sysdig Secure API**. Here, you can generate or copy your API token. This token is required to authenticate requests to the Sysdig Platform (See the [Configuration](#configuration) section for more details). + Go to your Sysdig instance and navigate to **Settings > Sysdig Secure API** (or **Sysdig Monitor API**). Either a Sysdig Secure or Sysdig Monitor API token works. This token is required to authenticate requests to the Sysdig Platform (See the [Configuration](#configuration) section for more details). 2. **Configure your MCP client**: Add the server configuration to your MCP client (e.g., Claude Desktop's `claude_desktop_config.json`). Choose your preferred installation method from the [Server Setup](#server-setup) section. The [Docker](#docker) method is the easiest to get started with since it requires no local toolchain. Substitute the following placeholders with your actual values: - - ``: The hostname of your Sysdig Secure instance (e.g., `https://us2.app.sysdig.com` or `https://eu1.app.sysdig.com`) - - ``: Your Sysdig Secure API token + - ``: The hostname of your Sysdig instance (e.g., `https://us2.app.sysdig.com` or `https://eu1.app.sysdig.com`) + - ``: Your Sysdig API token (Secure or Monitor) ## Available Tools @@ -168,8 +168,8 @@ The server dynamically filters the available tools based on the permissions asso The following environment variables are **required** for configuring the Sysdig SDK: -- `SYSDIG_MCP_API_HOST`: The URL of your Sysdig Secure instance (e.g., `https://us2.app.sysdig.com`). **Required when using `stdio` transport.** -- `SYSDIG_MCP_API_TOKEN`: Your Sysdig Secure API token. **Required only when using `stdio` transport.** +- `SYSDIG_MCP_API_HOST`: The URL of your Sysdig instance (e.g., `https://us2.app.sysdig.com`). **Required when using `stdio` transport.** +- `SYSDIG_MCP_API_TOKEN`: Your Sysdig API token (Secure or Monitor). **Required only when using `stdio` transport.** You can also set the following variables to override the default configuration: @@ -267,7 +267,7 @@ If you have Go installed, the MCP client can run the server directly without clo ], "env": { "SYSDIG_MCP_API_HOST": "", - "SYSDIG_MCP_API_TOKEN": "", + "SYSDIG_MCP_API_TOKEN": "", "SYSDIG_MCP_TRANSPORT": "stdio" } } @@ -281,21 +281,21 @@ Or using the CLI: # Claude Code claude mcp add --transport stdio \ -e SYSDIG_MCP_API_HOST= \ - -e SYSDIG_MCP_API_TOKEN= \ + -e SYSDIG_MCP_API_TOKEN= \ -e SYSDIG_MCP_TRANSPORT=stdio \ -- sysdig-mcp-server go run github.com/sysdiglabs/sysdig-mcp-server/cmd/server@latest # Gemini CLI gemini mcp add -t stdio \ -e SYSDIG_MCP_API_HOST= \ - -e SYSDIG_MCP_API_TOKEN= \ + -e SYSDIG_MCP_API_TOKEN= \ -e SYSDIG_MCP_TRANSPORT=stdio \ sysdig-mcp-server go run github.com/sysdiglabs/sysdig-mcp-server/cmd/server@latest # Codex CLI codex mcp add \ --env SYSDIG_MCP_API_HOST= \ - --env SYSDIG_MCP_API_TOKEN= \ + --env SYSDIG_MCP_API_TOKEN= \ --env SYSDIG_MCP_TRANSPORT=stdio \ -- sysdig-mcp-server go run github.com/sysdiglabs/sysdig-mcp-server/cmd/server@latest ``` @@ -329,7 +329,7 @@ Configure your client with: ], "env": { "SYSDIG_MCP_API_HOST": "", - "SYSDIG_MCP_API_TOKEN": "", + "SYSDIG_MCP_API_TOKEN": "", "SYSDIG_MCP_TRANSPORT": "stdio" } } @@ -368,7 +368,7 @@ Configure your client with: "command": "sysdig-mcp-server", "env": { "SYSDIG_MCP_API_HOST": "", - "SYSDIG_MCP_API_TOKEN": "", + "SYSDIG_MCP_API_TOKEN": "", "SYSDIG_MCP_TRANSPORT": "stdio" } } @@ -382,21 +382,21 @@ Or using the CLI: # Claude Code claude mcp add --transport stdio \ -e SYSDIG_MCP_API_HOST= \ - -e SYSDIG_MCP_API_TOKEN= \ + -e SYSDIG_MCP_API_TOKEN= \ -e SYSDIG_MCP_TRANSPORT=stdio \ -- sysdig-mcp-server sysdig-mcp-server # Gemini CLI gemini mcp add -t stdio \ -e SYSDIG_MCP_API_HOST= \ - -e SYSDIG_MCP_API_TOKEN= \ + -e SYSDIG_MCP_API_TOKEN= \ -e SYSDIG_MCP_TRANSPORT=stdio \ sysdig-mcp-server sysdig-mcp-server # Codex CLI codex mcp add \ --env SYSDIG_MCP_API_HOST= \ - --env SYSDIG_MCP_API_TOKEN= \ + --env SYSDIG_MCP_API_TOKEN= \ --env SYSDIG_MCP_TRANSPORT=stdio \ -- sysdig-mcp-server sysdig-mcp-server ``` @@ -413,7 +413,7 @@ kubectl create namespace mcp-server kubectl create secret generic mcp-server-secrets \ --namespace mcp-server \ --from-literal=SYSDIG_MCP_API_HOST= \ - --from-literal=SYSDIG_MCP_API_TOKEN= + --from-literal=SYSDIG_MCP_API_TOKEN= ``` **2. Deploy the server:** @@ -496,7 +496,7 @@ Additionally, you can specify the Sysdig Secure host by providing the `X-Sysdig- Example headers: ``` -Authorization: Bearer +Authorization: Bearer X-Sysdig-Host: ``` @@ -513,7 +513,7 @@ For the Claude Desktop app, configure the MCP server by editing the `claude_desk 1. Go to **Settings > Developer** in the Claude Desktop app. 2. Click on **Edit Config** to open the `claude_desktop_config.json` file. 3. Add the JSON configuration from the [Server Setup](#server-setup) section that matches your installation method (Go, Docker, or Binary). -4. Replace `` with your Sysdig Secure host URL and `` with your API token. +4. Replace `` with your Sysdig host URL and `` with your Sysdig Secure or Monitor API token. 5. Save the file and restart the Claude Desktop app. **Connecting to a Remote Server:** From 0cbb31bb92e8f198ae7c9f4bffddf7cb68bcc215 Mon Sep 17 00:00:00 2001 From: Fede Barcelona Date: Tue, 21 Apr 2026 17:33:33 +0200 Subject: [PATCH 2/2] docs: generalize Secure-only wording in token and auth sections --- README.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/README.md b/README.md index 3e68ace..d37e39f 100644 --- a/README.md +++ b/README.md @@ -181,7 +181,7 @@ You can also set the following variables to override the default configuration: - `SYSDIG_MCP_LISTENING_HOST`: The host for the server when it is deployed using remote protocols (`streamable-http`, `sse`). Defaults to all interfaces (`:port`). Set to `127.0.0.1` for local-only access. - `SYSDIG_MCP_STATELESS`: Enable stateless mode for `streamable-http` transport, where each request is self-contained with no session tracking (useful for AWS Bedrock AgentCore). Defaults to: `false`. -You can find your API token in the Sysdig Secure UI under **Settings > Sysdig Secure API**. Make sure to copy the token as it will not be shown again. +You can find your API token in the Sysdig UI under **Settings > Sysdig Secure API** (or **Sysdig Monitor API**). Make sure to copy the token as it will not be shown again. ![API_TOKEN_CONFIG](./docs/assets/settings-config-token.png) ![API_TOKEN_SETTINGS](./docs/assets/api-token-copy.png) @@ -487,9 +487,9 @@ To use the MCP server with a client like Claude or Cursor, you need to provide t ### Authentication -When using the `sse` or `streamable-http` transport, the server requires a Bearer token for authentication. The token is passed in the `X-Sysdig-Token` or default to `Authorization` header of the HTTP request (i.e `Bearer SYSDIG_SECURE_API_TOKEN`). +When using the `sse` or `streamable-http` transport, the server requires a Bearer token for authentication. The token is passed in the `X-Sysdig-Token` or default to `Authorization` header of the HTTP request (i.e `Bearer SYSDIG_MCP_API_TOKEN`). -Additionally, you can specify the Sysdig Secure host by providing the `X-Sysdig-Host` header. +Additionally, you can specify the Sysdig host by providing the `X-Sysdig-Host` header. > **Note:** When provided, the authentication headers (`Authorization`, `X-Sysdig-Token`) and host header (`X-Sysdig-Host`) take precedence over the configured environment variables.