Ext Ops Panel
Open dashboard
Comparison

codebase-documentor-for-aws vs io.github.jmshinhwa/data-act-switching-lint

codebase-documentor-for-aws is a plugin bundle for AI coding tools published by Amazon Web Services. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.jmshinhwa/data-act-switching-lint is an MCP server published by jmshinhwa. 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
Marketplacecodebase-documentor-for-awsio.github.jmshinhwa/data-act-switching-lint
Community marketplace awslabs/agent-plugins Listed
Version: 1.0.0
Forks (GitHub): 164
Stars (GitHub): 921
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Downloads/month (npm): 1 208
Downloads/week (npm): 52
Forks (GitHub): 1
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

codebase-documentor-for-aws vs io.github.jmshinhwa/data-act-switching-lint
Factcodebase-documentor-for-awsio.github.jmshinhwa/data-act-switching-lint
Marketplaces that list it11
Stars (GitHub) (differs)921 (better)1 (worse)
Forks (GitHub) (differs)164 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (knowledge-mcp.global.api.aws)On your machine (@readystack/data-act-switching-lint)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)3Not a bundle
Licence (differs)Apache-2.0Not stated
Repository (differs)github.com/awslabs/agent-pluginsgithub.com/jmshinhwa/readystack-themes
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Answered with HTTP 302 (4 days ago)no 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

codebase-documentor-for-aws

In its own words, on Community GitHub marketplaces:

Analyze codebases to generate structured technical documentation with source-of-truth citations. Optimized for AWS workloads using CDK, CloudFormation, and Terraform.

io.github.jmshinhwa/data-act-switching-lint

In its own words, on Official MCP Registry:

Reads your cloud contract text and names every clause Chapter VI no longer allows, with the article

How to run each

codebase-documentor-for-aws As a Claude Code plugin

Claude Code
/plugin marketplace add awslabs/agent-plugins
/plugin install codebase-documentor-for-aws@agent-plugins-for-aws

io.github.jmshinhwa/data-act-switching-lint As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio data-act-switching-lint -- npx -y @readystack/data-act-switching-lint --mcp

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

Only codebase-documentor-for-aws 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: codebase-documentor-for-aws · What it can do: io.github.jmshinhwa/data-act-switching-lint · 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