Ext Ops Panel
Open dashboard
Comparison

gemini-for-claude vs thread-keeper

gemini-for-claude is a plugin bundle for AI coding tools published by philipvanlewis. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). thread-keeper is an MCP server published by po4erk91. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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
Marketplacegemini-for-claudethread-keeper
Claude Code: claude-plugins-community Listed
Version: ab68876
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.13.1
Downloads/month (PyPI): 1 654
Downloads/week (PyPI): 173
Forks (GitHub): 4
Stars (GitHub): 14
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

gemini-for-claude vs thread-keeper
Factgemini-for-claudethread-keeper
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)14 (better)
Forks (GitHub) (differs)0 (worse)4 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (threadkeeper)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/philipvanlewis/gemini-for-claudegithub.com/po4erk91/thread-keeper
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

gemini-for-claude

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

Bridge Claude Code to Google's Gemini CLI. Mirrors the pattern of the official Codex plugin but for Google's AI stack. Adds 9 slash commands under /gemini: for code review, adversarial security review with CVE search, web-grounded research via Google Search (capability Codex lacks), task delegation with 1M-token context, image generation via nanobanana, and background job management. Supports Google OAuth (free tier), API key, and Vertex AI auth. Zero npm dependencies — one auditable Node.js ESM companion script.

thread-keeper

In its own words, on Official MCP Registry:

Multi-agent shared brain across Claude, Codex, Antigravity, Gemini, Copilot, and VS Code.

How to run each

gemini-for-claude As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install gemini-for-claude@claude-community

thread-keeper As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio thread-keeper -- uvx threadkeeper

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: gemini-for-claude · What it can do: thread-keeper · 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