Ext Ops Panel
Open dashboard
Comparison

ai-sync vs io.github.Intina47/context-sync

ai-sync is a plugin bundle for AI coding tools published by oreolion. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.Intina47/context-sync is an MCP server published by Intina47. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-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
Marketplaceai-syncio.github.Intina47/context-sync
Claude Code: claude-plugins-community Listed
Version: 1.1.0
Forks (GitHub): 0
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.1
Downloads/month (npm): 719
Downloads/week (npm): 251
Forks (GitHub): 19
Stars (GitHub): 190
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

ai-sync vs io.github.Intina47/context-sync
Factai-syncio.github.Intina47/context-sync
Marketplaces that list it11
Stars (GitHub) (differs)4 (worse)190 (better)
Forks (GitHub) (differs)0 (worse)19 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@context-sync/server)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)11Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/oreolion/ai-sync-plugingithub.com/intina47/context-sync
Changes in the last 7 days00
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

ai-sync

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

Cross-platform AI agent synchronization. When you switch between AI coding tools (Claude Code, Cursor, Codex, Aider, Cline, Windsurf, Copilot), ai-sync maintains a shared .ai-sync/ directory so the next agent picks up exactly where the last one left off — with full context of what was done, what's next, blockers, and build status. Features conflict detection, auto-progress tracking, session audit trails, and adapter files for 9 tools.

io.github.Intina47/context-sync

In its own words, on Official MCP Registry:

Universal AI Memory - Sync context across Claude, VsCode, Cursor, Continue, Windsurf, Zed & more

How to run each

ai-sync

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.Intina47/context-sync As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio context-sync -- npx -y @context-sync/server

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: ai-sync · What it can do: io.github.Intina47/context-sync · 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