MCP Server with Qdrant

Created By
ChangJunParka year ago
qdrant + mcp-qdrant-server
Overview

What is MCP Server with Qdrant?

MCP Server with Qdrant is a system that integrates the Qdrant vector database with the MCP (Model Control Protocol) server to store and retrieve code snippets efficiently.

How to use MCP Server with Qdrant?

To use the MCP Server, clone the repository, start the services using Docker Compose, and access the Qdrant UI and MCP Server through the provided local URLs.

Key features of MCP Server with Qdrant?

  • Code snippet storage and management
  • Natural language-based code search
  • Semantic search for related code retrieval
  • Support for Server-Sent Events (SSE)

Use cases of MCP Server with Qdrant?

  1. Storing and managing code snippets for easy retrieval.
  2. Searching for code snippets using natural language queries.
  3. Integrating with AI IDEs for enhanced coding assistance.

FAQ from MCP Server with Qdrant?

  • What are the system requirements?

You need Docker and Docker Compose to run the MCP Server with Qdrant.

  • How do I access the services?

You can access the Qdrant UI at http://localhost:6333/dashboard and the MCP Server at http://localhost:8000.

  • How is data stored?

Data is stored permanently in the ./qdrant_storage directory.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ChangJunPark
Star
1
Language
Shell
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago