Bring Ocr
to CrewAI
Create your Vinkius account to connect Parseur to CrewAI and start using all 10 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the Parseur MCP Server?
Bring Parseur Document Extraction arrays directly into your AI workflows. By explicitly mapping into powerful OCR and templating engines, your agent can push unstructured PDFs or bulk emails into remote routing limits, parsing exact text fields securely. Extract fields, examine documents, list defined parse-templates, and retry pipelines without manual intervention.
What you can do
- Mailboxes & Templates — Examine specifically bound mailboxes tracking which explicit templates dictate data extraction limits mapped natively
- Document Navigation — Extract properties showing precisely which unstructured strings were identified inside uploaded payloads checking
status: parsedcorrectly - Payload Uploading — Instruct the node limits mapping
upload_documentgenerating raw payloads routing straight into the engine for OCR logic - Job Management — Discover disconnected states mitigating failed validations by pushing
retry_documentinstantly forcing physical pipeline resets
How it works
- Subscribe to this server
- Enter your Parseur API Key explicitly
- Start evaluating explicit AI OCR workflows reliably via Claude, Cursor, or any MCP structure
Who is this for?
- Operational Workflows — explicitly map invoicing pipelines investigating extraction errors remotely avoiding web limits
- Finance Teams — trace OCR receipts dynamically identifying missing fields from Chat architectures directly into a JSON limit natively
- Developers — route manual document loads simulating continuous AI logic mapping testing integrations on webhook bounds
Built-in capabilities (10)
The type determines the parsing engine (e.g., "pdf", "email", "attachment"). Once created, you can configure templates and forward documents to the mailbox for automatic extraction. Create a new Parseur mailbox for document parsing
Pass the template name and a JSON config string defining field mappings. Parseur will use this template to extract structured data from matching documents. Create a new extraction template for a Parseur mailbox
Fields depend on the template configuration (e.g., invoice_number, total_amount, line_items). Only works for documents with status "processed". Retrieve the fully extracted JSON data from a parsed document
Does not include the parsed data itself — use get_document_data for that. Get metadata of a single parsed document
Use this to verify mailbox setup before sending documents. Get detailed configuration of a specific Parseur mailbox
Each entry includes document ID, status (processed, failed, pending), and metadata like sender and received date. List all parsed documents inside a Parseur mailbox
Each mailbox represents a parsing pipeline for a specific document type (invoices, receipts, emails). Use the returned mailbox IDs for subsequent operations like listing documents or uploading files. List all Parseur parsing mailboxes
Templates define the extraction rules (field names, locations, regex patterns) used to pull structured data from incoming documents. List available extraction templates for a Parseur mailbox
Useful after fixing template rules or when the original parse failed due to a transient error. The document will be matched against the latest template rules. Retry parsing a failed or errored Parseur document
eml) to the specified mailbox for automatic parsing. The document enters the processing queue and will be parsed according to the mailbox template. Returns the new document ID for tracking. Upload a document URL to a Parseur mailbox for parsing
Why CrewAI?
When paired with CrewAI, Parseur becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Parseur tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.
- —
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
mcpsparameter 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
Parseur in CrewAI
Why run Parseur with Vinkius?
The Parseur connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 10 tools are ready to work instantly without any complex setup.
You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.
* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure
Over 4,000 integrations ready for AI agents
Explore a vast library of pre-built integrations, optimized and ready to deploy.
Connect securely in under 30 seconds
Generate tokens to authenticate and link external services in a single step.
Complete visibility into every agent action
Audit live requests, latency, success rates, and active security compliance policies.
Optimize spending and track token ROI
Analyze real-time token consumption and cost metrics detailed by connection.
Explore our live AI Agents Analytics dashboard to see it all working
This dashboard is included when you connect Parseur using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.
Parseur and 4,000+ other AI tools. No hosting, no code, ready to use.
Professionals who connect Parseur to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.
Raw MCP | Vinkius | |
|---|---|---|
| Ready-to-use MCPs | Find and configure each manually | 4,000+ MCPs ready to use |
| Connection Setup | Manual coding & server setup | 1-click instant connection |
| Server Hosting | You host it yourself (needs 24/7 uptime) | 100% hosted & managed by Vinkius |
| Security & Privacy | Stored in plaintext config files | Bank-grade encrypted vault |
| Activity Visibility | Blind execution (no logs or tracking) | Live dashboard with real-time logs |
| Cost Control | Runaway AI token spend risk | Automatic budget limits |
| Revoking Access | Must delete files or code to stop | 1-click disconnect button |
How Vinkius secures
Parseur for CrewAI
Every request between CrewAI and Parseur is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.
Frequently asked questions
Does this tool parse the document directly or use the cloud engine?
The tool offloads the logic specifically via endpoints mapping back to the Parseur Cloud Engine. The AI acts to organize mailboxes, list templates, and fetch final states securely without computing massive local OCR networks.
Can I upload a raw file string to be parsed?
Yes. Utilizing the explicitly mapped upload_document constraint, the agent can inject raw string boundaries identifying formatting, passing files straightforward into the target mailbox ID natively.
Will I see missing required fields if extraction fails?
Absolutely. Querying get_document_details lists specific status bounds. If a template expects InvoiceTotal and misses it, the document flags a processing boundary issue precisely traceable here.
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.
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.
Explore More MCP Servers
View all →
Denim
10 toolsEquip your AI agent to manage marketing campaigns, track contacts, and monitor analytics via the Denim API.
Deterministic 50/30/20 Budget Engine
1 toolsTransform your AI into a hyper-precise financial controller. Mathematically enforce the 50/30/20 budgeting rule on pre-categorized expense pipelines to detect exact capital deviations.
Temu Seller Hub
12 toolsAutomate cross-border e-commerce ops via Temu — manage orders, track fulfillment, sync inventory, and process returns natively from any AI agent.
Shippify
11 toolsAutomate logistics and last-mile delivery via Shippify — manage deliveries, tracking, and warehouses directly from any AI agent.