Alperen CetinandCopilot App 0a4a57e1b5 Migrate the plugin to the postgres-mcp MCP server (#16) ...

## Summary

Point the plugin's MCP integration at the renamed **`postgres-mcp`**
distribution (formerly `pgsql-tools`), move to its `~/.postgres-mcp`
base folder, and align with its `PGSQL_MCP_` env-var normalization.

## Changes

- **Launcher (`run_mcp.js`)** — pin the CLI to the `postgres-mcp`
releases: release tag `cli-v*` → `mcp-v*`, asset `pgsql-tools-cli-*` →
`postgres-mcp-*`, binary `pgsql-tools` → `postgres-mcp`, start command
`mcp run` → `run`.
- **Base folder** — install/cache directory, PATH entry, and marker
moved from `~/.pgsql-tools-cli` to `~/.postgres-mcp` (co-located with
the binary's own config root).
- **Server registration** — the MCP server key in `.mcp.json` renamed to
`postgres-mcp`.
- **Env vars** — `PGSQL_TOOLS_QUERY_TIMEOUT_MS` →
`PGSQL_MCP_QUERY_TIMEOUT_MS`, and the test fixtures' connection-string
var → `PGSQL_MCP_CONNECTION_STRING`, matching the upstream env-var
normalization.
- **Version pin file** — `PGSQL_TOOLS_CLI_VERSION` →
`POSTGRES_MCP_CLI_VERSION`.
- **Plugin version** — bumped `0.0.1` → `0.1.0` (marketplace + Codex
manifests).
- **Docs / keywords / branding** — remaining `pgsql-tools` references
updated to `postgres-mcp`.

Retained intentionally: the `microsoft/pgsql-tools` GitHub release repo.

## Testing

- End-to-end launcher run: downloads the pinned asset, verifies the
SHA-256 checksum, installs to `~/.postgres-mcp/bin`, and the server
responds as `postgres-mcp`.
- Integration MCP e2e suite (8 tests) green against a real Postgres; 35
non-DB tests pass.

---------

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>

2026-07-15 13:45:02 -05:00

..

plugin

Migrate the plugin to the postgres-mcp MCP server (#16)

2026-07-15 13:45:02 -05:00

workflows

Migrate the plugin to the postgres-mcp MCP server (#16)

2026-07-15 13:45:02 -05:00