Ext Ops Panel
Open dashboard
Comparison

local-ci vs Kody

local-ci is a plugin bundle for AI coding tools published by MrPuls. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Kody is an MCP server published by kody-hq. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
Marketplacelocal-ciKody
Claude Code: claude-plugins-community Listed
Version: 0.0.24
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.6
Forks (GitHub): 79
Stars (GitHub): 812
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

local-ci vs Kody
Factlocal-ciKody
Marketplaces that list it11
Stars (GitHub) (differs)3 (worse)812 (better)
Forks (GitHub) (differs)0 (worse)79 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (kody.codes/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/mrpuls/local-cigithub.com/kody-hq/kody
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-17
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago, requires a key

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

local-ci

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

Autonomously run CI/CD pipelines on your behalf. This gives Claude Code the ability to validate code in real target environments — different runtimes, OS images, or with real services like databases

Kody

In its own words, on Official MCP Registry:

Your agents' cloud for individuals and teams. Search, execute, packages, jobs, and credentials.

How to run each

local-ci As a Claude Code plugin

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

Kody As a remote MCP server

Claude Code
claude mcp add --transport http kody https://kody.codes/mcp

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

Only Kody 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: local-ci · What it can do: Kody · 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