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

• animal_historywrite actionFree

  Run timeline for one animal. Filterable by branch and start cutoff; ordered newest first.

• animal_owner_contributionsFree

  Animals run by one owner: list, branches each tracks, last status, first_seen_at and elapsed days since first observation.

• blameFree

  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 when they replaced lines one-for-one; reverse adds the commit that removed each line later on the version's branch. At most 2000 lines per call; commits lists author, date and subject per short sha. Not the same as git_blame, which returns a file's commit history.

• blame_symbolFree

  Show the commit history that modified a symbol's file, filtered to the symbol's line range.

• browse_by_dateFree

  Browse threads within a specific date range. Useful for exploring what was discussed during a particular time period.

• build_status_freshnessFree

  Most recent :entry/last-build-at observation across all entries. Use to detect a stalled cfbot scraper.

• buildfarm_overviewFree

  High-level buildfarm health: animal count, recent run counts, currently-failing animals, top owners, OS / branch breakdown, and freshness.

• calendar_feedsFree

  List every pg.ddx.io calendar feed (iCalendar URLs) with event counts: all events, regions, countries, conference series, the PostgreSQL release cycle, teams and organisations.

• check_upstream_statusFree

  Check whether a pull request has been merged upstream. Returns the latest patch series head commit and any merge information.

• code_index_statusFree

  Get code indexing statistics: files indexed, symbol counts by kind and language, edge count, community count.

• code_searchFree

  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 \< \> as in grep), match=identifier for any of snake_case/CamelCase/UPPER spellings. File sets agree with `git grep -l` at the same commit. Results name the resolved sha and ref. complete=false means the totals are lower bounds (cut says why). With history (all | <rev> | A..B) it returns every matching line any commit in the range had, with the commit that added it and the one that removed it.

• codebase_mapFree

  Get a directory-level overview of the codebase showing file counts and symbol counts per directory.

