Ext Ops Panel
Open dashboard
Comparison

paperless-mcp vs io.github.CloudCorpRecords/docshare

paperless-mcp is an MCP server published by tb1337. Marketplaces we read that list it: 1 (PyPI (MCP servers)). io.github.CloudCorpRecords/docshare 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-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
Marketplacepaperless-mcpio.github.CloudCorpRecords/docshare
PyPI (MCP servers) Listed
Version: 0.1.0
Downloads/month (PyPI): 126
Downloads/week (PyPI): 469
Forks (GitHub): 1
Stars (GitHub): 1
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

paperless-mcp vs io.github.CloudCorpRecords/docshare
Factpaperless-mcpio.github.CloudCorpRecords/docshare
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (paperless-mcp)On your machine (@reneturcios/docshare)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Licence (differs)MITNot stated
Repository (differs)github.com/tb1337/paperless-mcpgithub.com/cloudcorprecords/docshare
Changes in the last 7 days (differs)02
First seen (differs)2026-10-132026-11-05

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

paperless-mcp

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

Model Context Protocol server for Paperless-ngx, backed by pypaperless.

io.github.CloudCorpRecords/docshare

In its own words, on Official MCP Registry:

EveryPage tracked PDF links: upload, update and delete PDFs, variant links and webhooks.

How to run each

paperless-mcp

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

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

Claude Code
claude mcp add --transport stdio docshare -- npx -y @reneturcios/docshare 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: paperless-mcp · What it can do: io.github.CloudCorpRecords/docshare · Compare two other plugins

Package data comes from the Python Package Index (pypi.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