How to Use the Qdrant MCP in CrewAI

Q: How do I expose specific Qdrant tools to a CrewAI agent?

Use MCPServerHTTP from crewai.mcp and define a toolfilter. This lets you restrict access to the MCP Server, giving your researcher agent only the search tool while keeping management tools hidden.

Q: How does CrewAI handle large paginated datasets from Qdrant?

Your agents can use the scroll tool to paginate through points. The shared memory feature in CrewAI allows the orchestrator to track the current offset, ensuring agents don't pull duplicate vectors.

Run specialized agent teams to manage and query Qdrant indexes using CrewAI.

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 CrewAI

Create your Vinkius account to connect Qdrant to CrewAI — 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 CrewAI

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Collaborative vector search with CrewAI

CrewAI allows you to split database tasks across specialized agents. This MCP Server helps a researcher agent run `search` to find similar vectors, while an analyst agent inspects the payload using `get_points` to verify data authenticity. This multi-agent coordination ensures that no single agent gets overwhelmed with vector math. The workflow passes clean structured data between roles, making your autonomous operations far more reliable than single-agent setups.

Autonomous index monitoring

Use this server to let a monitoring agent track your database health. By calling `list_collections` and `get_collection` on a schedule, the agent detects empty indexes or abnormal vector distributions without human intervention. If the agent notices a collection has dropped in size, it triggers a moderator agent to investigate. The moderator can then use `scroll` to inspect the remaining points and log the discrepancies.

Restricted tool exposure for agent safety

You don't want your research agents having delete permissions. CrewAI lets you use the MCP Server with a `tool_filter` to expose only safe tools like `count` and `search` to your front-line agents. The destructive `delete` tool is locked down, accessible only to a specialized moderator agent that requires high-level escalation. This compartmentalization keeps your vector datasets safe from rogue agent loops.

Setup guide

Set up Qdrant MCP in CrewAI

Prerequisites

Python 3.10+ installed
crewai package (pip install crewai)
Active Vinkius subscription with a valid endpoint token

1

Install CrewAI
Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.
2

Add the MCP URL to your agent
Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.
3

Kick off your crew
Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Qdrant tools as needed.

crew.py

from crewai import Agent, Task, Crew

agent = Agent(
    role="Qdrant Analyst",
    goal="Access and analyze Qdrant data via MCP.",
    backstory="Expert analyst with direct Qdrant access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Qdrant transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Get your connection token →

Prerequisites

Python 3.10+ installed
crewai + crewai-tools packages
Active Vinkius subscription with a valid endpoint token

1

Install dependencies
Run pip install crewai crewai-tools. The MCPServerAdapter handles lifecycle management and tool conversion.
2

Connect with MCPServerAdapter
Use MCPServerAdapter as a context manager with SseServerParameters pointing to your Vinkius endpoint. The adapter automatically manages connection lifecycle.
3

Assign tools and run
Pass the returned mcp_tools to your agent's tools parameter. The adapter converts MCP tools to native BaseTool objects compatible with all CrewAI agents.

crew.py

from crewai import Agent, Task, Crew
from crewai_tools import MCPServerAdapter
from mcp import SseServerParameters

server_params = SseServerParameters(
    url="https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
)

with MCPServerAdapter(server_params) as mcp_tools:
    agent = Agent(
        role="Qdrant Analyst",
        goal="Access and analyze Qdrant data via MCP.",
        backstory="Expert analyst with direct Qdrant access.",
        tools=mcp_tools,
    )

    task = Task(
        description="List recent Qdrant transactions",
        agent=agent,
        expected_output="A summary of recent activity",
    )

    crew = Crew(agents=[agent], tasks=[task])
    result = crew.kickoff()
    print(result)

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 CrewAI

Use `MCPServerHTTP` from `crewai.mcp` and define a `tool_filter`. This lets you restrict access to the MCP Server, giving your researcher agent only the `search` tool while keeping management tools hidden.

Yes, the server handles concurrent requests in an isolated Vinkius sandbox. Your researcher agent can run `search` while your analyst agent runs `get_collection` in parallel without blocking each other.

Your agents can use the `scroll` tool to paginate through points. The shared memory feature in CrewAI allows the orchestrator to track the current offset, ensuring agents don't pull duplicate vectors.

Simply pass your Vinkius endpoint URL directly into your Agent definition using the `mcps` list parameter. The framework automatically handles the MCP handshake and imports the tools.

No, the connection is direct and encrypted. Your vector floats, point IDs, and payload metadata pass through an ephemeral, zero-trust sandbox on Vinkius, ensuring your database credentials and records remain completely private.

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