npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

embarsy-qdrant-mcp

v0.1.8

Published

Codebase-indexing MCP server for Embarsy — semantic code search over a local Qdrant + OpenAI-compatible embeddings stack. Routes embeddings and Qdrant through Embarsy's proxy so auth and Monitoring counters just work.

Readme

embarsy-qdrant-mcp

Codebase-indexing MCP server for Embarsy — semantic code search for Claude Code and Codex, backed by a local Qdrant + OpenAI-compatible embeddings stack.

It indexes a directory of source into Qdrant and exposes a search_code MCP tool. Everything runs through Embarsy's proxy on localhost:8000, so the API keys are honored and both the embedding and Qdrant counters move in Embarsy → Monitoring. Pure JS — no native build.

Using the Embarsy app? You don't need this package: the bridge ships inside Embarsy 0.2.3+, and Connections → Connect wires up Claude Code and Codex for you. This package is for working from the terminal.

Install

npm install -g embarsy-qdrant-mcp

Provides two commands: embarsy-index (index a codebase) and embarsy-mcp (the MCP server + config helpers).

Configuration

Set via environment variables. Only the two API keys are required — everything else defaults to Embarsy.

| Variable | Default | Notes | |---|---|---| | OPENAI_API_KEY | — | required — Embarsy → Connections → Zoo / Roo Code → API Key | | QDRANT_API_KEY | — | required — Embarsy → Connections → Zoo / Roo Code → Qdrant API Key | | QDRANT_COLLECTION_NAME | see notes | indexing: embarsy-<dir> (or --collection). Search: when unset, the index covering the editor's folder is picked automatically | | OPENAI_BASE_URL | http://localhost:8000/v1 | OpenAI-compatible embeddings endpoint | | EMBEDDING_MODEL | qwen3-embedding | | | EMBEDDING_DIMENSION | 1024 | must match the model | | QDRANT_URL | http://localhost:8000/qdrant | Qdrant REST (Embarsy proxy) |

Index a codebase

OPENAI_API_KEY=<API Key> QDRANT_API_KEY=<Qdrant API Key> \
  embarsy-index ~/projects/my-app --collection my-app

Re-run any time — it's incremental (unchanged files are skipped, deleted files are pruned), respects every .gitignore in the tree (so a folder holding several projects honours each project's own), and skips vendored/binary/oversized files and build output.

Wire it into your editor

The setup helpers write the config with absolute node + script paths, so the desktop apps (which don't inherit your shell PATH) can always launch the server.

Codex — appends to ~/.codex/config.toml:

OPENAI_API_KEY=<API Key> QDRANT_API_KEY=<Qdrant API Key> embarsy-mcp --setup-codex

Restart Codex, run /mcp → embarsy-qdrant appears.

Claude Code — writes ~/.claude.json, so it works in every indexed folder (add --project to write a .mcp.json in the current folder instead):

OPENAI_API_KEY=<API Key> QDRANT_API_KEY=<Qdrant API Key> embarsy-mcp --setup-claude

One registration serves every indexed project: the server picks the index from the folder the editor is working in. Set QDRANT_COLLECTION_NAME only to pin one collection everywhere.

MCP tools

  • search_code — semantic search; returns the most relevant chunks with file:line and a snippet. When the index covers a parent of the editor's folder (say ~/code while you work in ~/code/my-app), it searches my-app/ first and widens to the whole index only if nothing there is convincing; whole_index: true searches everything from the start. Paths come back relative to the editor's folder, or absolute when outside it.
  • index_status — how many chunks are indexed in the collection.

License

PolyForm Strict 1.0.0 — source-available, not open source: noncommercial use only, no redistribution or modification without a separate written license. The full text ships with this package (LICENSE). Commercial or modification license → [email protected].