Ext Ops Panel
Open dashboard
Comparison

io.github.0Mattias/bettermemory vs temporal-mcp

io.github.0Mattias/bettermemory is an MCP server published by 0Mattias. Marketplaces we read that list it: 1 (Official MCP Registry). temporal-mcp is an MCP server published by MirrorEthic. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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

Where each is published
Marketplaceio.github.0Mattias/bettermemorytemporal-mcp
Official MCP Registry Listed
Version: 8.0.0
Downloads/month (PyPI): 4 973
Downloads/week (PyPI): 650
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.0
Downloads/month (PyPI): 84
Downloads/week (PyPI): 12
Forks (GitHub): 0
Stars (GitHub): 3
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

io.github.0Mattias/bettermemory vs temporal-mcp
Factio.github.0Mattias/bettermemorytemporal-mcp
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (bettermemory)Remote server (temporal-mcp.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/0mattias/bettermemorygithub.com/mirrorethic/temporal-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 47 h ago returned HTTP 405

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

io.github.0Mattias/bettermemory

In its own words, on Official MCP Registry:

Memory for coding agents, checked against the filesystem and git before it is believed.

temporal-mcp

In its own words, on Official MCP Registry:

Wall-clock awareness for LLM agents. Two tools: elapsed-time-between-turns + day rollover detection.

How to run each

io.github.0Mattias/bettermemory As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio bettermemory -- uvx bettermemory

temporal-mcp As a remote MCP server

Claude Code
claude mcp add --transport http temporal-mcp https://temporal-mcp.dev/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 temporal-mcp 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: io.github.0Mattias/bettermemory · What it can do: temporal-mcp · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built