Ext Ops Panel
Open dashboard
Comparison

craft-statusline vs Git

craft-statusline is a plugin bundle for AI coding tools published by derjochenmeyer. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Git is an MCP server published by Abhishekkumar2021. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
Marketplacecraft-statuslineGit
Claude Code: claude-plugins-community Listed
Version: 3.0.0
Forks (GitHub): 1
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.0
Downloads/month (npm): 188
Downloads/week (npm): 25
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

craft-statusline vs Git
Factcraft-statuslineGit
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)2 (better)1 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@abhishekmcp/git)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 0
Parts of the bundle (differs)51
LicenceMITMIT
Repository (differs)github.com/derjochenmeyer/claude-code-craft-statuslinegithub.com/abhishekkumar2021/mcp-suite
Changes in the last 7 days (differs)02
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

craft-statusline

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

A Claude Code statusline written in bash. Shows model and effort level, a state-aware git branch badge, context window with absolute-token traffic light (yellow at 400k tokens, red at 85%), rolling 5h and 7d rate limits, and optional session cost. Zero Node, zero Python, zero Nerd Fonts. Only requires jq. Bash 3.2 compatible, runs on macOS, Linux, and WSL.

Git

In its own words, on Official MCP Registry:

Local Git via MCP: status, log, diff, file history, branches, and gated stage/commit. Pure-JS.

How to run each

craft-statusline As a Claude Code plugin

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

Git As a local MCP server: npm package

Claude Code
claude mcp add --env "GIT_ROOTS=<YOUR_GIT_ROOTS>" --transport stdio git -- npx -y @abhishekmcp/git

Requires: GIT_ROOTS

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

The marketplaces of craft-statusline publish no settings it asks for, so we do not compare settings.

What it can do: craft-statusline · What it can do: Git · 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. Data comes from public marketplace files in GitHub repositories of their authors. 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