Ext Ops Panel
Open dashboard
Comparison

sync-docs vs ctxlint

sync-docs is a plugin bundle for AI coding tools published by agent-sh. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). ctxlint is an MCP server published by YawLabs. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacesync-docsctxlint
Claude Code: claude-plugins-community Listed
Version: 5.1.0
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.28.0
Downloads/month (npm): 51 602
Downloads/week (npm): 12 417
Forks (GitHub): 3
Stars (GitHub): 11
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

sync-docs vs ctxlint
Factsync-docsctxlint
Marketplaces that list it11
Stars (GitHub) (differs)3 (worse)11 (better)
Forks (GitHub) (differs)0 (worse)3 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@yawlabs/ctxlint)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)3Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/agent-sh/sync-docsgithub.com/yawlabs/ctxlint
Changes in the last 7 days00
First seen (differs)2026-10-122026-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

sync-docs

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

Detect outdated documentation by comparing docs against actual code state — broken references, version mismatches, stale code examples, and missing CHANGELOG entries. Documentation drifts from code silently: a function gets renamed, an import path changes, a version bumps, but the README and CHANGELOG still reference the old state. `/sync-docs` compares documentation files against the current codebase, finds the gaps, and auto-applies safe fixes (version updates, CHANGELOG entries) while flagging ambiguous cases (removed exports referenced in docs, code examples needing context) for manual review. Plug into /next-task and /prepare-delivery as the pre-ship docs gate.

ctxlint

In its own words, on Official MCP Registry:

Lint AI agent context files (CLAUDE.md, AGENTS.md, etc.) against your actual codebase

How to run each

sync-docs As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install sync-docs@claude-community

ctxlint As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ctxlint -- npx -y @yawlabs/ctxlint

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

Neither one's marketplaces publish the settings it asks for.

What it can do: sync-docs · What it can do: ctxlint · 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