Ext Ops Panel
Open dashboard
Comparison

sanity vs sketchup-mcp2

sanity is a plugin bundle for AI coding tools published by sanity-io. Marketplaces we read that list it: 5 (Claude Code: claude-plugins-official, Official MCP Registry, Claude: knowledge-work-plugins, Claude Code: claude-plugins-community, Community GitHub marketplaces). sketchup-mcp2 is an MCP server published by zinin. Marketplaces we read that list it: 1 (PyPI (MCP servers)). As of our marketplace pass on 2026-11-08. 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
Marketplacesanitysketchup-mcp2
Claude Code: claude-plugins-official Listed
Version: 1.0.0
Forks (GitHub): 31
Stars (GitHub): 197
Not marked · First seen
Not listed
Official MCP Registry Listed
Version: 2.46.0
Forks (GitHub): 31
Stars (GitHub): 197
Not marked · First seen
Not listed
Claude: knowledge-work-plugins Listed
Version: 1.0.0
Forks (GitHub): 31
Stars (GitHub): 197
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 31
Stars (GitHub): 197
Not marked · First seen
Not listed
PyPI (MCP servers) Not listed Listed
Version: 0.4.0
Downloads/month (PyPI): 3 203
Downloads/week (PyPI): 1 292
Forks (GitHub): 9
Stars (GitHub): 58
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

sanity vs sketchup-mcp2
Factsanitysketchup-mcp2
Marketplaces that list it (differs)5 (better)1 (worse)
Stars (GitHub) (differs)197 (better)58 (worse)
Forks (GitHub) (differs)31 (better)9 (worse)
Last release (differs)2026-11-03 (better)2026-10-21 (worse)
Where it runs (differs)Remote server (mcp.sanity.io)On your machine (sketchup-mcp2)
Transport (differs)Streamable HTTPNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)15Not a bundle
LicenceMITMIT
Repository (differs)github.com/sanity-io/agent-toolkitgithub.com/zinin/sketchup-mcp2
Changes in the last 7 days (differs)10
First seen (differs)2026-10-112026-10-13
Endpoint at the last check (differs)Status out of date: last check 31 h ago returned HTTP 405no remote endpoint we check

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

sanity

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

Sanity content platform integration with MCP server, agent skills, and slash commands. Query and author content, build and optimize GROQ queries, design schemas, and set up Visual Editing.

sketchup-mcp2

In its own words, on PyPI (MCP servers):

Sketchup integration through Model Context Protocol

How to run each

sanity As a Claude Code plugin

Claude Code
/plugin install sanity@claude-plugins-official

sketchup-mcp2

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

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only sanity has a remote endpoint we check. How we check endpoints

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: sanity · What it can do: sketchup-mcp2 · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Package data comes from the Python Package Index (pypi.org). 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