MCPg CLAUDE.md

Repository instructions for MCPg, a PostgreSQL database server that exposes database operations to AI assistants through MCP. PostgreSQL is a relational database system, and MCP is a standard for connecting assistants to tools.

In plain words
What is it for?
Use them when changing, testing, documenting, packaging, or checking the safety rules of the MCPg server.
Why use it?
They point the coding agent to the project's source of truth and emphasize checking claims against the code, command line, or live service.

Instructions file

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add instructions/devopam/mcpg/claude-md
Clone the repo
git clone --depth 1 https://github.com/devopam/MCPg
Per session 1,295 This file is loaded in full into every session.
When invoked 1,295 The same file — it is already loaded in full.
Security scan A 0 findings. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.01295 $0.01295
Opus 5 $0.00647 $0.00647
Sonnet 5 $0.00259 $0.00259
Haiku 4.5 $0.00129 $0.00129

Measured 2d ago against content hash c951a42f7cc4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

MCPg CLAUDE.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

CLAUDE.md · 94 lines

How it starts

The opening of the file, as written. The whole thing — 94 lines — stays where its author put it; the contents beside it link to each section on GitHub.

CLAUDE.md — MCPg project memory

Durable facts and conventions for working in this repo. Kept short so it stays true; verify anything here against the code before relying on it.

What MCPg is

A production-grade PostgreSQL MCP server. Single-process, async (asyncio), Python 3.12–3.14. 254 MCP tools (read-only mode exposes a subset). Ships to PyPI (mcpg), GHCR, the MCP registry, Smithery, and a read-only HF Spaces demo.

Golden rules

  • Verify before you write — especially docs. Every claim in a doc must be checked against the code, the CLI, or a live endpoint, never from memory. This is a hard project rule.
  • Generated beats hand-maintained. If a catalogue can drift, it's generated and guarded by a test. Don't hand-edit generated blocks.
  • Commit per logical slice, push often. Big multi-batch changes have been lost to context resets — small commits survive.
  • Never hand-edit src/mcpg/_vendor/ (see below).

Source-of-truth map (don't duplicate these — point at them)

  • Version: src/mcpg/__init__.py __version__. pyproject.toml reads it dynamically via hatchling (dynamic = ["version"]). The MCPB bundle pins are synced by packaging/mcpb/sync_version.py; tests/unit/test_mcpb_bundle.py enforces the match. A release bumps exactly one line.
  • Tool surface: tests/contract/tool_surface.snapshot.json (256 tools) is the contract. about.py's tool_count = len(tool_names). Two contract snapshots (surface + return shapes) — regenerate with MCPG_REGENERATE_TOOL_SNAPSHOT=1 / MCPG_REGENERATE_TOOL_RETURN_SHAPES=1 and commit the diffs.
  • Doc reference tables: the tool index (docs/tools.md) and module map (docs/architecture.md) are generated by tools/generate_doc_tables.py and guarded by tests/contract/test_doc_tables.py. Regenerate and paste between the <!-- BEGIN/END generated --> markers; don't hand-edit.
  • Access modes: src/mcpg/policy.py. read-only (reads) / restricted (reads + DML writes — the "safe read-write" tier) / unrestricted (everything). DDL / SHELL / LISTEN (and MIGRATE, which piggybacks on DDL) each additionally need MCPG_ALLOW_* in unrestricted mode.
  • NL→SQL providers: 19 built-in via the _PROVIDERS registry in src/mcpg/nl2sql.py (single source; deviating key env vars: HF_TOKEN, GITHUB_TOKEN, DEEPINFRA_TOKEN). The provider table in docs/user-guide.md mirrors it.

Read the full file on GitHub · 94 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 94 lines · 1,295 tokens per session scan A c951a42f7cc4

Subscribe to this mod's changes

MCPg CLAUDE.md is an instructions file published in the GitHub repository devopam/MCPg (9 stars, last pushed 7d ago), licensed MIT. It adds 1,295 tokens to every session, about $0.0065 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.