2,500+ MCP servers ready to use
Vinkius

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

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.

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

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "browserhub": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Browserhub
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 Browserhub MCP Server

Connect your Browserhub.io account to any AI agent and orchestrate your web scraping, data extraction, and proxy management workflows through natural conversation.

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

  • Scraper Oversight — List all your configured scrapers and blueprints, and retrieve detailed metadata for each.
  • Job Execution — Trigger scraping jobs with dynamic URL overrides and monitor their progress in real-time.
  • Direct Scraping — Perform one-off URL extractions using real browsers without pre-defined scrapers.
  • Data Retrieval — Retrieve structured data captured by your jobs directly into your workspace.
  • Infrastructure Management — List available proxy locations and check your account credit balance.
  • Task History — List and inspect all your previous scraping jobs.

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

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

01

Create MCP config

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

02

Add the server config

Paste the JSON configuration above

03

Enable Agent mode

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

04

Start using Browserhub

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

Why Use VS Code Copilot with the Browserhub MCP Server

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

01

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

02

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

03

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

04

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

Browserhub + VS Code Copilot Use Cases

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

01

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

02

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

03

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

04

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

Browserhub MCP Tools for VS Code Copilot (10)

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

01

direct_scrape

Perform a one-off URL scrape without a pre-defined scraper

02

get_account_balance

Check account credit balance

03

get_blueprint

Get details of a specific blueprint

04

get_scraper

Get details of a specific scraper

05

get_scraping_job

Get status and results of a scraping job

06

list_blueprints

List all scraper blueprints

07

list_proxy_locations

List all available proxy locations

08

list_scrapers

List all configured scrapers

09

list_scraping_jobs

List all scraping jobs

10

run_scraper

Start a scraping job using a specific scraper

Example Prompts for Browserhub in VS Code Copilot

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

01

"List all my configured scrapers in Browserhub."

02

"Scrape the URL https://example.com using the 'E-commerce' scraper."

03

"Check my Browserhub account credit balance."

Troubleshooting Browserhub MCP Server with VS Code Copilot

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

01

MCP tools not available

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

Browserhub + VS Code Copilot FAQ

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

01

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

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

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

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.

Connect Browserhub to VS Code Copilot

Get your token, paste the configuration, and start using 10 tools in under 2 minutes. No API key management needed.