Ext Ops Panel
Open dashboard
Comparison

semanticsearch vs MCP Document Reader

semanticsearch is a plugin bundle for AI coding tools published by ZhuBit. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). MCP Document Reader is an MCP server published by xt765. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-18. 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
MarketplacesemanticsearchMCP Document Reader
Claude Code: claude-plugins-community Listed
Version: 0.1.0
Forks (GitHub): 3
Stars (GitHub): 29
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.3.1
Downloads/month (PyPI): 486
Downloads/week (PyPI): 128
Forks (GitHub): 7
Stars (GitHub): 23
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

semanticsearch vs MCP Document Reader
FactsemanticsearchMCP Document Reader
Marketplaces that list it11
Stars (GitHub) (differs)29 (better)23 (worse)
Forks (GitHub) (differs)3 (worse)7 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (mcp-documents-reader)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)4Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/zhubit/cowork-semantic-searchgithub.com/xt765/mcp_documents_reader
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

semanticsearch

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

A fully offline semantic search tool for Claude. Index local files (PDF, DOCX, Markdown, TXT, PPTX, CSV) into a vector database and search them using natural language. Uses hybrid search combining vector similarity with full-text keyword matching for accurate retrieval. Supports incremental indexing, 50+ languages, and runs entirely on your machine — no API keys, no data leaves your device.

MCP Document Reader

In its own words, on Official MCP Registry:

An MCP enabled multi-format document reader supporting DOCX, PDF, TXT, and Excel files

How to run each

semanticsearch As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install semanticsearch@claude-community

MCP Document Reader As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio mcp-documents-reader -- uvx mcp-documents-reader

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

The marketplaces of MCP Document Reader publish no settings it asks for, so we do not compare settings.

What it can do: semanticsearch · What it can do: MCP Document Reader · Compare two other plugins

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