Agents Index

pg.ddx.io: the PostgreSQL community's memory

OnlineOfficialNew

Every PostgreSQL mailing list since 1991, linked to the commits, code, commitfest and docs.

Visit publisherConnectJSON

What it can do: 80 tools

  • retrieve_context read-onlySTART HERE for a question about PostgreSQL. Searches every mailing list (inbox narrows it) with hybrid keyword + semantic ranking and returns cited passages that fit token_budget (default 4000, max 32000): one passage pe
  • animal_history read-onlyOne animal's runs, newest first; branch and since filter.
  • animal_owner_contributions read-onlyAnimals one owner runs (owner_name or owner_email; at least one): the branches each tracks, last status, first_seen_at and days since.
  • blame_symbol read-onlyThe commits that changed a symbol's lines in its file.
  • browse_by_date read-onlyThreads active in a date range [since, until) on one list.
  • build_status_freshness read-onlycfbot data age: last_build_at is the newest build finish time held (from GitHub Actions), seen_at the newest time our sync saw a result, build_count the builds stored. An old seen_at means our cfbot scraper stalled; an o
  • buildfarm_overview read-onlyBuildfarm health: animal count, recent runs, failing animals, top owners, OS / branch breakdown, freshness.
  • check_upstream_status read-onlyWas a pull request merged upstream: the patch series' latest head commit and any merge information.
  • code_index_status read-onlyCode index statistics: files, symbols by kind and language, edges, communities.
  • codebase_map read-onlyFile and symbol counts per directory.
  • commit_buildfarm_status read-onlyBuildfarm results for one postgres commit: each animal that built it with branch, status (passed/failed/flapping), failing stage and log url, and a {passed, failed, flapping, unknown} rollup. Cite the SHA and log urls.
  • commit_history read-onlyEverything linked to one commit: subject, author and date with its sha, the message body (commit.message, trailers removed), the mail thread its Discussion: link names (participants resolved to people and organizations),
  • commitfest_stats read-onlyAll commitfests: entries by status, top authors, and totals of people, commitfests and entries.
  • contribution_summary read-onlyPer release: people, distinct commits, count of commits per role (canonical authoritative repos only), revert commits.
  • detect_changes read-onlyThe symbols that changed between two commits (file content hashes).
  • discussion_links read-onlyA commit's Discussion / Closes / Fixes / Backpatch-through trailers: raw text and extracted URL. The mail they lead to, the committers announcement and mail citing the SHA: git_search (mail_refs).
  • embedding_status read-onlyEmbedding coverage of a list: messages embedded, model, last run.
  • entry_branches read-onlyRepository branches tracked for a commitfest entry: repo, branch_name, is_authoritative.
  • entry_history read-onlyAn entry's status across commitfests, matched by shared thread Message-ID (precise), else by title prefix (weak).
  • find_breaks read-onlyAnimals that failed on a branch between two commits: from the first run of from_commit to the last run of to_commit on that branch (run times, not git order: the buildfarm has no commit order).
  • find_contributions read-onlyOne person's contribution rows: commit SHAs and animals, each with role and release. By email, else name.
  • find_dead_code read-onlyFunctions and methods nothing calls (no incoming call edges).
  • find_entries_for_author read-onlyCommitfest entries a person authored: email (exact) or name (substring, case-sensitive).
  • find_entries_for_thread read-onlyCommitfest entries whose page links any message of the thread.
  • find_entries_with_failures_on read-onlyAn animal's recent failed runs, and commitfest entries failing in cfbot on branches it tracks. Correlated by branch and time (buildfarm builds commits, cfbot cf/<id> branches), not joined.
  • find_failing_patches read-onlyCommitfest entries whose latest cfbot build fails on a platform: cf_id, title, entry_status, needs_rebase (the build is of an older version: the newest does not apply), commitfest_number. Cite https://commitfest.postgres
  • find_failing_runs read-onlyThe newest failing buildfarm runs fleet-wide: what is broken now.
  • find_passing_long_pending read-onlyEntries green on every platform that apply to master, not updated for min_days: why isn't it committed?
  • find_patches_by_platform_status read-onlyEntries passing on one platform and failing on another (e.g. linux vs macos: a portability bug).
  • find_pattern read-onlyRegex search of code symbol bodies (trigram-indexed).
  • find_rebase_needed_patches read-onlyEntries cfbot says no longer apply to master: they need a rebase.
  • find_related_discussions read-onlyMail related to a commit, topic or PR. A postgres commit SHA (7-40 hex): the mail that refers to it (match_mode commit): Discussion: threads, then the committers announcement, then mail citing the hash, each with how_it_
  • find_similar_messages read-onlyMessages near one message by embedding: related or duplicate threads.
  • get_animal read-onlyOne animal: hardware, OS, compiler, owner, branches, last status, its last 20 runs.
  • get_attachment read-onlyOne attachment of a message, whole: by 1-based index or filename substring (as get_message/get_thread list them). Text as text whatever its type (a .patch is ready for git apply); binary as base64 (encoding=base64). size
  • get_author_messages read-onlyOne list's messages from a sender (name or address, as search's f:), newest first; since/until bound them.
  • get_callees read-onlyWhat a symbol calls or references (forward call graph).
  • get_callers read-onlyReverse call graph: who calls or references qualified_name, with file and lines (like `git grep -w` on call sites). HEAD only; macros and function pointers are not followed. Read one with git_show_file at its line.
  • get_commitfest read-onlyOne commitfest: entries by status and its top authors.
  • get_communities read-onlyLouvain clusters of the call graph: related symbols by functional area.

…and 40 more.

Connect it

Claude Code
claude mcp add --transport http pg-ddx-io-the-postgresql-community-s-mem https://pg.ddx.io/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://pg.ddx.io/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "pg-ddx-io-the-postgresql-community-s-mem": {
      "url": "https://pg.ddx.io/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "pg-ddx-io-the-postgresql-community-s-mem": {
      "type": "http",
      "url": "https://pg.ddx.io/mcp"
    }
  }
}

Questions

What does pg.ddx.io: the PostgreSQL community's memory do?

Every PostgreSQL mailing list since 1991, linked to the commits, code, commitfest and docs. It exposes 80 tools to AI assistants.

What tools does pg.ddx.io: the PostgreSQL community's memory provide?

80 tools, including retrieve_context, animal_history, animal_owner_contributions, blame_symbol, browse_by_date, build_status_freshness, buildfarm_overview, check_upstream_status, code_index_status, codebase_map, commit_buildfarm_status, commit_history….

How do I connect pg.ddx.io: the PostgreSQL community's memory to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://pg.ddx.io/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does pg.ddx.io: the PostgreSQL community's memory require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is pg.ddx.io: the PostgreSQL community's memory online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes pg.ddx.io: the PostgreSQL community's memory?

pg.ddx.io. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Developer Tools