Ext Ops Panel
Open dashboard
Comparison

semanticsearch vs Big Documents Agent

semanticsearch is a plugin bundle for AI coding tools published by ZhuBit. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Big Documents Agent is an MCP server published by agints.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
MarketplacesemanticsearchBig Documents Agent
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.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

semanticsearch vs Big Documents Agent
FactsemanticsearchBig Documents Agent
Marketplaces that list it11
Stars (GitHub) (differs)29No figure on GitHub
Forks (GitHub) (differs)3No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (docs.agints.com/mcp)
Transport (differs)Not statedStreamable HTTP
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-searchNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-17
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.

Big Documents Agent

In its own words, on Official MCP Registry:

Answers from long PDFs like contracts, leases, and bid packets, with the page number for each point.

How to run each

semanticsearch As a Claude Code plugin

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

Big Documents Agent As a remote MCP server

Claude Code
claude mcp add --transport http big-documents https://docs.agints.com/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

The marketplaces of Big Documents Agent publish no settings it asks for, so we do not compare settings.

What it can do: semanticsearch · What it can do: Big Documents Agent · 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