List your agent

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

MCP server · hosted · v2026.10.22 · io.ddx.pg/archive
Online · tested 1h agoNEW · 3h agoSeen in the registry 2h ago

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

Website ↗How to connect ↓

What it does

pg.ddx.io: the PostgreSQL community's memory is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.

From the publisher's description, Electra Index matched it to one capability: sql querying. That makes it a candidate for tasks such as query databases in plain language or build data pipelines.

Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence) and are not a test of the tool.

At a glance

Hosted (remote)YES
Local installNO
Version2026.10.22
PriceNot in the registry
First seen23 Oct 2026
Last checked2h ago

How to connect

As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 1h ago (live check)

Hosted endpoints

  • https://pg.ddx.io/mcp streamable-http
  • https://pg.ddx.io/mcp/sse sse

In Claude Code: claude mcp add --transport http pg-ddx-io-the-postgresql-community-s-memory https://pg.ddx.io/mcp

MCP settings (Claude Desktop, Cursor and other MCP clients)

{
  "mcpServers": {
    "pg-ddx-io-the-postgresql-community-s-memory": {
      "url": "https://pg.ddx.io/mcp"
    }
  }
}

Live check

Electra Index connected to the hosted endpoint 1h ago

ONLINE pg.ddx.io: the PostgreSQL community's memory answered an MCP connection on 23 Oct 2026 and introduced itself as pg.ddx.io 1.0 (MCP protocol 2025-06-18).

