Ext Ops Panel
Open dashboard
Comparison

nerdygeek vs Paparats MCP: Self-Hosted Semantic Code Search

nerdygeek is a plugin bundle for AI coding tools published by docxbox. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Paparats MCP: Self-Hosted Semantic Code Search is an MCP server published by IBazylchuk. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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
MarketplacenerdygeekPaparats MCP: Self-Hosted Semantic Code Search
Claude Code: claude-plugins-community Listed
Version: 2.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2.11.3
Downloads/month (npm): 808
Downloads/week (npm): 343
Forks (GitHub): 1
Stars (GitHub): 11
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

nerdygeek vs Paparats MCP: Self-Hosted Semantic Code Search
FactnerdygeekPaparats MCP: Self-Hosted Semantic Code Search
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)11 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last release (differs)Not published2026-10-25
Where it runs (differs)Installs as a plugin bundleOn your machine (@paparats/cli)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/docxbox/nerdygeekgithub.com/ibazylchuk/paparats-mcp
Changes in the last 7 days (differs)06
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

nerdygeek

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

NerdyGeek gives Claude Code a version-aware documentation lookup tool that dynamically discovers official docs for frameworks and libraries, retrieves the most relevant sections, filters noise, and returns structured answers with source links and code examples. It is designed to help coding agents recover from uncertainty quickly and continue working with current documentation instead of stale assumptions.

Paparats MCP: Self-Hosted Semantic Code Search

In its own words, on Official MCP Registry:

Self-hosted semantic code search MCP for Claude Code & Cursor. Multi-repo, AST-aware, stays local.

How to run each

nerdygeek As a Claude Code plugin

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

Paparats MCP: Self-Hosted Semantic Code Search

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

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: nerdygeek · What it can do: Paparats MCP: Self-Hosted Semantic Code Search · 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