• combine_calendarsFree

  Combine several pg.ddx.io calendar feeds into ONE subscription. Give feed paths or URLs as listed by calendar_feeds (e.g. events/region/europe, series/pgconf-eu, teams/committers, people/<8hex>, https://pg.ddx.io/cal/orgs/edb.ics; 1-200). Returns the combined feed's hash, canonical feed list, https url and webcal url. The same selection always yields the same URL.

• commit_buildfarm_statusFree

  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 branch, tag or major version (17, 9.6) for the commit it points at. Cite the commit SHA and the log urls.

• commit_historyFree

  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. For postgres also first_releases (per branch the change landed on: branch, sha, release e.g. 14.23 or null when unreleased, first_version incl. betas, shipped=false when it was reverted before that release), reverted_by (the commits that revert it, each with its own reverted_by) and reverts, read from git tags and commit messages, never guessed. commit_id takes a SHA (>= 7 hex), branch, tag, major version (17, 9.6), <ref>~N or a commit_id from another tool; repository defaults to postgres. The diff itself is not included (git_diff, or git_show_file for one file). Cite the sha and the thread's https://postgr.es/m/<message_id>.

• commitfest_statsFree

  Overview of all indexed commitfests: count by status, top contributors (entries authored), distinct people / commitfests / entries totals.

• contribution_summaryFree

  Summary of contribution counts per release: unique people, distinct commits, role breakdown (count(DISTINCT commit_sha) per role, canonical authoritative repos only), and revert-commit count. Powers the /community hero strip.

• cross_referenceFree

  What relates to one stored item, and what happened to it. ref: a Message-ID or message URL, a commit SHA or URL, a docs URL or page.html, a wiki URL or title, a commitfest URL, CVE-YYYY-NNNNN, or feature:<words> (matched to commitfest titles; ref.entries_used says which). Returns related threads, commits (with releases and reverted_by), docs, wiki pages, commitfest entries and people, each with why, strongest first: explicit links, shared identifiers, then similar topic. For a postgres commit, thread, entry or feature, timeline says which release shipped it and whether it was reverted or back-patched: status plus dated events (first post, commitfest listings, commits with branch and first release, reverts), each with its source url. kinds narrows; limit_per_kind (default 5, max 25). ~3 s budget: late parts go in timed_out. Same as GET /api/v2/related.

• detect_changesFree

  Detect which symbols changed between two commits by comparing file content hashes.

• discussion_linksFree

  Discussion / Closes / Fixes / Backpatch-through trailers attached to one commit. Returns the raw trailer text and any URL extracted. For the messages those links resolve to, plus the committers announcement and messages citing the SHA, use git_search (mail_refs on each result).

• embedding_statusFree

  Get embedding coverage statistics: how many messages have embeddings, which model was used, and when embeddings were last generated.

• entry_branchesFree

  Repository branches tracked for a commitfest entry. Joins commitfest.entry_repos with ag_repositories so callers see repo name + branch_name + is_authoritative.

• entry_historyFree

  Status changes for a commitfest entry across commitfests. The relational table doesn't carry an audit log, so we approximate the patch's lifeline by joining on shared :entry/thread-message-id (precise) and falling back to title-prefix substring (weak).

• find_breaksFree

  Animals that failed on a branch within the time window bounded by two commit SHAs. The window is defined by the earliest started_at observed for either SHA on that branch — not by git topological order, since the buildfarm tables don't carry commit ordering.

• find_contributionsFree

  Find raw contribution rows for one person: git commit SHAs / buildfarm animals tagged with a role + release. Useful for drill-down on a contributor's recent work.

• find_dead_codeFree

  Find functions/methods with zero incoming call graph edges (potentially unused code).

• find_entries_for_authorFree

  Find commitfest entries where the given person is an author. Looks up by email (exact) or by name (substring, case-sensitive).

• find_entries_for_threadFree

  Find commitfest entries linked to a pgsql-hackers thread by Message-ID. (Returns empty until the mailing-list cross-reference scrape lands; the index attribute :entry/thread-message-id is in the schema.)

• find_entries_with_failures_onFree

  Cross-domain feed: recent failed buildfarm runs for a named animal, plus commitfest entries with cfbot :failing rollups whose tracked branches overlap the animal's. Note: buildfarm runs commit SHAs and cfbot runs cf/<id> branches, so this verb correlates by branch overlap and time window — not by direct schema join.

• find_failing_patchesFree

  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 narrows to one CI platform; limit caps the list. Cite https://commitfest.postgresql.org/patch/<cf_id>/.

• find_failing_runsFree

  Most recent failing buildfarm runs across the entire fleet. Filterable by branch and start cutoff. Use to answer 'what is broken right now?'

• find_passing_long_pendingFree

  Green patches stuck in review: entries whose builds pass on every platform yet whose :entry/last-updated is older than N days. Useful for the 'why isn't this committed yet?' question.

• find_patches_by_platform_statuswrite actionFree

  Patches that pass on some platforms but not others. Example: passing on linux but failing on macos -> portability bug.

• find_patternFree

  Search for a regex pattern in code symbol bodies. Uses trigram indexes for acceleration.

• find_rebase_needed_patchesFree

  Entries cfbot reports as no longer applying to master tip (:entry/applies-cleanly is false). These need an author rebase.

• find_related_discussionsFree

  Find mailing list messages related to a commit, topic, or PR. Searches subject and Message-ID fields via case-insensitive substring; if substring search returns no hits and an embedding provider is configured, falls back to semantic search across all inboxes.

• find_similar_messagesFree

  Find messages similar to a given message using its embedding vector. Useful for finding related discussions or duplicate threads.

• find_string_literalsFree

  Find occurrences of a literal in current (HEAD) source, restricted to a syntactic kind: "strings" (inside double quotes), "comments" (after // or /*), or "all".

• get_animalFree

  Profile of one buildfarm animal: hardware/OS/compiler/owner, branches tracked, last build status, plus the last 20 runs (any branch).

• get_attachmentFree

  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 to read or `git apply`), binary ones as base64 with encoding=base64; size is the decoded byte count. Cite the message as https://postgr.es/m/<message_id>.

• get_author_messagesFree

  Find messages by a specific author, optionally filtered by date range. Uses the f: (from) search prefix.

• get_calleesFree

  Find all symbols that the given symbol calls/references (forward call graph).

• get_callersFree

  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. limit caps the list. Read a caller with git_show_file at its line.

• get_commitFree

  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, first_releases (per branch the change landed on: sha, release such as 14.23, first_version incl. betas, shipped=false when reverted before that release; null release = not yet released), reverted_by and reverts, files changed with line counts, and its diff rendered from the index (at most 3000 lines; diff_complete says whether it was cut). Accepts a SHA (7+ hex), branch, tag or any version form.

• get_commitfestFree

  Get a single commitfest with entries grouped by status and the top contributors (authors with the most entries).

• get_communitiesFree

  List Louvain community clusters detected in the call graph. Communities group related symbols by functional area.

• get_communityFree

  Get details and member symbols for a specific community.

• get_contributorFree

  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 they own. People who hid their page are excluded from name lookups. For what they did recently use whats_new. Cite https://pg.ddx.io/community/<hash>.

• get_contributor_historyFree

  Show all past mailing list submissions by a contributor (matched by email address or name).

• get_dependentsFree

  Get transitive dependents: all symbols in the blast radius if this symbol changes.

• get_doc_pageFree

  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 the path. Cite the returned url.

• get_entryFree

  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_patches. Cite https://commitfest.postgresql.org/patch/<cf_id>/.

• get_execution_flowsFree

  Trace execution flow paths through the call graph from entry points.

• get_impactFree

  Analyze the impact of modifying a symbol: risk level, blast radius, affected communities and execution flows.

• get_inbox_infoFree

  Get metadata for an inbox (name, addresses, message count, last activity)

• get_inbox_statsFree

  Return aggregate statistics about an inbox: message counts by time period, top authors, and activity trends.

• get_inbox_summaryFree

  Per-inbox summary: total messages, top 10 posters, thread count, date range, and lifetime average messages/day (total messages divided by the days spanned by the archive).

• get_messageFree

  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, filename, content_type, size}] and has_patch. Never raw MIME: get_attachment returns an attachment's content, get_raw_message the RFC 822 source. Finds the list itself unless inbox is given. Cite as https://postgr.es/m/<message_id>.