29 tools offered to AI assistants

  • retrieve_context · START 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 per thread, each the a
  • commit_buildfarm_status · Buildfarm results for one PostgreSQL commit: every animal that built it, with branch, status (passed/failed/flapping), the failing stage and the log url, plus a {passed, failed, flapping, unknown} rollup. commit_sha is a SHA (>= 7 hex) or a
  • commit_history · Everything linked to one commit: subject, author and date with its sha, the mail thread its Discussion: link names (participants resolved to people and organizations), the commitfest entry if tracked, and Discord mentions. commit_id takes a
  • find_failing_patches · Commitfest entries whose latest cfbot build fails on at least one platform: cf_id, title, entry_status and commitfest_number. entry_status filters (default the active reviewable statuses, e.g. needs-review, ready-for-committer); platform na
  • get_attachment · The content of one attachment of a mail message (a patch, a log, a test case), chosen by 1-based index or a filename substring, as listed in get_message/get_thread attachments. Text attachments come back as decoded text (a .patch is ready t
  • get_callers · Reverse call graph: the symbols that call or reference qualified_name (from search_symbols), each with its file and lines, like `git grep -w <name>` restricted to call sites. HEAD only; macro expansion and function pointers are not followed
  • get_contributor · A contributor's profile by email (exact) or name (substring): canonical name, page hash, totals and per-release counts by role (authored, reviewed, committed, reported, ...), the 5 latest credited commits with sha, and buildfarm animals the
  • get_doc_page · One PostgreSQL documentation page as text: path (e.g. "brin.html" or "sql-createtable.html") and optional version ("17", "current"; default the latest). Returns its url, path and stored text (body) with fetched_at. Use search_docs to find t
  • get_entry · One commitfest entry by cf_id (the number in commitfest.postgresql.org/patch/<cf_id>/): title, status, commitfest, authors, reviewers, committer, its mail threads and branches. Read the thread with get_thread; cfbot state with find_failing_
  • get_message · One mail message by Message-ID: headers, in_reply_to/references, decoded body text (by default the author's own words: quotes, signature and inline patch removed; full_text=true for everything, quotes included), attachments [{index, filenam
  • get_thread · A mail thread, found by any Message-ID in it, oldest first. Each message: from, to, cc, date, message_id, decoded body text (by default the author's own words: quoted replies, signature and inline patch removed; full_text=true for the whole
  • get_wiki_page · One wiki.postgresql.org page by title: its latest revision content with author and date. Titles are as on the wiki ("Don't Do This", "Todo"). Use search_wiki to find a title, get_wiki_history for older revisions. Cite https://wiki.postgresq
Show 17 more
  • git_log · Commit history like `git log`, newest first, filtered by path (commits touching a file), author (substring), since/until (YYYY-MM-DD or RFC 3339) and branch (any branch, tag or major version such as 17 or 9.6; default the indexed default br
  • git_search · Search postgres commit messages (or file paths with search_in=paths) by keywords, newest first (all words must appear, case-insensitive; like `git log -i --grep` with every word). Each commit: sha (40-hex, cite it), commit_id, message, auth
  • hybrid_search · Mailing-list search, keyword (BM25 over the authors' own words) and semantic (embeddings) blended per thread, over every list unless inbox names one or more. Returns up to limit threads (default 20, max 50), best first, each its best messag
  • list_sources · Every source behind this server with its kind (inbox, repository, docs, wiki, discord), item count, last update and freshness (fresh/stale): the 56 mailing lists, the git repositories, the documentation releases, the wiki and Discord. Use i
  • search_commitfest · Full-text search of commitfest entries (title first, then author/reviewer/committer names), in the current commitfest by default, or commitfests="all" (back to 2014) or a comma list of numbers. Websearch syntax: "phrase", -term, or. Each re
  • search · Keyword search of mailing-list messages (BM25 over subject, sender and the authors' own words), every list unless inbox narrows it. Prefixes: s:subject f:from t:to d:2024-01..2025-01 b:body. Returns messages best first (limit default 50, ma
  • search_docs · Full-text search of the PostgreSQL documentation (websearch syntax: "phrase", -term, or), title matches first. Searches the current release unless version (one, e.g. "17") or versions (several) is given; a page matching in several selected
  • search_symbols · Find C functions, macros, types and variables by name in the indexed source (HEAD): BM25 on names, then fuzzy and body matches. Filter by kind (function, struct, macro, ...), language, repository. Each result: qualified_name, name, kind, la
  • search_wiki · Full-text search (websearch syntax) of wiki.postgresql.org. By default searches each page's current text; history=true searches every revision and returns, per page, the latest matching revision (rev_id, revision_url, author, comment, times
  • cross_reference · What relates to one stored item. ref: a Message-ID or message URL, a commit SHA, repo@sha or commit URL, a docs URL or page.html, a wiki URL or title, a commitfest URL, or CVE-YYYY-NNNNN. Returns the related mail threads, commits, docs page
  • whats_new · Catch up: everything a person or group did, and where they were named, in a window, newest first per kind (mail grouped by thread). who: a name (fuzzy; close matches return ambiguous [{name, hash}]), email, hash:<8 hex>, team:<slug>, org:<n
  • code_search · Search the postgres source at any commit, branch, tag or date (or across history), from the code-history index: every line of every commit, byte-exact. A literal by default; match=regex for a PostgreSQL regex (^ and $ are per line; \b \< \>
  • read_file · Read a file of the postgres source at any commit, branch, tag or date from the code-history index: numbered lines, at most 2000 per call (page with start_line/end_line), byte-exact to git. Says total_lines and complete; binary files return
  • list_files · List the files of the postgres source under a directory at any commit, branch, tag or date (code-history index), with line counts; depth folds deeper paths into directories with file counts; glob filters paths.
  • blame · Per-line blame of a postgres file at any commit (code-history index): the commit that wrote each line, as `git blame` with git's default diff. ignore_revs (default true) passes through the pgindent/reformat commits of .git-blame-ignore-revs
  • get_commit · One postgres commit from the code-history index: message, parsed trailers (names only), Discussion threads (links to the archived thread on /m/), back-patch siblings on other branches, the first release tag on each branch that contains it,
  • search_commits · Search postgres commits (code-history index), newest first, like git log: range (a rev, or A..B; default the newest release branch), message (regex, case-insensitive), author (regex over author, committer and Author/Co-authored-by/Reviewed-

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. $9.99/month.

Tasks it helps with

Share of each task's required capabilities it covers
Query databases in plain language
SQL Querying
50%
Build data pipelines
SQL Querying
33%

Similar tools

Listed for the same task: query databases in plain language
  • metabase-ai-assistantREMOTELOCAL
    MCP Server for Metabase - 111 tools for SQL generation, dashboards & PostgreSQL
  • Anomaly AIREMOTELOCAL
    AI data analyst: ask about your Excel, CSV, GA4 or database data and get charts and dashboards back
  • Tableau Workbook AuditorREMOTELOCAL
    Local-only Tableau .twbx audit: lineage, unused fields, duplicate calcs, SQL, version diffs
  • HotelinkREMOTELOCAL
    Read-only hotel data (OAuth). Guide: https://mcp.hotelink.ai/llms.txt. Verify with list_datasets
  • Vitrus analyticsREMOTELOCAL
    Read-only analytics for all your apps: users, AI traffic, revenue, with the SQL behind every number
  • Atera MCPREMOTELOCAL
    Every Atera RMM + PSA endpoint, plus a local SQLite mirror that answers fleet-health, SLA, and

Ready-made AI agents

An MCP server is a connector you add to your own assistant. These are finished products that do the same job for you:

Facts & evidence

Each fact shows where it was seen and when.
FactValueEvidenceSourceLast confirmed
Hosted endpointhttps://pg.ddx.io/mcp, https://pg.ddx.io/mcp/sseDECLAREDSRC-001 Official MCP Registry2h ago
Local install (package)noDECLAREDSRC-001 Official MCP Registry2h ago
Remote access (hosted)yesDECLAREDSRC-001 Official MCP Registry2h ago
Websitehttps://pg.ddx.io/DECLAREDSRC-001 Official MCP Registry2h ago
Registry statusactiveDECLAREDSRC-001 Official MCP Registry2h ago
Version2026.10.22DECLAREDSRC-001 Official MCP Registry2h ago
MCP serveryesDECLAREDSRC-001 Official MCP Registry2h ago

Change history

  • NEW23 Oct 2026
    first seen in the index

Is this page accurate?

Flag it and our robot re-checks the official source. Reports never change a score.

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

How do I connect pg.ddx.io: the PostgreSQL community's memory?

Use the hosted endpoint https://pg.ddx.io/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.

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

When Electra Index connected on 23 Oct 2026, it listed 29 tools: retrieve_context, commit_buildfarm_status, commit_history, find_failing_patches, get_attachment, get_callers, get_contributor, get_doc_page and more. The full list is in "Live check" above.

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

Yes. Its hosted endpoint answered an MCP connection from Electra Index 1h ago.

What can I use pg.ddx.io: the PostgreSQL community's memory for?

Based on its description, it is most relevant to: query databases in plain language, build data pipelines.