Temporal vs io.github.STiFLeR7/memex
Temporal is a plugin bundle for AI coding tools published by Temporal. Marketplaces we read that list it: 1 (Codex: openai-curated (openai/plugins)). io.github.STiFLeR7/memex is an MCP server published by STiFLeR7. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-12. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Codex: openai-curated (openai/plugins) | Listed Version: 0.4.0 Forks (GitHub): 961 Stars (GitHub): 7 396 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.2 Forks (GitHub): 0 Stars (GitHub): 12 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.3.2 Forks (GitHub): 0 Stars (GitHub): 0 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 | Temporal | io.github.STiFLeR7/memex |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 7 396 (better) | 12 (worse) |
| Forks (GitHub) (differs) | 961 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (stifler-memex-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 4, secrets among them: 2 |
| Parts of the bundle (differs) | 4 | 1 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/openai/plugins | github.com/stifler7/memex |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Temporal
Comprehensive skill for the entire Temporal lifecycle — developing applications, using the Temporal CLI, running and managing Temporal Server, and working with Temporal Cloud.
io.github.STiFLeR7/memex
Temporal engineering context for agents via MCP.
How to run each
Temporal
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
io.github.STiFLeR7/memex As a local MCP server: npm package
claude mcp add --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "NEO4J_PASSWORD=<YOUR_NEO4J_PASSWORD>" --env "NEO4J_URI=<YOUR_NEO4J_URI>" --env "NEO4J_USER=<YOUR_NEO4J_USER>" --transport stdio memex -- npx -y stifler-memex-mcpRequires: GEMINI_API_KEY (secret), NEO4J_PASSWORD (secret), NEO4J_URI, NEO4J_USER
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Temporal publish no settings it asks for, so we do not compare settings.
What it can do: Temporal · What it can do: io.github.STiFLeR7/memex · Compare two other plugins
Data comes from the public marketplace file https://github.com/openai/plugins/blob/HEAD/.agents/plugins/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.