• get_message_headersFree

  Get email headers as structured key/value pairs. Returns all headers or a specific header by name.

• get_message_referencesFree

  Discover cross-references in a message. Returns explicit References/In-Reply-To headers plus any Message-IDs found in the body text, with archive lookup for each.

• get_new_messagesFree

  Return messages newer than a given article number cursor, enabling agents to poll for new messages without re-scanning. Use after=0 for the first call, then use the returned last_article_num as the cursor for subsequent calls.

• get_patch_brancheswrite actionFree

  Get the git branches created from a patch series. Shows what branches were applied from email patches for code intelligence analysis.

• get_patch_build_historywrite actionFree

  Build matrix for one entry: per-platform/config status, log URL, observation time, applies-cleanly flag, rollup.

• get_patch_serieswrite actionFree

  Get patch submission history for a forge pull request URL. Returns all iterations submitted to the mailing list.

• get_raw_messageFree

  Get the complete raw RFC 822 email bytes for a message. Useful for agents that need to parse headers/structure themselves or forward messages.

• get_repo_sync_statsFree

  Get commit frequency analysis and sync statistics for a repository. Returns median commit interval, recommended poll frequency, and recent fetch log.

• get_repository_summaryFree

  Per-repository summary: total commits, top 10 contributors, branches, language breakdown (from indexed symbols), and a sampled most-touched-paths list.

• get_signatureFree

  Get the function/method signature and doc comment for a symbol.

• get_source_infoFree

  Detail for a single source by name. Returns kind, item_count, last_update, next_sync, freshness_status, and description.

• get_symbolFree

  Get full details for a code symbol by its qualified name, including source code, signature, documentation, and file location.

• get_tests_forFree

  Find test symbols that reference the given symbol.

• get_threadFree

  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 decoded text; never raw MIME), attachments [{index, filename, content_type, size}] and has_patch. Paged: 20 messages per call (limit max 500; offset/next_offset/has_more); bodies capped at max_body_chars (default 4000; 0 = no cap; body_truncated marks a cut). include_bodies=false gives a cheap outline. Finds the list itself unless inbox is given. Cite as https://postgr.es/m/<message_id>.

