Ext Ops Panel
Open dashboard
Comparison

com.deerdawn/deerdawn vs Afterpaths

com.deerdawn/deerdawn is an MCP server published by deerdawn.com. Marketplaces we read that list it: 1 (Official MCP Registry). Afterpaths is an MCP server published by burnssa. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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
Marketplacecom.deerdawn/deerdawnAfterpaths
Official MCP Registry Listed
Version: 1.0.53
Downloads/month (npm): 1 586
Downloads/week (npm): 170
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.2.5
Downloads/month (PyPI): 188
Downloads/week (PyPI): 28
Forks (GitHub): 0
Stars (GitHub): 2
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

com.deerdawn/deerdawn vs Afterpaths
Factcom.deerdawn/deerdawnAfterpaths
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.deerdawn.com/mcp)On your machine (afterpaths)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 02, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)github.com/hissingspider/deerdawn-mcpgithub.com/burnssa/afterpaths
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days ago, requires a keyno remote endpoint we check

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

com.deerdawn/deerdawn

In its own words, on Official MCP Registry:

AI session memory: the brief your AI reads before every session so no session starts cold.

Afterpaths

In its own words, on Official MCP Registry:

Session memory for AI coding agents. Search past sessions, extract rules, and track what works.

How to run each

com.deerdawn/deerdawn As a remote MCP server

Claude Code
claude mcp add --transport http deerdawn https://api.deerdawn.com/mcp

Afterpaths As a local MCP server: PyPI package

Claude Code
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio afterpaths -- uvx --from "afterpaths[mcp]" afterpaths afterpaths-mcp

Requires: ANTHROPIC_API_KEY (secret), OPENAI_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only com.deerdawn/deerdawn 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

Only com.deerdawn/deerdawn asks for

  • DEERDAWN_API_URL

Only Afterpaths asks for

  • ANTHROPIC_API_KEY (secret)
  • OPENAI_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: com.deerdawn/deerdawn · What it can do: Afterpaths · Compare two other plugins

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.

Where the data comes from: how the catalog is built