MCP server

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

io.ddx.pg/archive

Checked 26 Oct 2026, 08:29 UTC · Not tested (older connection type)

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

Website

At a glance

Type

MCP server

Publisher

ddx.io (verified by the MCP Registry)

Status

Not checked

Tools

125

Last checked

26 Oct 2026, 08:29 UTC

Tools

• animal_history ~141 tokens
  Run timeline for one animal. Filterable by branch and start cutoff; ordered newest first.
• animal_owner_contributions ~107 tokens
  Animals run by one owner: list, branches each tracks, last status, first_seen_at and elapsed days since first observation.
• blame ~417 tokens
  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 comm
• blame_symbol ~123 tokens
  Show the commit history that modified a symbol's file, filtered to the symbol's line range.
• browse_by_date Browses the web · ~180 tokens
  Browse threads within a specific date range. Useful for exploring what was discussed during a particular time period.
• build_status_freshness ~62 tokens
  Most recent :entry/last-build-at observation across all entries. Use to detect a stalled cfbot scraper.
• buildfarm_overview ~71 tokens
  High-level buildfarm health: animal count, recent run counts, currently-failing animals, top owners, OS / branch breakdown, and freshness.
• calendar_feeds ~81 tokens
  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_status ~89 tokens
  Check whether a pull request has been merged upstream. Returns the latest patch series head commit and any merge information.
• code_index_status ~102 tokens
  Get code indexing statistics: files indexed, symbol counts by kind and language, edge count, community count.
• code_search ~698 tokens
  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/CamelCa
• codebase_map ~122 tokens
  Get a directory-level overview of the codebase showing file counts and symbol counts per directory.
• combine_calendars ~218 tokens
  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
• commit_buildfarm_status ~176 tokens
  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 po
• commit_history ~323 tokens
  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, sh
• commitfest_stats ~70 tokens
  Overview of all indexed commitfests: count by status, top contributors (entries authored), distinct people / commitfests / entries totals.
• contribution_summary ~122 tokens
  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_reference ~506 tokens
  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 and to the subjects of the postgres commits that introduce
• detect_changes ~193 tokens
  Detect which symbols changed between two commits by comparing file content hashes.
• discussion_links ~159 tokens
  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_status ~111 tokens
  Get embedding coverage statistics: how many messages have embeddings, which model was used, and when embeddings were last generated.
• entry_branches ~100 tokens
  Repository branches tracked for a commitfest entry. Joins commitfest.entry_repos with ag_repositories so callers see repo name + branch_name + is_authoritative.
• entry_history ~126 tokens
  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_breaks ~179 tokens
  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_contributions ~182 tokens
  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_code ~117 tokens
  Find functions/methods with zero incoming call graph edges (potentially unused code).
• find_entries_for_author ~134 tokens
  Find commitfest entries where the given person is an author. Looks up by email (exact) or by name (substring, case-sensitive).
• find_entries_for_thread ~122 tokens
  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_on ~178 tokens
  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 di
• find_failing_patches ~239 tokens
  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://
• find_failing_runs ~145 tokens
  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_pending ~132 tokens
  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_status ~151 tokens
  Patches that pass on some platforms but not others. Example: passing on linux but failing on macos -> portability bug.
• find_pattern ~140 tokens
  Search for a regex pattern in code symbol bodies. Uses trigram indexes for acceleration.
• find_rebase_needed_patches ~90 tokens
  Entries cfbot reports as no longer applying to master tip (:entry/applies-cleanly is false). These need an author rebase.
• find_related_discussions ~226 tokens
  Find mailing list messages related to a commit, topic, or PR. A postgres commit SHA (7-40 hex) returns the mail that refers to that commit (match_mode commit): its Discussion: threads first, then the committers announcement, then messages citing the hash, each with how_it_refers. Anything else searc
• find_similar_messages ~169 tokens
  Find messages similar to a given message using its embedding vector. Useful for finding related discussions or duplicate threads.