• get_thread_referencesFree

  Cross-reference graph for an entire thread. Collects all Message-IDs referenced in body text across all messages in the thread and resolves which other threads they point to.

• get_wiki_historyFree

  Get revision history for a wiki page.

• get_wiki_pageFree

  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.postgresql.org/wiki/<title>.

• git_analyze_activityFree

  Show commit activity over time, bucketed by period. Useful for understanding development pace and trends.

• git_analyze_authorsFree

  Get commit statistics per author: total commits, first and last commit dates. Ranked by commit count.

• git_analyze_bus_factorFree

  Identify files with the fewest distinct authors (bus factor risk). Files modified by only one person are knowledge silos.

• git_analyze_churnFree

  Identify the most frequently modified files in the repository. High-churn files may indicate hotspots or unstable code.

• git_analyze_couplingFree

  Find files that are frequently changed together. Logical coupling can reveal hidden dependencies between components.

• git_analyze_hotspotsFree

  Aggregate file churn by directory to find the most actively changed areas of the codebase.

• git_blameFree

  File version history, not a per-line blame: the commits that changed a file on the history of a commit (like `git log <rev> -- <path>`), newest first, each with sha, commit_id, author, date, summary and status (added/modified/deleted). Renames are not followed. Up to `limit` commits (default 100, max 1000); has_more says there are older ones.

• git_diffFree

  Two modes: (1) commit-range mode — pass base_branch and head_branch to get the list of commits unique to head_branch (set difference base..head), optionally filtered by author/message/path; (2) content-diff mode — pass from_commit and to_commit to compute file-level unified diffs between two specific commits.

• git_logFree

  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 branch). Each commit: sha (40-hex, cite it), commit_id, message (subject for a branch log), author and dates. limit default 50, max 200; offset pages; has_more. repository defaults to postgres.

• git_searchFree

  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, author, date, people credited, and mail_refs: up to 5 messages that refer to it {inbox, message_id, subject, url, how_it_refers: discussion-trailer, committers-announcement or mentions-hash}. repository defaults to postgres; limit default 50, max 200. Details with commit_history.

• git_show_fileFree

  Read a file at any commit, branch, tag or major version (like `git show <rev>:<path>`), from the git clone. commit takes a SHA (>= 7 hex), branch, tag, 17 or 9.6, <ref>~N or a commit_id; default HEAD; an unknown name or path is an error, never a silent HEAD. Returns at most 2000 lines per call: start_line/end_line pick the range, total_lines gives the length and cut=true says more follow. Lines are numbered with a tab (numbered=false gives the exact bytes). Each result has sha (cite it with the path and lines) and ref. Binary files return a note instead of content.

• grep_repositoryFree

  Literal-text search of the CURRENT source only (HEAD of master for postgres, the default branch elsewhere), like `git grep -F` (regex characters are escaped; case_insensitive=true for -i). Returns up to max_results files (default 50, max 500), each with repo_name, file_path, line_no and snippet (its first matching line). For any other commit, branch, tag, major version or date, for every match with context, or to search history, use code_search (version=, history=). Read a hit with read_file or git_show_file; cite path:line with the sha.

• history-ofFree

  One-shot historical context for CI: given content (a diff, file path, symbol, commit subject, or feature name), return the most relevant default-branch commits, the associated mailing-list discussion (message links), and the tracked people involved (community page links). Read-only; composes git history + list search.

• hybrid_searchFree

  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 message: inbox, message_id, subject, from, date, thread_id, fused_score (0-1), similarity and a short excerpt of the author's own words. Like a ranked `git log --grep` for mail. Cite as https://postgr.es/m/<message_id>; read with get_thread or get_message (inbox from the result). author, since and until restrict both arms to one sender and a date window.

• hybrid_search_codeFree

  Combined keyword + semantic code search using Reciprocal Rank Fusion. Requires embeddings to be generated.

• list_animalsFree

  List PostgreSQL buildfarm animals. Filterable by OS, branch tracked, last build status, or owner. Failing animals are returned first (sort key: last_status='failed' DESC, name ASC).

• list_branchesFree

  List tracked branches for a repository, including head commit and default branch status.

