mcpField
I
infra-postgres

infra-postgres

github.com/clickhouseCloud & DevOps5623.3k installsUpdated 1w ago
Repository

About infra-postgres

infra-postgres guides agents using clickhousectl to manage local Postgres and managed Postgres in ClickHouse Cloud. It covers operations and migration workflows.

Key features

  1. 01Separates local and cloud workflows
  2. 02Routes to the relevant reference
  3. 03Covers cloud service operations
  4. 04Provides migration workflow guidance
  5. 05Provides CLI installation guidance

Use cases

  1. 01Run local Postgres for development or tests
  2. 02Operate a cloud Postgres service
  3. 03Migrate existing Postgres to ClickHouse Cloud Postgres

Install

Copy the command and run it in a terminal.

$npx skills add https://github.com/clickhouse/agent-skills --skill infra-postgres

After installing, type/infra-postgresin Claude Code to confirm it loaded.

Bundled files

References and scripts installed along with SKILL.md.

metadata.json
README.md
ref/
cloud.md
local.md
migrate.md

Details

From the project README

Postgres with clickhousectl

clickhousectl manages Postgres in two environments:

  • Local — named, Docker-backed Postgres instances on the user's machine, for development.
  • Cloud — managed Postgres services in ClickHouse Cloud (beta), for production: HA, read replicas, point-in-time restore.

This file routes to the right reference. The step-by-step workflows live in ref/local.md, ref/cloud.md, and ref/migrate.md — read the one that matches the user's situation before running commands.

Which reference to use

The user wants to...Read
Develop or prototype locally, run tests/CI against Postgres, no cloud account neededref/local.md
Go to production, host a managed Postgres, or use ClickHouse Cloud explicitlyref/cloud.md
Operate an existing cloud service (passwords, TLS, config, replicas, failover, restore)ref/cloud.md
Migrate an existing Postgres (Neon, Supabase, RDS, ...) into ClickHouse Cloud Postgresref/migrate.md
Develop locally now, ship to production laterStart with ref/local.md; it points to ref/cloud.md when it's time to go to prod

If it's genuinely ambiguous (e.g. "set up Postgres for my app"), default to local for development tasks and ask before creating anything in the cloud — cloud services cost money.

Prerequisites (both workflows)

Check that clickhousectl is installed:

which clickhousectl

If not found, install it:

curl -fsSL https://clickhouse.com/cli | sh

This installs to ~/.local/bin/clickhousectl (with a chctl alias). If the command is still not found, suggest export PATH="$HOME/.local/bin:$PATH" or a new terminal.

All commands accept --json for machine-readable output. Exit codes follow gh conventions: 0 success, 1 error, 2 cancelled, 4 auth required.

Related

  • To replicate Postgres data into ClickHouse for analytics, see ClickPipes (clickhousectl cloud clickpipe --help). ClickPipes cannot target a Postgres service — for Postgres-to-Postgres migration use ref/migrate.md.
  • For ClickHouse itself (local development or ClickHouse Cloud services), use the infra-clickhouse skill.

Comments

Markdown supported