Skip to content

feat: add proxy_config tool docs #131

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
levkk merged 1 commit into from
Nov 10, 2026
Merged

feat: add proxy_config tool docs #131

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions docs/enterprise_edition/mcp.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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:
Expand Down
Loading