Skill

postgres-mcp

PostgreSQL database operations via MCP - schema inspection, live queries, EXPLAIN analysis. Use when you need to inspect the actual database state, verify migrations, or analyze query performance.

npx claudepluginhub littlelingo/context-engine --plugin context-engine

Tool Access

This skill uses the workspace's default tool permissions.

Preview

Query and inspect your PostgreSQL database directly from Claude Code.

Supporting Assets

REFERENCE.md

SKILL.md

Similar Skills

cache-components

139.3k

Guides Next.js Cache Components and Partial Prerendering (PPR) with cacheComponents enabled. Implements 'use cache', cacheLife(), cacheTag(), revalidateTag(), static/dynamic optimization, and cache debugging.

cache-components

mcp-builder

124.2k

Guides building MCP servers enabling LLMs to interact with external services via tools. Covers best practices, TypeScript/Node (MCP SDK), Python (FastMCP).

9 files

anthropics-skills-13

canvas-design

124.2k

Generates original PNG/PDF visual art via design philosophy manifestos for posters, graphics, and static designs on user request.

20 files

anthropics-skills-13

Stats

Stars1

Forks0

Last CommitMar 30, 2026

Actions

View Source View Plugin View on GitHub View README

Help us improve

Share bugs, ideas, or general feedback.

PostgreSQL MCP - Live Database Access

Query and inspect your PostgreSQL database directly from Claude Code.

When to Use

Before writing migrations: Inspect current schema to confirm starting state

After running migrations: Verify the migration applied correctly

Query development: Test queries against real data before committing

Performance analysis: Run EXPLAIN ANALYZE on queries you're writing

Debugging data issues: Inspect actual data to understand bugs

Workflow: Pre-Migration Verification

List current tables to understand state

Describe the table you're about to modify

Write and apply the migration

Describe the table again to verify

Run a test query to confirm data integrity

Workflow: Query Optimization

Write the query

Run with EXPLAIN ANALYZE to see the plan

Identify sequential scans on large tables

Add appropriate indexes

Re-run EXPLAIN ANALYZE to verify improvement

Output Rules

Always use LIMIT clauses in exploratory queries (default LIMIT 20)

Query specific tables rather than dumping full schema — use \d tablename not \dt *

Use EXPLAIN (without ANALYZE) first; only add ANALYZE when you need actual timing data

Multi-query exploration sessions (3+ queries) should be delegated to a subagent to keep raw result sets out of lead agent context

Safety Rules

Default server is READ-ONLY - it cannot modify data

Enhanced server (@henkey) allows writes - use with caution

Never store connection strings in committed files

Use environment variables for credentials

For available tools and MCP configuration options, read REFERENCE.md in this directory.

PostgreSQL MCP - Live Database Access

Query and inspect your PostgreSQL database directly from Claude Code.

When to Use

Before writing migrations: Inspect current schema to confirm starting state
After running migrations: Verify the migration applied correctly
Query development: Test queries against real data before committing
Performance analysis: Run EXPLAIN ANALYZE on queries you're writing
Debugging data issues: Inspect actual data to understand bugs

Workflow: Pre-Migration Verification

List current tables to understand state
Describe the table you're about to modify
Write and apply the migration
Describe the table again to verify
Run a test query to confirm data integrity

Workflow: Query Optimization

Write the query
Run with EXPLAIN ANALYZE to see the plan
Identify sequential scans on large tables
Add appropriate indexes
Re-run EXPLAIN ANALYZE to verify improvement

Output Rules

Always use LIMIT clauses in exploratory queries (default LIMIT 20)
Query specific tables rather than dumping full schema — use \d tablename not \dt *
Use EXPLAIN (without ANALYZE) first; only add ANALYZE when you need actual timing data
Multi-query exploration sessions (3+ queries) should be delegated to a subagent to keep raw result sets out of lead agent context

Safety Rules

Default server is READ-ONLY - it cannot modify data
Enhanced server (@henkey) allows writes - use with caution
Never store connection strings in committed files
Use environment variables for credentials

For available tools and MCP configuration options, read REFERENCE.md in this directory.