• list_commitfestsFree

  List PostgreSQL commitfests indexed in the mentat triple store. Each commitfest carries a status (:open / :in-progress / :closed) and an entry count grouped by status.

• list_contributorsFree

  List PostgreSQL community contributors aggregated across git trailers (Reviewed-by, Tested-by, etc.), commit author/committer headers, and buildfarm animal owners. Sorted by total contributions descending. Filterable by release / role / source.

• list_discord_channelsFree

  List monitored Discord channels with message counts.

• list_doc_versionsFree

  List available documentation versions with page counts.

• list_entriesFree

  List commitfest entries (proposed patch series). Filterable by status, commitfest number, or topic; paginated.

• list_filesFree

  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.

• list_inboxesFree

  List all configured agora mailboxes with name, message_count, latest_message_date, latest_import_date, listid (when known) and description. Optional min_messages filter; limit/offset are accepted for forward compatibility.

• list_projectsFree

  List bridge-configured projects linking a forge repository to a mailing list inbox.

• list_recentFree

  List recent messages from an inbox

• list_repositoriesFree

  List all registered git repositories with name, branch, commit_count, file_count, indexed-symbol_count, latest_commit, last_fetched_at, and import_state. Optional min_commits and branch filters; limit/offset accepted for forward compatibility.

• list_sourcesFree

  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 it to learn the inbox and repository names other tools accept and how current each is. kind filters; min_items drops small sources.

• list_threadsFree

  Browse recent threads (topic-level view). Returns thread summaries with message counts, date ranges, and latest message metadata.

• read_fileFree

  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 their metadata only.

• recent_commitfest_activityFree

  Rolling window of commitfest entries updated in the last N days. Returns the entries plus a status histogram. Uses the relational commitfest.entries table for predictable latency.

• regex_search_codeFree

  Regular-expression search of the CURRENT source only (HEAD of master for postgres, the default branch elsewhere), like `git grep -E` with grep's line semantics: ^ and $ anchor at line starts and ends, . does not cross lines. PostgreSQL regex syntax (\s, \w, (?i) work). path_glob narrows by SQL LIKE pattern ("src/backend/%.c"), repository by name. Returns up to max_results files (default 50, max 500) with repo_name, file_path, line_no and snippet (its first matching line). For any other commit, branch, tag, major version or date, all matches with context, or history, use code_search with match=regex. Cite path:line with the sha.

• release_contributorsFree

  Top contributors per role for one release. Scope: canonical authoritative repos only (ag_repositories.is_authoritative = TRUE). Returns top 20 per role across authored / reviewed / tested / reported / committed (per-role distinct-commit counts).

• repository_statsFree

  Get detailed statistics for a git repository including commit count, file count, branch, and import state.

• retrieve_contextFree

  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 author's own words (quotes, signature and patch removed, cut at ~1200 chars) with url, inbox, message_id, from and date. found=false with a reason when the archive does not appear to discuss the question, instead of weak matches. Retrieval only: write the answer yourself. Cite each claim with its passage url or https://postgr.es/m/<message_id>; open a thread with get_thread. author, since and until restrict it to what one person wrote in a date window (filter echoes them).

• searchFree

  Keyword search of mailing-list messages (BM25 over subject, sender and the authors' own words), every list unless inbox narrows it. Operators in query: s:/intitle: subject, f:/from: sender, b:/intext: body, after:/before:/d:2024-01..2025-01 dates, site:<list>, filetype:patch, link:<url glob>, /regex/. Returns messages best first (limit default 50, max 200; offset pages; collapse_threads=true keeps one per thread), each with inbox, message_id, subject, from, date, thread_id and an excerpt, plus total and has_more. Use it for exact words, names and identifiers; hybrid_search for questions. Cite as https://postgr.es/m/<message_id>. author, since and until restrict it to one sender and a date window.

• search-regexFree

  Full-text search across mailing list messages using POSIX regex patterns. Supports edit-distance fuzzy matching via the `k` parameter (0 = exact regex, >=1 = up to k insertions/deletions/substitutions per match). Same prefix syntax as `search`: s:subject f:from t:to d:2024-01..2025-01 b:body_text

• search_all_sourcesFree

  Unified search across all document sources (docs, wiki, and email). Returns results ranked by relevance.

• search_commitfestFree

  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 result: cf_id, title, status, commitfest(s), people, last update, the commitfest.postgresql.org patch url and the pg.ddx.io thread link. limit default 20, max 50. Details with get_entry; cite the patch url.

• search_commitsFree

  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-by trailers), paths, since/until (YYYY-MM-DD), changed_lines (a regex an added or removed line matches, as git log -G) and occurrences (a string whose count in a file changed, as git log -S).

