Paparats MCP Server

Semantic code search for AI coding assistants. Local Qdrant, multi-repo, no API keys.

Remote serverstreamable-httpPython

What is the Paparats MCP server?

Semantic code search for AI coding assistants. Local Qdrant, multi-repo, no API keys. That is what the paparats mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

 ← try the full stack in your browser, no install (details)

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 2 tools. What each one is for:

  • Watching — The indexer container watches the projects mounted into it via chokidar with debouncing (1s default). On change, only the affected file re-enters the
  • Performance — The Performance tool exposed by this server

What it needs from you

Configuration is passed through the environment: OPENAI_API_KEY, VOYAGE_API_KEY, QDRANT_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Paparats's toolset — Watching, Performance — is a fair guide to whether it matches your workflow. It is maintained by IBazylchuk; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
WatchingThe indexer container watches the projects mounted into it via chokidar with debouncing (1s default). On change, only the affected file re-enters the pipeline. Unchanged content is never re-embedded thanks to the content
PerformanceThe Performance tool exposed by this server.

How to install the Paparats MCP server

{
  "mcpServers": {
    "paparats": {
      "command": "npx",
      "args": ["-y", "@paparats/cli"],
      "env": {
        "OPENAI_API_KEY": "your-value",
        "VOYAGE_API_KEY": "your-value",
        "QDRANT_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
OPENAI_API_KEYCredential the server authenticates with.Yes
VOYAGE_API_KEYCredential the server authenticates with.Yes
QDRANT_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Paparats to Watching.
  • Use Paparats to Performance.

Frequently asked questions

It connects Paparats to MCP-compatible AI assistants such as Claude and Cursor, exposing 2 tools (Watching, Performance) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Paparats directly.