Qdrant Retrieve MCP Server

Created By
gergelyszerovaya year ago
MCP server for semantic search with Qdrant vector database
Overview

what is Qdrant Retrieve MCP Server?

Qdrant Retrieve MCP Server is a server designed for semantic search using the Qdrant vector database, enabling efficient retrieval of semantically similar documents across multiple collections.

how to use Qdrant Retrieve MCP Server?

To use the server, configure it with the Qdrant API key and specify the Qdrant instance URL. You can then send queries to retrieve similar documents based on your input.

key features of Qdrant Retrieve MCP Server?

  • Semantic search across multiple collections
  • Multi-query support for enhanced search capabilities
  • Configurable result count to tailor the output
  • Collection source tracking for better context

use cases of Qdrant Retrieve MCP Server?

  1. Retrieving relevant documents for research purposes
  2. Enhancing search functionalities in applications
  3. Analyzing large datasets for semantic similarities

FAQ from Qdrant Retrieve MCP Server?

  • What is the default port for the MCP HTTP server?

The default port for the MCP HTTP server is 3001.

  • Can I enable HTTP transport?

Yes, you can enable HTTP transport by using the --enableHttpTransport option.

  • Is there a REST API available?

Yes, you can enable the REST API server by using the --enableRestServer option.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gergelyszerovay
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Alloy

2 days ago
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)

8 hours ago
Crevio

a day ago