qdrant-mcp-local

Created By
hirokita117a year ago
ローカル環境でQdrantとMCP-server-qdrantを簡単に立ち上げるためのDocker Compose設定
Overview

what is qdrant-mcp-local?

qdrant-mcp-local is a Docker Compose setup that allows users to easily launch Qdrant and MCP-server-qdrant in a local environment.

how to use qdrant-mcp-local?

To use qdrant-mcp-local, clone the repository, create a data directory, and run Docker Compose to start the services. The Qdrant vector search engine and MCP server will be accessible at specified local URLs.

key features of qdrant-mcp-local?

  • Easy setup of Qdrant and MCP-server-qdrant using Docker Compose
  • Persistent data storage in a local directory
  • Customizable environment variables through a .env file

use cases of qdrant-mcp-local?

  1. Setting up a local development environment for vector search applications.
  2. Testing and debugging applications that utilize the Model Context Protocol (MCP).
  3. Experimenting with Qdrant's capabilities without needing a cloud setup.

FAQ from qdrant-mcp-local?

  • What are the prerequisites for using qdrant-mcp-local?

You need Docker and Docker Compose V2 installed on your machine.

  • How do I stop the services?

You can stop the services by running docker compose down in the terminal.

  • What if the containers do not start?

You can run a debug script or check the logs for troubleshooting.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
hirokita117
Star
0
Language
Shell
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago