How to Use the Qdrant MCP in VS Code Copilot

Q: How do we configure Qdrant access for our team in VS Code Copilot?

You define the MCP Server in your .vscode/mcp.json file and commit it to your repository. Every developer with VS Code Copilot gets immediate access to the Qdrant tools.

Q: Can VS Code Copilot run similarity searches on my Qdrant index?

Yes, it can. The agent uses the search tool to execute vector similarity queries and returns the closest matches directly inside your chat window.

Q: How does VS Code Copilot handle large Qdrant collections?

It uses the scroll tool to paginate through points and payloads. This allows you to inspect large datasets without overloading your editor's memory.

Q: Is there a way to verify the total vector count in a collection?

Yes, your agent uses the count tool to get the exact number of points in any collection, making it easy to monitor ingestion status.

Share live Qdrant database tools across your entire engineering team directly inside VS Code Copilot.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers — Included with Plan

Connect Qdrant MCP to VS Code Copilot

Create your Vinkius account to connect Qdrant to VS Code Copilot — we handle the hosting, security, and runtime updates so you don't have to. No server setup required.

GDPR Included with Plan

Setup Qdrant with VS Code Copilot

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Team-Wide Vector Tooling via VS Code Copilot

This MCP Server integrates the Qdrant `search` tool into VS Code Copilot so your team can test similarity logic without manual API client setups. This shared configuration ensures everyone on the team uses the same database endpoints. It eliminates the "works on my machine" problem when debugging complex vector search pipelines. You just commit the config to Git and go.

Production-Safe Index Inspections in VS Code

Your VS Code Copilot agent uses `get_collection` and `list_collections` to fetch structural data, allowing developers to verify vector dimensions and distance configurations safely. For fine-grained debugging, the agent can call `get_points` to pull specific vector IDs. This lets you inspect raw payload fields and confirm that your production ingestion workers are writing metadata correctly. You don't need production SSH access to debug.

Iterative Vector Debugging

Your VS Code Copilot MCP agent uses the `scroll` tool to retrieve batches of vectors and payloads, letting you analyze distribution quality directly in your workspace. If you find corrupted or outdated embeddings, the agent can run `delete` to remove those specific points. It then uses `count` to verify the updated collection size, ensuring your development environment stays in sync. This makes testing new embedding models much faster.

Setup guide

Set up Qdrant MCP in VS Code Copilot

Prerequisites

VS Code 1.99 or later with GitHub Copilot extension
Active Vinkius subscription with a valid endpoint token

1

Open MCP configuration

Open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and run "MCP: Add Server". Select HTTP (Streamable) as the server type. VS Code will create .vscode/mcp.json in your workspace.
2

Add the Qdrant MCP

Paste the JSON snippet shown on the right into your .vscode/mcp.json. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Switch to Agent mode

Open Copilot Chat (Cmd+Shift+I / Ctrl+Shift+I) and switch to Agent mode using the dropdown. MCP tools are only available in Agent mode — they do not appear in Edit or Ask modes.
4

Verify the connection

In the Copilot Chat input, type # to list available tools. You should see the Qdrant tools listed. Try asking: "List my recent Qdrant transactions" and Copilot will invoke them automatically.

.vscode/mcp.json

{
  "mcpServers": {
    "qdrant-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Qdrant. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Qdrant now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Qdrant MCP in VS Code Copilot

You define the MCP Server in your `.vscode/mcp.json` file and commit it to your repository. Every developer with VS Code Copilot gets immediate access to the Qdrant tools.

Yes, it can. The agent uses the `search` tool to execute vector similarity queries and returns the closest matches directly inside your chat window.

It uses the `scroll` tool to paginate through points and payloads. This allows you to inspect large datasets without overloading your editor's memory.

Yes, your agent uses the `count` tool to get the exact number of points in any collection, making it easy to monitor ingestion status.

All Qdrant credentials are encrypted and managed securely via Vinkius. Your actual Qdrant vector coordinates and metadata payloads are routed through ephemeral, zero-trust MCP sandboxes, ensuring no data leakage to VS Code Copilot.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript