Ext Ops Panel
Open dashboard
Comparison

AI Agents API Library vs J-Dawgs AI Tool Store & Human Hands — Catalog MCP

AI Agents API Library is a plugin bundle for AI coding tools published by Marek Papis. Marketplaces we read that list it: 1 (Community GitHub marketplaces). J-Dawgs AI Tool Store & Human Hands — Catalog MCP is an MCP server published by joshuajdawg0350. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
MarketplaceAI Agents API LibraryJ-Dawgs AI Tool Store & Human Hands — Catalog MCP
Community marketplace eater2/ai_agents_api_library Listed
Version: 0.3.12
Forks (GitHub): 11
Stars (GitHub): 33
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.1
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

AI Agents API Library vs J-Dawgs AI Tool Store & Human Hands — Catalog MCP
FactAI Agents API LibraryJ-Dawgs AI Tool Store & Human Hands — Catalog MCP
Marketplaces that list it11
Stars (GitHub) (differs)33 (better)0 (worse)
Forks (GitHub) (differs)11 (better)0 (worse)
Last release (differs)2026-11-04Not published
Where it runs (differs)Remote server (ai-agents-api-library.vercel.app/mcp)On your machine (jdawgs-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/eater2/ai_agents_api_librarygithub.com/joshuajdawg0350/jdawgs-mcp
Changes in the last 7 days (differs)12
First seen (differs)2026-10-132026-11-04
Endpoint at the last check (differs)Status out of date: last check 2 days ago returned HTTP 405no 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

AI Agents API Library

In its own words, on Community GitHub marketplaces:

Find third-party APIs and MCP servers for any capability an agent lacks, with auth method, free tier, MCP endpoint and docs.

J-Dawgs AI Tool Store & Human Hands — Catalog MCP

In its own words, on Official MCP Registry:

Read-only catalog of the J-Dawgs AI Tool Store (100+ agent tools) plus Human Hands for AIs.

How to run each

AI Agents API Library As a Claude Code plugin

Claude Code
/plugin marketplace add eater2/ai_agents_api_library
/plugin install ai-agents-api-library@eater2

J-Dawgs AI Tool Store & Human Hands — Catalog MCP As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio j-dawgs-mcp -- uvx jdawgs-mcp

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

Only AI Agents API Library has a remote endpoint we check. How we check endpoints

Tools each declares

Neither the marketplaces of J-Dawgs AI Tool Store & Human Hands — Catalog MCP nor its endpoint list any tools, so we do not compare tools.

Settings each asks for

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

What it can do: AI Agents API Library · What it can do: J-Dawgs AI Tool Store & Human Hands — Catalog MCP · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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