Ext Ops Panel
Open dashboard
Comparison

@ibarcarty/mcp-server-google-drive vs io.github.CloudCorpRecords/driveport

@ibarcarty/mcp-server-google-drive is an MCP server published by ibarcarty. Marketplaces we read that list it: 1 (npm registry (MCP servers)). io.github.CloudCorpRecords/driveport is an MCP server published by CloudCorpRecords. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
Marketplace@ibarcarty/mcp-server-google-driveio.github.CloudCorpRecords/driveport
npm registry (MCP servers) Listed
Version: 1.4.0
Downloads/month (npm): 773
Downloads/week (npm): 334
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Forks (GitHub): 0
Stars (GitHub): 0
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

@ibarcarty/mcp-server-google-drive vs io.github.CloudCorpRecords/driveport
Fact@ibarcarty/mcp-server-google-driveio.github.CloudCorpRecords/driveport
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@ibarcarty/mcp-server-google-drive)On your machine (@reneturcios/driveport)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/ibarcarty/mcp-server-google-drivegithub.com/cloudcorprecords/driveport
Changes in the last 7 days (differs)02
First seen (differs)2026-10-122026-11-01

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

@ibarcarty/mcp-server-google-drive

In its own words, on npm registry (MCP servers):

MCP server for Google Drive, Google Docs, Google Sheets, Google Slides, and Google Calendar with full read/write operations, rich markdown-to-docs formatting, theming, shared drive support, and OAuth2 authentication

io.github.CloudCorpRecords/driveport

In its own words, on Official MCP Registry:

Google Drive files: search, list, read, upload, download, folders and trash, as MCP tools.

How to run each

@ibarcarty/mcp-server-google-drive

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

io.github.CloudCorpRecords/driveport As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio driveport -- npx -y @reneturcios/driveport mcp

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: @ibarcarty/mcp-server-google-drive · What it can do: io.github.CloudCorpRecords/driveport · Compare two other plugins

Package data comes from the public npm registry (registry.npmjs.org). 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