Unstructured MCP Server for CrewAI 6 tools — connect in under 2 minutes
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.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
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)
* 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.
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 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.
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
Unstructured + CrewAI Use Cases
Practical scenarios where CrewAI combined with the Unstructured MCP Server delivers measurable value.
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
Scheduled intelligence reports: set up a crew that periodically queries Unstructured, analyzes trends over time, and generates executive briefings in markdown or PDF format
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
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:
get_workflow_details
Retrieves configuration details for a specific processing workflow
list_data_destinations
g. Vector DBs, SQL). Lists all configured target locations for processed data
list_data_sources
Lists all configured remote data connectors (e.g. S3, GCS)
list_processing_workflows
Lists all end-to-end document processing pipelines
list_workflow_jobs
Lists all active and historical workflow execution jobs
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.
"Show me all our active destination connectors."
"List the historical processing jobs from today."
"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.
MCP tools not discovered
Agent not using tools
Timeout errors
Rate limiting or 429 errors
Unstructured + CrewAI FAQ
Common questions about integrating Unstructured MCP Server with CrewAI.
How does CrewAI discover and connect to MCP tools?
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?
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?
Can CrewAI agents call multiple MCP tools in parallel?
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)?
crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.Connect Unstructured with your favorite client
Step-by-step setup guides for every MCP-compatible client and framework:
Anthropic's native desktop app for Claude with built-in MCP support.
AI-first code editor with integrated LLM-powered coding assistance.
GitHub Copilot in VS Code with Agent mode and MCP support.
Purpose-built IDE for agentic AI coding workflows.
Autonomous AI coding agent that runs inside VS Code.
Anthropic's agentic CLI for terminal-first development.
Python SDK for building production-grade OpenAI agent workflows.
Google's framework for building production AI agents.
Type-safe agent development for Python with first-class MCP support.
TypeScript toolkit for building AI-powered web applications.
TypeScript-native agent framework for modern web stacks.
Python framework for orchestrating collaborative AI agent crews.
Leading Python framework for composable LLM applications.
Data-aware AI agent framework for structured and unstructured sources.
Microsoft's framework for multi-agent collaborative conversations.
Connect Unstructured to CrewAI
Get your token, paste the configuration, and start using 6 tools in under 2 minutes. No API key management needed.
