Ext Ops Panel
Open dashboard
Comparison

claude-library vs io.github.pro-target/ai-r

claude-library is a plugin bundle for AI coding tools published by tabers77. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-21. 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
Marketplaceclaude-libraryio.github.pro-target/ai-r
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed 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

claude-library vs io.github.pro-target/ai-r
Factclaude-libraryio.github.pro-target/ai-r
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)3 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (agent-session-reader)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)6Not published
Parts of the bundle (differs)35Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/tabers77/claude_experimentsgithub.com/pro-target/ai-r
Changes in the last 7 days00
First seen2026-10-112026-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

claude-library

In its own words, on Claude Code: claude-plugins-community:

23 reusable skills, 2 agents, and smart hooks for any project. Covers the full development cycle: architecture mapping, implementation planning, code review, safe refactoring, security-aware editing, quality audits, and 5 interactive learning modules with persistent memory. Hooks auto-lint Python files, block destructive git commands, protect sensitive files, and auto-suggest relevant skills based on your prompt.

io.github.pro-target/ai-r

In its own words, on Official MCP Registry:

Read local AI agent sessions (Claude Code, Codex, OpenCode, Antigravity, Pi): intents, plans, tools

How to run each

claude-library As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install claude-library@claude-community

io.github.pro-target/ai-r As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio ai-r -- uvx --from agent-session-reader ai-r-mcp agent-session-reader

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

Neither one's marketplaces publish the settings it asks for.

What it can do: claude-library · What it can do: io.github.pro-target/ai-r · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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