Ext Ops Panel
Open dashboard
Comparison

numeric-mcp-toolkit vs Agent Spreadsheet MCP

numeric-mcp-toolkit is a plugin bundle for AI coding tools published by geoff-lew. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Agent Spreadsheet MCP is an MCP server published by PSU3D0. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
Marketplacenumeric-mcp-toolkitAgent Spreadsheet MCP
Claude Code: claude-plugins-community Listed
Version: 1.0.3
Forks (GitHub): 0
Stars (GitHub): 2
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.16.0
Forks (GitHub): 8
Stars (GitHub): 60
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

numeric-mcp-toolkit vs Agent Spreadsheet MCP
Factnumeric-mcp-toolkitAgent Spreadsheet MCP
Marketplaces that list it11
Stars (GitHub) (differs)2 (worse)60 (better)
Forks (GitHub) (differs)0 (worse)8 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (ghcr.io/psu3d0/agent-spreadsheet:0.16.0-full)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)20Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/geoff-lew/numeric-toolkitgithub.com/psu3d0/agent-spreadsheet
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

numeric-mcp-toolkit

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

Skills for the Numeric's MCP. Purpose-built workflows for accounting teams — rec workbooks, department anomaly scanning, cross-workspace close dashboards, audit evidence exports, close pulse reporting, consolidated flux commentary, financial metrics, clean report exports, and executive/board-ready reports.

Agent Spreadsheet MCP

In its own words, on Official MCP Registry:

Agent-safe Excel workbook analysis, editing, recalc, and verification tools.

How to run each

numeric-mcp-toolkit As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install numeric-mcp-toolkit@claude-community

Agent Spreadsheet MCP As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio agent-spreadsheet -- docker run -i --rm -i --rm -v "<YOUR_WORKBOOK_DIR>:/data" ghcr.io/psu3d0/agent-spreadsheet:0.16.0-full --workspace-root /data --transport stdio

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: numeric-mcp-toolkit · What it can do: Agent Spreadsheet MCP · 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