Ext Ops Panel
Open dashboard
Comparison

Google Drive vs Desearch

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)). Desearch is an MCP server published by Desearch-ai. 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 DriveDesearch
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: 0.1.4
Downloads/month (npm): 1 889
Downloads/week (npm): 254
Forks (GitHub): 1
Stars (GitHub): 1
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 Desearch
FactGoogle DriveDesearch
Marketplaces that list it11
Stars (GitHub) (differs)7 446 (better)1 (worse)
Forks (GitHub) (differs)966 (better)1 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (drivemcp.googleapis.com/mcp/v1)Remote server (mcp.desearch.ai/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)7Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/openai/pluginsgithub.com/desearch-ai/mcp-desearch
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 7 h agoResponded 2 days ago, requires a key

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.

Desearch

In its own words, on Official MCP Registry:

AI search, X search, web search, page extraction, and X trends.

How to run each

Google Drive As a Codex plugin

Codex
codex plugin marketplace add openai/plugins

Desearch As a remote MCP server

Claude Code
claude mcp add --transport http mcp-desearch https://mcp.desearch.ai/mcp --header "x-api-key: <YOUR_DESEARCH_API_KEY>"

Requires: DESEARCH_API_KEY (secret), x-api-key header

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

Both endpoints 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

The marketplaces of Google Drive publish no settings it asks for, so we do not compare settings.

What it can do: Google Drive · What it can do: Desearch · 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