log-aggregator vs Foam Observability
log-aggregator is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑18.
log-aggregator is a plugin bundle for AI coding tools published by barnburner121. No marketplace we read lists it any more. Foam Observability is an MCP server published by foam-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-13. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace barnburner121/claude-plugin-marketplace | Removed on 2026-10-18 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.0 No figure published Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | log-aggregatorno longer listed · | Foam Observability |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 3 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@barnburner121/plugin-hub-mcp) | Remote server (sdk.api.foam.ai/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 2 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/barnburner121/claude-plugin-marketplace | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | No HTTP response at the last check (10 h ago) |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of log-aggregator
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Connect your coding agent to the hosted LogPacer MCP server, with skills for setting up collection, instrumenting apps and investigating logs.
-
Query Sumo Logic logs, alerts, dashboards, and SIEM insights directly from Copilot.
-
Set up and use Gonzo, the open-source terminal log analysis tool. Detects deployment platforms (Vercel, Supabase, K8s, Docker, AWS, Cloudflare, Fly, Render, Railway, Netlify…
-
Use Datadog directly in Copilot / VS Code through a preconfigured Datadog MCP server. Query logs, metrics, traces, dashboards, and more through natural conversation.
-
Ingest and search LogsLoom logs from coding agents.
-
Use Datadog directly in Claude Code through a preconfigured Datadog MCP server. Query logs, metrics, traces, dashboards, and more through natural conversation. This plugin is in…
What each says it does
log-aggregator
Generate log aggregation configs (ELK, Loki)
Foam Observability
Query application logs, traces, and metrics from your AI coding assistant via Foam's MCP server.
How to run each
log-aggregator
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Foam Observability As a remote MCP server
claude mcp add --transport http observability https://sdk.api.foam.ai/mcp --header "Authorization: Bearer <YOUR_TOKEN>"
Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Foam Observability has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: log-aggregator · What it can do: Foam Observability · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.