## Description This PR adds two read-only, PostgreSQL tool kinds to MCPToolbox that standardize discovery of extensions: - `postgres-list-installed-extensions` – lists extensions installed in the current database with: `name`, `version`, `schema`, `owner` `description`. - `postgres-list-available-extensions` – lists extensions available to install on the cluster with: `name`, `default_version`, `description`. Both are safe by default, and return well-typed JSON suitable for UIs, agents, and automation. **Test Output** - `list_installed_extensions` <img width="1414" height="781" alt="image" src="https://github.com/user-attachments/assets/aab102a7-90ab-4516-9bc2-bcbfdab02bb1" /> - `list_available_extensions` <img width="1421" height="774" alt="image" src="https://github.com/user-attachments/assets/a4f80f22-bb2e-4350-acb2-12eb020d88cb" /> --- > Should include a concise description of the changes (bug or feature), it's > impact, along with a summary of the solution ## PR Checklist --- > Thank you for opening a Pull Request! Before submitting your PR, there are a > few things you can do to make sure it goes smoothly: - [x] Make sure you reviewed [CONTRIBUTING.md](https://github.com/googleapis/genai-toolbox/blob/main/CONTRIBUTING.md) - [x] Make sure to open an issue as a [bug/issue](https://github.com/googleapis/genai-toolbox/issues/new/choose) before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea - [x] Ensure the tests and linter pass - [x] Code coverage does not decrease (if any source code was changed) - [x] Appropriate docs were updated (if necessary) - [x] Make sure to add `!` if this involve a breaking change 🛠️ Fixes #<issue_number_goes_here>
3.1 KiB
title, type, weight, description
| title | type | weight | description |
|---|---|---|---|
| PostgreSQL | docs | 1 | PostgreSQL is a powerful, open source object-relational database. |
About
PostgreSQL is a powerful, open source object-relational database system with over 35 years of active development that has earned it a strong reputation for reliability, feature robustness, and performance.
Available Tools
-
postgres-sqlExecute SQL queries as prepared statements in PostgreSQL. -
postgres-execute-sqlRun parameterized SQL statements in PostgreSQL. -
postgres-list-tablesList tables in a PostgreSQL database. -
postgres-list-active-queriesList active queries in a PostgreSQL database. -
postgres-list-available-extensionsList available extensions for installation in a PostgreSQL database. -
postgres-list-installed-extensionsList installed extensions in a PostgreSQL database.
Pre-built Configurations
- PostgreSQL using MCP Connect your IDE to PostgreSQL using Toolbox.
Requirements
Database User
This source only uses standard authentication. You will need to create a PostgreSQL user to login to the database with.
Example
sources:
my-pg-source:
kind: postgres
host: 127.0.0.1
port: 5432
database: my_db
user: ${USER_NAME}
password: ${PASSWORD}
{{< notice tip >}} Use environment variable replacement with the format ${ENV_NAME} instead of hardcoding your secrets into the configuration file. {{< /notice >}}
Reference
| field | type | required | description |
|---|---|---|---|
| kind | string | true | Must be "postgres". |
| host | string | true | IP address to connect to (e.g. "127.0.0.1") |
| port | string | true | Port to connect to (e.g. "5432") |
| database | string | true | Name of the Postgres database to connect to (e.g. "my_db"). |
| user | string | true | Name of the Postgres user to connect as (e.g. "my-pg-user"). |
| password | string | true | Password of the Postgres user (e.g. "my-password"). |
| queryParams | map[string]string | false | Raw query to be added to the db connection string. |