thread-keeper vs io.github.pro-target/ai-r
thread-keeper is an MCP server published by po4erk91. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.pro-target/ai-r is an MCP server published by pro-target. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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 |  thread-keeper |  io.github.pro-target/ai-r |
|---|---|---|
| Official MCP Registry | Listed Version: 0.13.1 Downloads/month (PyPI): 1 654 Downloads/week (PyPI): 45 Forks (GitHub): 4 Stars (GitHub): 13 Not marked · First seen |
Listed Version: 0.4.2 Downloads/month (PyPI): 89 Downloads/week (PyPI): 22 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
| Fact | thread-keeper | io.github.pro-target/ai-r |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 13 (better) | 3 (worse) |
| Forks (GitHub) (differs) | 4 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (threadkeeper) | On your machine (agent-session-reader) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/po4erk91/thread-keeper | github.com/pro-target/ai-r |
| 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
thread-keeper
Multi-agent shared brain across Claude, Codex, Antigravity, Gemini, Copilot, and VS Code.
io.github.pro-target/ai-r
Read local AI agent sessions (Claude Code, Codex, OpenCode, Antigravity, Pi): intents, plans, tools
How to run each
thread-keeper As a local MCP server: PyPI package
claude mcp add --transport stdio thread-keeper -- uvx threadkeeperio.github.pro-target/ai-r As a local MCP server: PyPI package
claude mcp add --transport stdio ai-r -- uvx --from agent-session-reader ai-r-mcp agent-session-readerCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: thread-keeper · What it can do: io.github.pro-target/ai-r · 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.