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.

Parseur MCP Server for VS Code Copilot 10 tools — connect in under 2 minutes

Name: Parseur
Availability: InStock
Author: Vinkius

code.visualstudio.com/docs/copilot/chat/mcp-servers

Built by Vinkius GDPR 10 Tools IDE

GitHub Copilot in VS Code is the most widely adopted AI coding assistant, embedded directly into the world's most popular code editor. With MCP support in Agent mode, Copilot can access external data and APIs to generate context-aware code grounded in real-time information.

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.

RecommendedModern Approach — Zero Configuration

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.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "parseur": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

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

GitHub Copilot Agent mode brings Parseur data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 10 tools — Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

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: parsed correctly
Payload Uploading — Instruct the node limits mapping upload_document generating raw payloads routing straight into the engine for OCR logic
Job Management — Discover disconnected states mitigating failed validations by pushing retry_document instantly forcing physical pipeline resets

The Parseur MCP Server exposes 10 tools through the Vinkius. Connect it to VS Code Copilot 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 VS Code Copilot via MCP

Follow these steps to integrate the Parseur MCP Server with VS Code Copilot.

Create MCP config

Create a .vscode/mcp.json file in your project root

Add the server config

Paste the JSON configuration above

Enable Agent mode

Open GitHub Copilot Chat and switch to Agent mode using the dropdown

Start using Parseur

Ask Copilot: "Using Parseur, help me..." — 10 tools available

Why Use VS Code Copilot with the Parseur MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with Parseur through the Model Context Protocol.

VS Code is used by over 70% of developers — adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

Project-scoped MCP configs (`.vscode/mcp.json`) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

Parseur + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the Parseur MCP Server delivers measurable value.

Live API integration: Copilot can query an MCP server, inspect the response schema, and generate typed API client code in the same step

DevSecOps workflows: security teams can give developers access to domain intelligence tools directly in their editor for real-time vulnerability assessment during code review

Data pipeline development: Copilot fetches sample data via MCP and generates transformation scripts, validators, and test fixtures from actual API responses

Documentation generation: Copilot queries available tools and auto-generates README sections, API reference docs, and usage examples

Parseur MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect Parseur to VS Code Copilot 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 VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot 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 VS Code Copilot

Common issues when connecting Parseur to VS Code Copilot through the Vinkius, and how to resolve them.

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Parseur + VS Code Copilot FAQ

Common questions about integrating Parseur MCP Server with VS Code Copilot.

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.