Ext Ops Panel
Open dashboard
Comparison

Customer Support vs AIMarket — live agent marketplace

Customer Support is a plugin bundle for AI coding tools published by Anthropic. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). AIMarket — live agent marketplace is an MCP server published by alexar76. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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
MarketplaceCustomer SupportAIMarket — live agent marketplace
Claude: knowledge-work-plugins Listed
Version: 1.3.0
Forks (GitHub): 3 378
Stars (GitHub): 29 875
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 3.15.21
Forks (GitHub): 0
Stars (GitHub): 1
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

Customer Support vs AIMarket — live agent marketplace
FactCustomer SupportAIMarket — live agent marketplace
Marketplaces that list it11
Stars (GitHub) (differs)29 875 (better)1 (worse)
Forks (GitHub) (differs)3 378 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (modelmarket.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)13Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/anthropics/knowledge-work-pluginsgithub.com/alexar76/aimarket-hub
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 25 h ago

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

Customer Support

In its own words, on Claude: knowledge-work-plugins:

Triage tickets, draft responses, escalate issues, and build your knowledge base. Research customer context and turn resolved issues into self-service content.

AIMarket — live agent marketplace

In its own words, on Official MCP Registry:

Search and invoke real AI capabilities on modelmarket.dev. Free trial, then a prepaid key.

How to run each

Customer Support As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install customer-support@knowledge-work-plugins

AIMarket — live agent marketplace As a remote MCP server

Claude Code
claude mcp add --transport http aimarket-hub https://modelmarket.dev/mcp --header "X-API-Key: <YOUR_X_API_KEY>"

Requires: X-API-Key header

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

Only AIMarket — live agent marketplace 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: Customer Support · What it can do: AIMarket — live agent marketplace · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/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