• search_discord_topicsFree

  Find PostgreSQL Discord discussions semantically related to a query. Returns only the channel, approximate date range, and participants of relevant conversations — never message content or links (per the Discord community agreement).

• search_docsFree

  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 versions is one result listing each version and its URL. Returns title, path, url, the versions it matched and a snippet. Read a page with get_doc_page; cite its postgresql.org/docs url.

• search_patchesFree

  Find patch series by parsing [PATCH v2 3/7]-style subject prefixes. Returns structured patch metadata including version, sequence, total, and series grouping.

• search_symbolsFree

  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, language, file, start_line and end_line. Like `ctags`/`git grep -w` for definitions. Follow with get_callers, or git_show_file with start_line/end_line to read the body.

• search_wikiFree

  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, timestamp, is_current) and how many matched; since/until bound the revision dates. Read a page with get_wiki_page; cite its wiki url.

• semantic_searchFree

  Search messages on every list (or the lists in inbox) by semantic similarity using vector embeddings; each result names its inbox. Returns messages most similar in meaning to the query text. Requires embeddings to be generated first (see embedding_status). Each result carries an 'excerpt': the author's own words, quoted text and signatures removed.

• semantic_search_codeFree

  Search code symbols by semantic similarity using vector embeddings. Requires embeddings.

• symbols_in_fileFree

  List all code symbols defined in a file, ordered by line number.

• upcoming_eventsFree

  PostgreSQL community events in a date window: conferences, PGDays, meetups, online events, Call for Papers and registration deadlines, conference talks (with speakers and their pg.ddx.io person hash), Talking Postgres episodes, release dates and commitfests. Same data as the iCalendar feeds at https://pg.ddx.io/calendars (community event listings from the PostgreSQL Event Calendar, curated by Andreas Scherbaum).

• whats_newFree

  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:<name>, new:<window>, a phrase ('the core team'), or a list. since/until: ISO date, today, 2w/14d/1m, pg19 (a release's development window), all; default 14 days. during: a calendar event uid/url. topic narrows by hybrid search. Kinds: waiting (one person, no topic: what is on their radar, each with group, priority 0-100 and why), mail_from, mail_to_cc, mail_mention, git_author, git_credit, git_mention, wiki_edit, wiki_mention, commitfest, calendar, roster. Names, page hashes and urls only, never addresses. ~4 s budget; late kinds go in timed_out with partial=true. Cite each item's url. Same as GET /api/v2/activity.

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 1823ms20/20
• Tool poisoning125 tool descriptions checked15/15
• Auth qualityopen endpoint exposes 5 write-action tools with no auth3/15
• Maintenanceno repository listed3/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

65/100

higher than 15% of 1,299 Productivity servers

Tools

125

the typical Productivity server has 7

Tools that change things

4%

typical: 0%. Fewer write tools means less an agent can break

Uptime

96%

of our recent checks; the typical remote Productivity server answers 100%

Response time

124 ms

faster than 82% of 655 Productivity servers

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

Is pg.ddx.io: the PostgreSQL community's memory MCP server safe?

With care: it is graded C, so read the findings first (65/100). Read the pg.ddx.io: the PostgreSQL community's memory safety report

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

It runs remotely at pg.ddx.io. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

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

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

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

The latest release is v2026.10.22.

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

96% of our last 28 checks got an answer. We check remote servers about four times a day.

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

Servers from other publishers that do the same job: loci MCP server, Workfile MCP server and Context7 MCP server.

How does pg.ddx.io: the PostgreSQL community's memory compare with other Productivity MCP servers?

safety score 65/100 (higher than 15% of 1,299 Productivity servers); tools 125 (the typical Productivity server has 7); tools that change things 4% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.