• find_string_literals ~188 tokens
  Find occurrences of a literal in current (HEAD) source, restricted to a syntactic kind: "strings" (inside double quotes), "comments" (after // or /*), or "all".
• get_animal ~93 tokens
  Profile of one buildfarm animal: hardware/OS/compiler/owner, branches tracked, last build status, plus the last 20 runs (any branch).
• get_attachment ~271 tokens
  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=
• get_author_messages ~232 tokens
  Find messages by a specific author, optionally filtered by date range. Uses the f: (from) search prefix.
• get_callees ~141 tokens
  Find all symbols that the given symbol calls/references (forward call graph).
• get_callers ~207 tokens
  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 i
• get_commit ~338 tokens
  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=fal
• get_commitfest ~87 tokens
  Get a single commitfest with entries grouped by status and the top contributors (authors with the most entries).
• get_communities ~126 tokens
  List Louvain community clusters detected in the call graph. Communities group related symbols by functional area.
• get_community ~108 tokens
  Get details and member symbols for a specific community.
• get_contributor ~216 tokens
  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 (commit_sha = the git SHA, roles = every role they had in it), and buildfarm animals they own.
• get_contributor_history ~110 tokens
  Show all past mailing list submissions by a contributor (matched by email address or name).
• get_dependents ~166 tokens
  Get transitive dependents: all symbols in the blast radius if this symbol changes.
• get_doc_page ~160 tokens
  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_entry ~139 tokens
  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_flows ~140 tokens
  Trace execution flow paths through the call graph from entry points.
• get_impact ~128 tokens
  Analyze the impact of modifying a symbol: risk level, blast radius, affected communities and execution flows.
• get_inbox_info ~93 tokens
  Get metadata for an inbox (name, addresses, message count, last activity)
• get_inbox_stats ~165 tokens
  Return aggregate statistics about an inbox: message counts by time period, top authors, and activity trends.
• get_inbox_summary ~96 tokens
  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_message ~339 tokens
  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_a
• get_message_headers ~166 tokens
  Get email headers as structured key/value pairs. Returns all headers or a specific header by name.
• get_message_references ~150 tokens
  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_messages ~210 tokens
  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_branches ~90 tokens
  Get the git branches created from a patch series. Shows what branches were applied from email patches for code intelligence analysis.
• get_patch_build_history ~89 tokens
  Build matrix for one entry: per-platform/config status, log URL, observation time, applies-cleanly flag, rollup.
• get_patch_series ~84 tokens
  Get patch submission history for a forge pull request URL. Returns all iterations submitted to the mailing list.
• get_raw_message ~143 tokens
  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_stats ~114 tokens
  Get commit frequency analysis and sync statistics for a repository. Returns median commit interval, recommended poll frequency, and recent fetch log.
• get_repository_summary ~94 tokens
  Per-repository summary: total commits, top 10 contributors, branches, language breakdown (from indexed symbols), and a sampled most-touched-paths list.
• get_signature ~115 tokens
  Get the function/method signature and doc comment for a symbol.
• get_source_info ~92 tokens
  Detail for a single source by name. Returns kind, item_count, last_update, next_sync, freshness_status, and description.
• get_symbol ~145 tokens
  Get full details for a code symbol by its qualified name, including source code, signature, documentation, and file location.
• get_tests_for ~112 tokens
  Find test symbols that reference the given symbol.
• get_thread ~442 tokens
  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, filenam
• get_thread_references ~152 tokens
  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_history ~86 tokens
  Get revision history for a wiki page.
• get_wiki_page ~124 tokens
  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_activity ~136 tokens
  Show commit activity over time, bucketed by period. Useful for understanding development pace and trends.
• git_analyze_authors ~126 tokens
  Get commit statistics per author: total commits, first and last commit dates. Ranked by commit count.
• git_analyze_bus_factor ~132 tokens
  Identify files with the fewest distinct authors (bus factor risk). Files modified by only one person are knowledge silos.
• git_analyze_churn ~130 tokens
  Identify the most frequently modified files in the repository. High-churn files may indicate hotspots or unstable code.
• git_analyze_coupling ~158 tokens
  Find files that are frequently changed together. Logical coupling can reveal hidden dependencies between components.
• git_analyze_hotspots ~149 tokens
  Aggregate file churn by directory to find the most actively changed areas of the codebase.
• git_blame ~274 tokens
  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, ma
• git_diff ~492 tokens
  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 specifi
• git_log ~390 tokens
  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, messag
• git_search ~298 tokens
  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 t
• git_show_file ~432 tokens
  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: star
• grep_repository ~300 tokens
  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
• history-of ~245 tokens
  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 his
• hybrid_search ~688 tokens
  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_
• hybrid_search_code ~185 tokens
  Combined keyword + semantic code search using Reciprocal Rank Fusion. Requires embeddings to be generated.
• list_animals ~236 tokens
  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_branches ~95 tokens
  List tracked branches for a repository, including head commit and default branch status.
• list_commitfests ~107 tokens
  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_contributors ~255 tokens
  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_channels ~47 tokens
  List monitored Discord channels with message counts.
• list_doc_versions ~47 tokens
  List available documentation versions with page counts.
• list_entries ~220 tokens
  List commitfest entries (proposed patch series). Filterable by status, commitfest number, or topic; paginated.
• list_files ~292 tokens
  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_inboxes ~170 tokens
  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_projects ~54 tokens
  List bridge-configured projects linking a forge repository to a mailing list inbox.
• list_recent ~107 tokens
  List recent messages from an inbox
• list_repositories ~209 tokens
  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_sources ~240 tokens
  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
• list_threads ~172 tokens
  Browse recent threads (topic-level view). Returns thread summaries with message counts, date ranges, and latest message metadata.
• read_file ~297 tokens
  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_activity ~129 tokens
  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_code ~351 tokens
  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
• release_contributors ~153 tokens
  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_stats ~101 tokens
  Get detailed statistics for a git repository including commit count, file count, branch, and import state.
• retrieve_context ~555 tokens
  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
• search ~696 tokens
  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
• search-regex ~275 tokens
  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_sources ~228 tokens
  Unified search across all document sources (docs, wiki, and email). Returns results ranked by relevance. Search operators (site:, after:, before:, from:, link:, /regex/ ...) are applied per source; operators and warnings say what the query used, and skipped names each source the query left out and w
• search_commitfest ~308 tokens
  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 upda
• search_commits ~458 tokens
  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
• search_discord_topics ~158 tokens
  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_docs ~419 tokens
  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. Ret
• search_patches ~167 tokens
  Find patch series by parsing [PATCH v2 3/7]-style subject prefixes. Returns structured patch metadata including version, sequence, total, and series grouping.
• search_symbols ~310 tokens
  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 gre
• search_wiki ~314 tokens
  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 th
• semantic_search ~259 tokens
  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 autho
• semantic_search_code ~140 tokens
  Search code symbols by semantic similarity using vector embeddings. Requires embeddings.
• symbols_in_file ~112 tokens
  List all code symbols defined in a file, ordered by line number.
• upcoming_events ~442 tokens
  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
• whats_new ~564 tokens
  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. s

Browse

• Web scraping
• Website monitoring
• Team chat
• Calendars

Related MCP servers

• Socialloop
  SocialLoop: AI-native event platform — sell tickets, manage guests, run affiliates & promo codes.
• ctxstore — memory that follows you across models
  Persistent memory for AI agents: keyed facts, a wake bundle each session, one memory in every model.
• Canton Ccpedia
  Canton Network: CIPs and their on-chain vote outcomes, docs, forum, validator upgrade deadlines.
• ecomdly
  E-commerce skills for AI agents: feeds, Google Shopping, GA4. Your private Brain when signed in.
• emdly
  Search, install and submit Markdown skills for AI agents; private Brain files when signed in.
• Gnosem
  Cross-vendor AI memory over MCP. One semantic store, readable and writeable from every MCP client.
• oriiion
  Your marketing, a message away
• Colour Memory
  Colour meaning, history and evidence for AI: 45,000+ source-graded colour records and 91 tools.

Badge for your README

[![AptLynx](https://aptlynx.net/badge/io.ddx.pg/archive.svg)](https://aptlynx.net/servers/io.ddx.pg/archive)

Listing text is written by the maker; AptLynx lists tools and does not vouch for them. Find another tool · Browse by topic · For agents