Parseur MCP Server for Cline 10 tools — connect in under 2 minutes
Cline is an autonomous AI coding agent inside VS Code that plans, executes, and iterates on tasks. Wire Parseur through the Vinkius and Cline gains direct access to every tool — from data retrieval to workflow automation — without leaving the terminal.
ASK AI ABOUT THIS MCP SERVER
Vinkius supports streamable HTTP and SSE.
Vinkius Desktop App
The modern way to manage MCP Servers — no config files, no terminal commands. Install Parseur and 2,500+ MCP Servers from a single visual interface.
{
"mcpServers": {
"parseur": {
"url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
}
}
}
* 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 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.
Cline operates autonomously inside VS Code — it reads your codebase, plans a strategy, and executes multi-step tasks including Parseur tool calls without waiting for prompts between steps. Connect 10 tools through the Vinkius and Cline can fetch data, generate code, and commit changes in a single autonomous run.
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
The Parseur MCP Server exposes 10 tools through the Vinkius. Connect it to Cline 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 Parseur to Cline via MCP
Follow these steps to integrate the Parseur MCP Server with Cline.
Open Cline MCP Settings
Click the MCP Servers icon in the Cline sidebar panel
Add remote server
Click "Add MCP Server" and paste the configuration above
Enable the server
Toggle the server switch to ON
Start using Parseur
Ask Cline: "Using Parseur, help me..." — 10 tools available
Why Use Cline with the Parseur MCP Server
Cline provides unique advantages when paired with Parseur through the Model Context Protocol.
Cline operates autonomously — it reads your codebase, plans a strategy, and executes multi-step tasks including MCP tool calls without step-by-step prompts
Runs inside VS Code, so you get MCP tool access alongside your existing extensions, terminal, and version control in a single window
Cline can create, edit, and delete files based on MCP tool responses, enabling end-to-end automation from data retrieval to code generation
Transparent execution: every tool call and file change is shown in Cline's activity log for full visibility and approval before committing
Parseur + Cline Use Cases
Practical scenarios where Cline combined with the Parseur MCP Server delivers measurable value.
Autonomous feature building: tell Cline to fetch data from Parseur and scaffold a complete module with types, handlers, and tests
Codebase refactoring: use Parseur tools to validate live data while Cline restructures your code to match updated schemas
Automated testing: Cline fetches real responses from Parseur and generates snapshot tests or mocks based on actual payloads
Incident response: query Parseur for real-time status and let Cline generate hotfix patches based on the findings
Parseur MCP Tools for Cline (10)
These 10 tools become available when you connect Parseur to Cline via MCP:
create_mailbox
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
create_template
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
get_document_data
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
get_document_details
Does not include the parsed data itself — use get_document_data for that. Get metadata of a single parsed document
get_mailbox
Use this to verify mailbox setup before sending documents. Get detailed configuration of a specific Parseur mailbox
list_documents
Each entry includes document ID, status (processed, failed, pending), and metadata like sender and received date. List all parsed documents inside a Parseur mailbox
list_mailboxes
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
list_templates
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
retry_document
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
upload_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
Example Prompts for Parseur in Cline
Ready-to-use prompts you can give your Cline agent to start working with Parseur immediately.
"Check my Parseur mailboxes to find the specific bounding IDs."
"Get the data schema parsed tightly inside document doc_987."
"Upload this snippet of parsed text directly into Mailbox xyz12 for OCR processing."
Troubleshooting Parseur MCP Server with Cline
Common issues when connecting Parseur to Cline through the Vinkius, and how to resolve them.
Server shows error in sidebar
Parseur + Cline FAQ
Common questions about integrating Parseur MCP Server with Cline.
How does Cline connect to MCP servers?
Can Cline run MCP tools without approval?
Does Cline support multiple MCP servers at once?
Connect Parseur 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 Parseur to Cline
Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.