mcpbeat

Multitenant Up

posthog/multitenant-up

Build, deploy, and port-forward the multi-tenant control plane on local Kubernetes. Use when you need to test duckgres in multi-tenant mode with per-team worker pools.

364 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
160
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/PostHog/duckgres --skill multitenant-up

The instruction itself

as written by the author

Boot up the multi-tenant K8s stack:

  • Build and deploy:
   just run-multitenant-local
  • Kill any stale port-forwards and start fresh ones:
   pkill -f 'port-forward.*duckgres' 2>/dev/null; sleep 1
   kubectl -n duckgres port-forward svc/duckgres 5432:5432 &>/dev/null &
   kubectl -n duckgres port-forward svc/duckgres 8815:8815 &>/dev/null &
   kubectl -n duckgres port-forward deployment/duckgres-control-plane 9090:9090 &>/dev/null &
  • Grab the admin API token:
   kubectl -n duckgres logs deployment/duckgres-control-plane | grep 'admin API token'
  • Extract the TLS cert for Flight SQL clients:
   kubectl -n duckgres exec deployment/duckgres-control-plane -- cat /certs/server.crt > /tmp/duckgres-server.crt
  • Report to the user:
  • Admin dashboard: http://localhost:9090 (show the token)
  • PG: PGSSLMODE=require PGPASSWORD=postgres psql -h localhost -U postgres
  • Flight SQL (DuckDB): GRPC_DEFAULT_SSL_ROOTS_FILE_PATH=/tmp/duckgres-server.crt duckdb then INSTALL duckhog FROM community; LOAD duckhog; ATTACH 'hog:memory?user=postgres&password=postgres&flight_server=grpc+tls://localhost:8815' AS mt;
  • Default credentials: postgres / postgres

How to use it

Copy the folder

Take posthog/multitenant-up from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.