From 27031377fbacc13a0c14fc3750919ce36d6a321a Mon Sep 17 00:00:00 2001 From: Lev Kokotov Date: Tue, 10 Nov 2026 14:46:46 -0800 Subject: [PATCH] feat: add proxy_config tool docs --- docs/enterprise_edition/mcp.md | 1 + 1 file changed, 1 insertion(+) diff --git a/docs/enterprise_edition/mcp.md b/docs/enterprise_edition/mcp.md index 5327adbf..506be6f6 100644 --- a/docs/enterprise_edition/mcp.md +++ b/docs/enterprise_edition/mcp.md @@ -127,6 +127,7 @@ The MCP server comes with four tools: | `pgdog.proxy_instances` | Show an up-to-date list of PgDog instances currently running. | | | `pgdog.proxy_metrics` | Fetch real-time PgDog metrics. The tool allows you to filter by database/user, by Kube instance name, and by time window. | | `pgdog.proxy_logs` | Fetch real-time logs from Kube containers running PgDog. | +| `pgdog.proxy_config` | Fetch latest configuration loaded into each PgDog instance. | | `pgdog.auth_check` | A no-op tool that allows you to verify if the harness has the correct Bearer token. | An agent typically doesn't need special instructions to use these tools. For example, a common prompt to debug a production incident could be: