Ext Ops Panel
Open dashboard
Comparison

Google Drive vs Execute cuneiform-tablet-reader-mcp

Google Drive is a plugin bundle for AI coding tools published by OpenAI. Marketplaces we read that list it: 1 (Codex: openai-curated (openai/plugins)). Execute cuneiform-tablet-reader-mcp is an MCP server published by Evozim. 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
MarketplaceGoogle DriveExecute cuneiform-tablet-reader-mcp
Codex: openai-curated (openai/plugins) Listed
Version: 0.1.15
Forks (GitHub): 966
Stars (GitHub): 7 446
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.0.0
No figure published
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

Google Drive vs Execute cuneiform-tablet-reader-mcp
FactGoogle DriveExecute cuneiform-tablet-reader-mcp
Marketplaces that list it11
Stars (GitHub) (differs)7 446No figure on GitHub
Forks (GitHub) (differs)966No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (drivemcp.googleapis.com/mcp/v1)Remote server (api.m2mcent.com/cuneiform-tablet-reader-mcp/sse)
Transport (differs)Streamable HTTPSSE
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)7Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/openai/pluginsNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 8 h agoAnswered with HTTP 402 (42 h ago)

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

Google Drive

In its own words, on Codex: openai-curated (openai/plugins):

Use Google Drive as the single entrypoint for Drive, Docs, Sheets, and Slides work.

Execute cuneiform-tablet-reader-mcp

In its own words, on Official MCP Registry:

Premium agentic endpoint for cuneiform-tablet-reader-mcp.

How to run each

Google Drive As a Codex plugin

Codex
codex plugin marketplace add openai/plugins

Execute cuneiform-tablet-reader-mcp As a remote MCP server

Claude Code
claude mcp add --transport sse cuneiform-tablet-reader-mcp https://api.m2mcent.com/cuneiform-tablet-reader-mcp/sse --header "Payment-Signature: <YOUR_PAYMENT_SIGNATURE>"

Requires: Payment-Signature header

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

Only the endpoint of Google Drive responded at the last daily 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: Google Drive · What it can do: Execute cuneiform-tablet-reader-mcp · Compare two other plugins

Data comes from the public marketplace file https://github.com/openai/plugins/blob/HEAD/.agents/plugins/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