Do I need the ParseHub Desktop tool running to use this?

No. This integration operates completely natively via ParseHub's Cloud API endpoints. You only need the desktop app to build the templates originally. All executions mapped here happen on their cloud scaling servers.

Can I provide a different Start URL when running a project?

Yes. The `run_project_with_url` command allows you to explicitly provide a `start_url` query property. This instructs the ParseHub crawler to ignore its project-saved URL and begin parsing the newly mapped domain using the same semantic template.

Is the downloaded data returned in JSON or raw HTML?

The payload fetched by `get_run_data` is exported entirely as structured, pre-parsed JSON mirroring the exact template node selections defined in your project architecture.

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

Name: ParseHub
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 ParseHub and 2,500+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

Classic Setup·json

{
  "mcpServers": {
    "parsehub": {
      "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 ParseHub MCP Server

Bring ParseHub Cloud Scraping directly into your AI workflows. Manage pre-configured web scraping targets natively and orchestrate complex headless browser automation directly from chat. Dispatch run jobs on command, query execution status limits, and extract final parsed payloads securely.

GitHub Copilot Agent mode brings ParseHub 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

Project Navigation — Inspect and list configured ParseHub projects, determining start URLs, templates, and total crawler pages attached
Execution Dispatch — Command remote servers to trigger specific headless data extraction jobs run_project optionally overriding starting URLs natively
Observability Tracing — Monitor exactly where a Run object is (queued, initialized, running, complete) without checking the desktop app
Payload Extraction — Pull down structured arrays containing the scraped payloads securely via get_run_data matching explicit datasets

The ParseHub 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 ParseHub to VS Code Copilot via MCP

Follow these steps to integrate the ParseHub 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 ParseHub

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

Why Use VS Code Copilot with the ParseHub MCP Server

GitHub Copilot for Visual Studio Code provides unique advantages when paired with ParseHub 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

ParseHub + VS Code Copilot Use Cases

Practical scenarios where VS Code Copilot combined with the ParseHub 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

ParseHub MCP Tools for VS Code Copilot (10)

These 10 tools become available when you connect ParseHub to VS Code Copilot via MCP:

cancel_run

If the run was already scraping pages, partial data may be available. Data from already-scraped pages is preserved and can be retrieved with get_run_data. Use this to stop long-running scrapes or free up queue slots. Cancel a queued or actively running ParseHub run

delete_run

Cannot be undone. Use this to clean up old runs and free up storage quota on your account. Permanently delete a ParseHub run and its extracted data

get_last_ready_data

Ideal for dashboards or integrations that always want the freshest available data without managing individual run tokens. Instantly get the latest completed data for a ParseHub project

get_project

The project_token can be found via list_projects or in the ParseHub desktop client settings tab. Get detailed configuration of a specific ParseHub project

get_run_data

Only works when the run status is "complete" and data_ready is true. The JSON structure mirrors the template selection configuration set up in the ParseHub desktop client. Download the raw JSON data extracted from a completed ParseHub run

get_run_details

Poll this endpoint to wait for a run to complete before fetching data. Check the status of a specific ParseHub run

list_projects

Each project includes a project_token (unique identifier), title, last_run timestamp, and template configuration. Use the project_token for all subsequent run management operations. List all ParseHub web scraping projects

list_runs

Useful for auditing or finding a specific completed run to fetch data from. Get the history of all runs for a ParseHub project

run_project

Returns a run_token for tracking progress. The run enters a queue and begins processing within seconds. Use get_run to monitor and get_run_data to retrieve results once complete. Start a new ParseHub scraping run for a project

run_project_with_url

Perfect for scraping different pages with the same template (e.g., different product categories). The template extraction rules still apply unchanged — only the starting page changes. Start a ParseHub run targeting a custom URL instead of the project default

Example Prompts for ParseHub in VS Code Copilot

Ready-to-use prompts you can give your VS Code Copilot agent to start working with ParseHub immediately.

"Fetch the list of scrape projects I have on my ParseHub account."

"Start a new run for project 't9zx...' and check its status."

"Extract the finished data JSON payload from run ID 'run_k1l'."

Troubleshooting ParseHub MCP Server with VS Code Copilot

Common issues when connecting ParseHub 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.

ParseHub + VS Code Copilot FAQ

Common questions about integrating ParseHub 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.