Can it delete documents from my search engines?

Yes. The `st.delete_documents` tool removes specific documents by ID from an engine. Each deletion requires explicit document IDs, so nothing is removed accidentally.

Does it support search analytics like CTR?

Yes. Use `st.analytics_top_searches` and `st.analytics_top_clicks` to retrieve real usage data — top queries, click-through rates, and conversion metrics.

What Swiftype plan is required?

Any plan that includes Site Search API access. You need a valid API key from your Swiftype dashboard — the integration uses standard REST endpoints available to all API-enabled accounts.

Swiftype MCP Server for CrewAI 10 tools — connect in under 2 minutes

Name: Swiftype
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 10 Tools Framework

Connect your CrewAI agents to Swiftype through Vinkius, pass the Edge URL in the `mcps` parameter and every Swiftype 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="Swiftype Specialist",
    goal="Help users interact with Swiftype effectively",
    backstory=(
        "You are an expert at leveraging Swiftype 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 Swiftype "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 10 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 Swiftype MCP Server

Empower your conversational AI with robust enterprise search capabilities by securely integrating the Swiftype (Elastic) MCP connector. Stop navigating web dashbaords to manage indexing logic; allow your LLM to act as a direct data architect interacting with your core Swiftype endpoints natively. With full support for reading, creating, and deleting JSON documents on the fly, inspecting live search engine queries, and querying direct analytical metrics like top clicks—this connector brings headless search administration straight to your preferred prompt environment.

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

What you can do

Headless Search & Suggestions — Execute strict queries interrogating custom content engines running st.post_search and provide predictive autocompletes processing st.post_suggest.
CRUD Document Indexing — Pull exact active records from isolated data maps using st.list_documents, inject new payload structures in bulk operating st.create_documents, or vaporize explicit keys commanding st.delete_documents.
Architectural Discovery — Browse registered core scopes applying st.list_engines and parse schema blueprints identifying object hierarchies with st.list_doc_types.
Search Analytics & CTR — Uncover real-world operational user conversion intent evaluating actual volume via st.analytics_top_searches and calculating active hit paths invoking st.analytics_top_clicks.

The Swiftype MCP Server exposes 10 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 Swiftype to CrewAI via MCP

Follow these steps to integrate the Swiftype 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 10 tools from Swiftype

Why Use CrewAI with the Swiftype MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Swiftype 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 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

Swiftype + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Swiftype MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Swiftype 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 Swiftype, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Swiftype 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 Swiftype against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Swiftype MCP Tools for CrewAI (10)

These 10 tools become available when you connect Swiftype to CrewAI via MCP:

st.analytics_top_clicks

Identify precise active arrays spanning native Hold parsing

st.analytics_top_searches

Inspect deep internal arrays mitigating specific Plan Math

st.create_documents

Enumerate explicitly attached structured rules exporting active Billing

st.delete_documents

json` eliminating cached pages permanently erasing bounds metrics from search. Dispatch an automated validation check routing explicit Gateway history

st.list_doc_types

json` extracting schema blueprints enforcing exact map types correctly. Retrieve explicit Cloud logging tracing explicit Vault limits

st.list_documents

json` dumping all stored metadata physically tracking IDs per document type. Irreversibly vaporize explicit validations extracting rich Churn flags

st.list_domains

json` verifying automated crawler limits mapped inside explicit index scopes. Identify precise active arrays spanning native Gateway auth

st.list_engines

json` extracting all active isolated Elastic indices bound per tenant. Identify bounded CRM records inside the Headless Swiftype Platform

st.post_search

json` firing raw queries into the specific Engine returning faceted JSON hierarchies. Perform structural extraction of properties driving active Account logic

st.post_suggest

json` bounding predictive keys and spelling tolerant matches decoupled from main indexing. Provision a highly-available JSON Payload generating hard Customer bindings

Example Prompts for Swiftype in CrewAI

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

"List all my available Swiftype search engines, then run a search for 'documentation' on the most relevant one and show me the top 3 analytics clicks it generated last week."

"List all active engines in our Swiftype account."

"Run a test suggestion for 'passw' in the internal wiki engine."

Troubleshooting Swiftype MCP Server with CrewAI

Common issues when connecting Swiftype 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

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

Swiftype + CrewAI FAQ

Common questions about integrating Swiftype 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.