Can the agent perform vector plus text-filtering search combined natively?

Yes. Provide the agent with the collection name alongside the text payload and tell it the exact vector structure. It leverages internal filters querying natively and returns the nearest neighbors with exact accuracy scores.

How do I make the AI create a semantic collection ready for embeddings (OpenAI 1536 dims)?

Ask the agent to use 'create_collection'. Provide standard JSON declaring the name, the field structure, and explicitly define the `float[]` field tracking the 1536 dims length. The cluster will spin the framework up instantly.

Can it delete problematic vectors holding bad geometry data manually?

Absolutely. Supplying the explicit collection target and the item 'id' to the delete_document prompt securely wipes out all traces from the dataset. Use this sparingly as it can't be undone easily.

Typesense Vector Search MCP Server for CrewAI 6 tools — connect in under 2 minutes

Name: Typesense Vector Search
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 6 Tools Framework

Connect your CrewAI agents to Typesense Vector Search through the Vinkius — pass the Edge URL in the `mcps` parameter and every Typesense Vector Search tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Typesense Vector Search Specialist",
    goal="Help users interact with Typesense Vector Search effectively",
    backstory=(
        "You are an expert at leveraging Typesense Vector Search tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token — get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Typesense Vector Search "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 6 available tools "
        "and what they can do."
    ),
)

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

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Typesense Vector Search MCP Server

Connect your Typesense Vector Search environment to any AI agent and take full autonomous control over vector collections, indexing processes, and semantic querying through daily conversation.

When paired with CrewAI, Typesense Vector Search becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Typesense Vector Search tools autonomously — one agent queries data, another analyzes results, a third compiles reports — all orchestrated through the Vinkius with zero configuration overhead.

What you can do

Vector Semantic Search — Issue combined text-filtering alongside vector similarity (vec) queries natively through chat
Collection Provisioning — Instantly create new semantic schema datasets holding complex vector embedding structures organically
Document Indexing — Let your AI insert or update JSON payloads into your database, bypassing manual code-level REST integrations
Schema & Records Insights — Retrieve absolute schema geometries mapping collections to ensure developers map fields correctly

The Typesense Vector Search MCP Server exposes 6 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Typesense Vector Search to CrewAI via MCP

Follow these steps to integrate the Typesense Vector Search MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py — CrewAI auto-discovers 6 tools from Typesense Vector Search

Why Use CrewAI with the Typesense Vector Search MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Typesense Vector Search through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles — one agent researches, another analyzes, a third generates reports — each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass the Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Typesense Vector Search + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Typesense Vector Search MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Typesense Vector Search for raw data, then a second analyst agent cross-references findings and flags anomalies — all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Typesense Vector Search, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Typesense Vector Search tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Typesense Vector Search against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Typesense Vector Search MCP Tools for CrewAI (6)

These 6 tools become available when you connect Typesense Vector Search to CrewAI via MCP:

create_collection

Provide the schema details as a JSON object. Creates a new search collection with a specific schema

delete_document

This action is irreversible. Permanently removes a document from a collection by its ID

get_collection_details

Retrieves schema and metadata for a specific collection

index_document

Provide the collection name and the document data as a JSON object. Adds or updates a document in a search collection

list_vector_collections

Lists all collections in the Typesense instance

search_vectors

Provide the collection name, a text query, and a vector_query string (e.g., "vec:(0.1, 0.2, ...)"). Performs a vector similarity search combined with optional text filtering

Example Prompts for Typesense Vector Search in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Typesense Vector Search immediately.

"List all active collections on this vector cluster. Do I have any collections initialized yet?"

"I have an embedding snippet: [0.34, 0.42, 0.99...]. Delete the document carrying ID 'test-123' and re-index it using this JSON data on collection 'faqs'."

"Explain the schema definitions used inside the 'products_inventory' collection."

Troubleshooting Typesense Vector Search MCP Server with CrewAI

Common issues when connecting Typesense Vector Search to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts — check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

The Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Typesense Vector Search + CrewAI FAQ

Common questions about integrating Typesense Vector Search MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily — when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.