Ext Ops Panel
Open dashboard
Comparison

claude-code-task-management vs Google Tasks MCP Server

claude-code-task-management is a plugin bundle for AI coding tools published by BeMySlaveDarlin. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Google Tasks MCP Server is an MCP server published by ebmurha. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
Marketplaceclaude-code-task-managementGoogle Tasks MCP Server
Claude Code: claude-plugins-community Listed
Version: 2.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.0
Downloads/month (PyPI): 126
Downloads/week (PyPI): 39
Forks (GitHub): 0
Stars (GitHub): 2
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

claude-code-task-management vs Google Tasks MCP Server
Factclaude-code-task-managementGoogle Tasks MCP Server
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)2 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (google-tasks-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 2
Hooks it runs (differs)2Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/bemyslavedarlin/cc-task-managergithub.com/ebmurha/google-tasks-mcp
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

claude-code-task-management

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

Track tasks, finalize sessions, resume context — all through natural language.

Google Tasks MCP Server

In its own words, on Official MCP Registry:

Manage Google Tasks from MCP-compatible AI clients.

How to run each

claude-code-task-management As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install claude-code-task-management@claude-community

Google Tasks MCP Server As a local MCP server: PyPI package

Claude Code
claude mcp add --env "GOOGLE_CLIENT_ID=<YOUR_GOOGLE_CLIENT_ID>" --env "GOOGLE_CLIENT_SECRET=<YOUR_GOOGLE_CLIENT_SECRET>" --env "GOOGLE_REDIRECT_URI=<YOUR_GOOGLE_REDIRECT_URI>" --transport stdio google-tasks-mcp -- uvx google-tasks-mcp

Requires: GOOGLE_CLIENT_ID (secret), GOOGLE_CLIENT_SECRET (secret), GOOGLE_REDIRECT_URI

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 claude-code-task-management publish no settings it asks for, so we do not compare settings.

What it can do: claude-code-task-management · What it can do: Google Tasks MCP Server · 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