Paparats – Local Semantic Code Search MCP server
Local-first semantic code search across all your repos. Private context for AI coding assistants.
11 stars99 downloads/wk
Reviews
Write oneNobody has reviewed Paparats – Local Semantic Code Search MCP yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
Paparats – Local Semantic Code Search MCP tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.9 · 2026-09-20 · same rubric, same numbers if you re-run it
- Code scan31 source files scanned13/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 17 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Findings (1)
- highShell command built from a string (injection risk)
exec.shell-concatdist/commands/install.js: …tainers...').start(); try { execSync(`${composeCmd} -f "${composePath}" up -d`, { stdi…
What the publisher says
From the Paparats – Local Semantic Code Search MCP repository's README, as published. We do not edit it. Read it on GitHub
Paparats MCP
← try the full stack in your browser, no install (details)
Paparats-kvetka — a magical flower from Slavic folklore that blooms on Kupala Night and grants whoever finds it the power to see hidden things. Likewise, paparats-mcp helps your agent see the right code across a sea of repositories.
🌿 Works with Claude Code · Cursor · Windsurf · Copilot · Codex · Antigravity · any MCP-compatible agent
Give your AI coding assistant deep, real understanding of your entire workspace. Paparats indexes every repo you care about — semantically, with AST-aware chunking and a cross-chunk symbol graph — and exposes it through the Model Context Protocol. Search by meaning, follow who-uses-what through real symbol edges, see who last touched a chunk and which ticket it came from — all without your code ever leaving your machine.
📊 The built-in /ui operator console — ROI, query quality, cross-project usage, per-user activity, indexer health. Screenshot uses synthetic data (?demo=1) — no real queries, users, or project names.
file once and feeds both chunking and the cross-chunk symbol graph (calls / calledby / references / referencedby) — 11 languages including TypeScript, Python, Go, Rust, Java, Ruby, C, C++, C#.
- ⚡ One install, one config. paparats install → paparats add ~/code/repo → done.
- 🌳 AST-aware chunking and symbol extraction. Tree-sitter parses every supported
per group holds components, decisions (ADRs) and lessons learned — your agent writes them as it works and reads them before answering. Bootstrap on day one with the initarchmemory MCP prompt (the /init of architectural memory). Server-side similarity gate prevents duplicates, supersedes links replace stale decisions, a min_score threshold gates low-confidence reads, every card carries an "updated N ago" stamp, and Prometheus metrics tell you whether your memory is actually being used.
- 🧠 Architectural memory that the agent maintains itself. A second vector store
to prove it (per-query, per-user, per-anchor-project).
- 💸 Saves tokens. Returns only the chunks that matter, with token-savings telemetry
(Tempo, Jaeger, Honeycomb, Datadog, Grafana Cloud, Elastic APM), local SQLite analytics, and a built-in /ui operator console that visualises ROI, query quality, cross-project usage and indexer health in one screen.
- 🔭 Production-ready observability. Prometheus /metrics, OpenTelemetry traces
llama-swap) on your machine. No cloud, no API keys, no telemetry leaving the box. Bring your own Qdrant Cloud / embed server URL if you want.
- 🏠 100% local by default. Qdrant + a local embed server (llama.cpp llama-server +
Table of Contents
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
Install directly
Runs npx -y @paparats/cli on your machine. Read the scan report first; the gateway never runs local packages.
claude mcp add paparats-mcp -- npx -y @paparats/cli
Paparats – Local Semantic Code Search MCP: common questions
- Is Paparats – Local Semantic Code Search MCP server safe?
- Mostly: it is graded B (74/100). Read the Paparats – Local Semantic Code Search MCP safety report
- How do I install Paparats – Local Semantic Code Search MCP?
- It runs on your machine. Copy the Claude Code, Claude Desktop or Cursor config from the install section.
- Does Paparats – Local Semantic Code Search MCP need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is Paparats – Local Semantic Code Search MCP maintained?
- The last commit was 18 days ago (2026-09-03). The latest release is v2.7.0.
- What can I use instead of Paparats – Local Semantic Code Search MCP?
- Servers from other publishers that do the same job: Documentation MCP server, Socraticode MCP server and Octocode MCP server. Compare all Paparats – Local Semantic Code Search MCP alternatives.
Alternatives to Paparats – Local Semantic Code Search MCP
Same job from other publishers: the closest match first, then the best rated.
- DocumentationLocal-first document management and semantic search for AI coding agentsnot reviewedEstablishedA
- SocraticodeMCP server for enterprise local codebase indexing, semantic search, and code dependency graphs.not reviewedEstablishedB
- not reviewedEstablishedA
Bitbybit CAD MCPBitbybit 3D parametric CAD API, version-exact, for coding agents: search, describe, examples, guidenot reviewedEstablishedA- MisakanetFailure-memory layer for coding agents: search evidence-rated failure lessons by error text.not reviewedEstablishedA