Ext Ops Panel
Open dashboard
Comparison

commit-craft vs ProjectPulse MCP

commit-craft is a plugin bundle for AI coding tools published by Alireza Rezvani. Marketplaces we read that list it: 1 (Community GitHub marketplaces). ProjectPulse MCP is an MCP server published by alexbypa. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-12. 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
Marketplacecommit-craftProjectPulse MCP
Community marketplace alirezarezvani/claude-skills Listed
Version: 2.14.6
Forks (GitHub): 4 120
Stars (GitHub): 29 704
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.10.0
Downloads/month (npm): 650
Downloads/week (npm): 169
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.10.0
Downloads/month (npm): 650
Downloads/week (npm): 169
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

commit-craft vs ProjectPulse MCP
Factcommit-craftProjectPulse MCP
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)29 704 (better)1 (worse)
Forks (GitHub) (differs)4 120 (better)0 (worse)
Last release (differs)2026-11-03 (better)2026-10-18 (worse)
Where it runs (differs)Installs as a plugin bundleOn your machine (projectpulse-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)4Not a bundle
LicenceMITMIT
Repository (differs)github.com/alirezarezvani/claude-skillsgithub.com/alexbypa/github-projectpulse-mcp
Changes in the last 7 days00
First seen (differs)2026-10-312026-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

commit-craft

In its own words, on Community GitHub marketplaces:

Turn a tangled working tree into a clean, reviewable commit series. Three deterministic stdlib scripts over git: a series planner that groups changes into commits in build-safe order (manifest with lockfile, pure moves, formatting, each module's change with its tests, docs, CI), holds back .env and key files, and flags mixed formatting and moves whose callers would break; a secret gate that scans staged or pushed lines for provider tokens, high-entropy secrets, sensitive files and conflict markers and blocks before the commit exists, with redacted output and reasoned waivers; and a message linter that blocks vague subjects, missing why on large changes and pending fixup commits, matching the repo's own convention. Ships pre-commit, commit-msg and pre-push hooks, cs-commit-craft agent, /cs-commit-craft and /cs-commit-check commands and 3 cited references.

ProjectPulse MCP

In its own words, on Official MCP Registry:

Monitor GitHub repo health, DORA metrics and CI signals from your AI assistant.

How to run each

commit-craft As a Claude Code plugin

Claude Code
/plugin marketplace add alirezarezvani/claude-skills
/plugin install commit-craft@claude-code-skills

ProjectPulse MCP As a local MCP server: npm package

Claude Code
claude mcp add --env "GITHUB_TOKEN=<YOUR_GITHUB_TOKEN>" --transport stdio github-projectpulse-mcp -- npx -y projectpulse-mcp

Requires: GITHUB_TOKEN (secret)

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 commit-craft publish no settings it asks for, so we do not compare settings.

What it can do: commit-craft · What it can do: ProjectPulse 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. Package data comes from the public npm registry (registry.npmjs.org). 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