1,517 mods tagged PostgreSQL that install into Claude Code, measured the same four ways as everything else here: what each costs in tokens on every session, what a security scan found and why, whether it is the original, and what changed.
MCP server exposing Postgres, Redis, Elasticsearch, MySQL, MongoDB, and LDAP as tools, with lazy connection management, retry, circuit breaking, per-connection read-only mode, and optional database drivers. Runs locally from the mcp-server-db npm package.
★not rated 81 1mo agoASocket: warn
tokens not measured
originalMIT
The backend platform for AI-native developers. A Postgres-based backend with auth, storage, compute, hosting, and AI gateway — built for coding agents. This plugin gives agents the full InsForge surface: database CRUD with RLS, authentication, storage, edge functions, AI, realtime, Stripe payments, and deployments.…
★not rated 43▲
+2 1mo agoA
tokens not measured
originalApache-2.0
Business intelligence analysis agent for PostgreSQL that discovers database metadata, generates SQL queries for revenue/customer/product metrics, and produces comprehensive analytical reports.
Official Supabase plugin for Claude Code with bundled Supabase skills and MCP access for project management, database work, auth, storage, and Postgres best practices.
★not rated 37▲
+1
changed 6d agoA
tokens not measured
Consort: a Spec-First Branched-Database TDD agent framework for building transactional applications on Lakebase (Databricks' serverless Postgres/OLTP database, not the Delta Lakehouse). A deterministic orchestrator drives role agents through a spec-first design lane and a test-driven build lane whose every cycle runs…
★not rated 34▲
+1
changed yesterdayA
tokens not measured
Detects and remediates table and index bloat in PostgreSQL using pgstattuple analysis. Identifies fragmentation, dead tuples, and wasted space with prioritized maintenance actions including VACUUM, REINDEX, and pgrepack recommendations.
Provision PostgreSQL, manage Apache Kafka, and deploy apps with Aiven - all from your AI assistant. Runs locally from the mcp-aiven npm package. Needs 4 environment variables to run.
★not rated 28 yesterdayA
tokens not measured
originalApache-2.0
Use when writing new Rails code for the PostgreSQL + Hotwire + Tailwind stack. Not for general architecture review. Trigger words: stack conventions, PostgreSQL, Hotwire, Tailwind, Turbo, Stimulus.
Lets the agent inspect a PostgreSQL database schema and run read-only SQL queries against it. Runs locally from the @modelcontextprotocol/server-postgres npm package. Needs 1 environment variable to run.
Configure, review, operate, and troubleshoot the pgroles Kubernetes operator and PostgresPolicy resources. Use when editing a PostgresPolicy or Helm release, reviewing or approving plans, diagnosing conflicts or status conditions, forcing reconciliation, or coordinating maintenance with the operator.
Diagnose and fix excessive Postgres egress (network data transfer) in a codebase. Use when a user mentions high database bills, unexpected data transfer costs, network transfer charges, egress spikes, "why is my Neon bill so high", "database costs jumped", SELECT optimization, query overfetching, reduce Neon costs…
Lets the agent inspect a PostgreSQL database schema and run read-only SQL queries against it. Runs locally from the @modelcontextprotocol/server-postgres npm package.
Use this skill whenever the user is working with Drizzle ORM on PostgreSQL. This covers any mention of Drizzle, drizzle-orm, drizzle-kit, drizzle-zod, pgTable, defineRelations, relations(), db.select(), db.query, or insert/update/delete against Postgres. Typical intents to trigger on: Designing or debugging Postgres…
Select and connect the right vector-store backend for the vector-mcp MCP server — chromadb, postgres/pgvector, qdrant, couchbase, or mongodb — and supply the correct dbtype/connection parameters that every collection and search call needs. Use when the agent must decide which engine to target, wire up…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: