2,500+ MCP servers ready to use
Vinkius

Unstructured MCP Server for CrewAI 6 tools — connect in under 2 minutes

Built by Vinkius GDPR 6 Tools Framework

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

Vinkius supports streamable HTTP and SSE.

python
from crewai import Agent, Task, Crew

agent = Agent(
    role="Unstructured Specialist",
    goal="Help users interact with Unstructured effectively",
    backstory=(
        "You are an expert at leveraging Unstructured 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 Unstructured "
        "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)
Unstructured
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 Unstructured MCP Server

Connect your Unstructured.io account to any AI agent to automate data ingestion and document processing pipelines seamlessly. Transform complex files into clean, AI-ready data without leaving your workflow.

When paired with CrewAI, Unstructured becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Unstructured 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

  • Data Sources — List all configured remote data connectors (e.g. S3, GCS, SharePoint) to see where documents can be pulled from.
  • Data Destinations — Browse target locations (like Vector DBs or SQL databases) where structured output is sent.
  • Processing Workflows — List end-to-end pipelines, retrieve specific workflow configurations, and explore source-destination mappings.
  • Job Execution — Manually trigger immediate document ingestion and partitioning jobs, and track their execution IDs.
  • Job Monitoring — List active and historical workflow execution jobs to monitor the progress of your document processing tasks.

The Unstructured 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 Unstructured to CrewAI via MCP

Follow these steps to integrate the Unstructured MCP Server with CrewAI.

01

Install CrewAI

Run pip install crewai

02

Replace the token

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

03

Customize the agent

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

04

Run the crew

Run python crew.py — CrewAI auto-discovers 6 tools from Unstructured

Why Use CrewAI with the Unstructured MCP Server

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

01

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

02

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

03

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

04

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

Unstructured + CrewAI Use Cases

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

01

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

02

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

03

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

04

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

Unstructured MCP Tools for CrewAI (6)

These 6 tools become available when you connect Unstructured to CrewAI via MCP:

01

get_workflow_details

Retrieves configuration details for a specific processing workflow

02

list_data_destinations

g. Vector DBs, SQL). Lists all configured target locations for processed data

03

list_data_sources

Lists all configured remote data connectors (e.g. S3, GCS)

04

list_processing_workflows

Lists all end-to-end document processing pipelines

05

list_workflow_jobs

Lists all active and historical workflow execution jobs

06

trigger_workflow_execution

Returns a job ID. Manually triggers an immediate execution of a processing workflow

Example Prompts for Unstructured in CrewAI

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

01

"Show me all our active destination connectors."

02

"List the historical processing jobs from today."

03

"Trigger the engineering onboarding workflow."

Troubleshooting Unstructured MCP Server with CrewAI

Common issues when connecting Unstructured to CrewAI through the Vinkius, and how to resolve them.

01

MCP tools not discovered

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

Agent not using tools

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

Timeout errors

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

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.

Unstructured + CrewAI FAQ

Common questions about integrating Unstructured MCP Server with CrewAI.

01

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.
02

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.
03

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.
04

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.
05

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.

Connect Unstructured to CrewAI

Get your token, paste the configuration, and start using 6 tools in under 2 minutes. No API key management needed.