Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx agentmods add instructions/deveyus/qdrant-mcp-server/agents-mdgit clone --depth 1 https://github.com/deveyus/qdrant-mcp-serverWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/deveyus/qdrant-mcp-server/agents-md)<a href="https://agentmods.dev/instructions/deveyus/qdrant-mcp-server/agents-md"><img src="https://agentmods.dev/badge/instructions/deveyus/qdrant-mcp-server/agents-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5 | $0.00945 | $0.00945 |
| Opus 5 | $0.00473 | $0.00473 |
| Sonnet 5 | $0.00189 | $0.00189 |
| Haiku 4.5 | $0.00094 | $0.00094 |
Grade A, and why
qdrant-mcp-server AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 3d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.
AGENTS.md
This file guides AI agents (Claude Code, OpenCode, Cursor) working in this repository.
What this repository is
A fork of mhalder/qdrant-mcp-server,
upstream MIT (c) 2025 Martin Halder and contributors. All upstream code belongs
to upstream. This fork adds exactly one change on top of upstream main:
recencyscoring forsemantic_searchandhybrid_search. Fresh documents surface ahead of older near-duplicates via Qdrant'sexp_decayformula.
See README.md -> "Fork Changes" for the full description.
Stack
- Node.js 22.x or 24.x, TypeScript, compiled with
tsctobuild/. - Native module
tree-sitterbuilds against system C++ headers. - Backend: Qdrant (vector DB), embedding via OpenCode-compatible provider (Ollama/OpenAI/etc.).
Build
npm install
# Node 22.x
npm run build
# Node 24.x: native module needs C++20
CXXFLAGS='-std=c++20' npm install
npm run build
Output goes to build/index.js. build/ and node_modules/ are gitignored.
Run
stdio transport is the default:
node build/index.js
Environment variables are documented in README.md -> Advanced Configuration.
The two most important: QDRANT_URL (your Qdrant server) and
EMBEDDING_PROVIDER (default ollama).
Registering the MCP server with OpenCode
Add this to opencode.json (project-scope or ~/.config/opencode/opencode.json):
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"qdrant": {
"type": "local",
"command": ["node", "/path/to/qdrant-mcp-server/build/index.js"],
"enabled": true,
"environment": {
"QDRANT_URL": "http://localhost:6333",
"EMBEDDING_PROVIDER": "ollama"
}
}
}
}
commandis an array of strings, never a single string.typeis required.- Point
QDRANT_URLat your Qdrant server; setEMBEDDING_PROVIDERand, if needed,EMBEDDING_BASE_URL/EMBEDDING_MODELto match your embedding setup. - Save + restart OpenCode after any config change; config is loaded at startup.
- See
README.md-> OpenCode Setup for the full example, including a permission block that auto-approves the search tools.
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 3d ago First seen · 112 lines · 945 tokens per session scan A 992f5472174d
qdrant-mcp-server AGENTS.md is an instructions file published in the GitHub repository deveyus/qdrant-mcp-server (0 stars, last pushed 18d ago), licensed MIT. It adds 945 tokens to every session, about $0.0047 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.
Other instructions, from other repositories
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
next.js AGENTS.md
Instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.