How to Scrape Websites with GitHub Copilot Agents in VS Code

GitHub Copilot's agent mode in VS Code can read your repo, run terminal commands, and edit files -- but it cannot fetch live web pages reliably. Add CrawlForge MCP and Copilot gains 31 scraping tools, from fetch_url to deep_research.

// .vscode/mcp.json
{
  "servers": {
    "crawlforge": {
      "type": "stdio",
      "command": "crawlforge-mcp-server",
      "env": { "CRAWLFORGE_API_KEY": "cf_live_your_key" }
    }
  }
}

This guide walks through enabling web scraping in GitHub Copilot agents step by step, with working TypeScript examples and troubleshooting for the common gotchas.

Table of Contents

• The Problem: Copilot's Limited Web Access
• Prerequisites
• Step 1: Install CrawlForge MCP
• Step 2: Enable Copilot Agent Mode
• Step 3: Register the MCP Server
• Step 4: Verify Tools Are Available
• Step 5: Your First Scrape
• Full Example: Generate a REST Client from Live Docs
• Advanced: Multi-Tool Workflows
• Troubleshooting
• FAQ

The Problem: Copilot's Limited Web Access

Copilot Chat has a @web participant but it rewrites your query into Bing search -- no raw page access, no structured extraction, no anti-bot bypass. In agent mode, Copilot can run shell commands, so you could pipe curl | pandoc through a tool call, but that misses JavaScript-rendered pages and trips anti-bot systems within minutes.

MCP solves this. Since VS Code 1.102 shipped general-availability MCP support in mid-2025, Copilot agents can call any MCP server you register. CrawlForge exposes 31 scraping tools as MCP, so scraping becomes a first-class agent action.

Prerequisites

• VS Code 1.102+ -- code --version
• GitHub Copilot subscription (Individual, Business, or Enterprise) with agent mode enabled
• Node.js 18+
• CrawlForge account -- free at crawlforge.dev/signup

Step 1: Install CrawlForge MCP

npm install -g crawlforge-mcp-server
crawlforge-mcp-server --version
# crawlforge-mcp-server 4.8.1

Step 2: Enable Copilot Agent Mode

1. Open VS Code settings (Cmd+, / Ctrl+,).
2. Search for chat.agent.enabled and toggle it on.
3. Open Copilot Chat (Ctrl+Alt+I / Cmd+Ctrl+I) and switch the mode dropdown from "Ask" to "Agent."

Agent mode is what enables MCP tool calls. In "Ask" or "Edit" modes, Copilot ignores registered MCP servers.

Step 3: Register the MCP Server

VS Code supports MCP at two scopes:

• Workspace -- .vscode/mcp.json in the repo root (team-shared via git)
• User -- editable via "MCP: Add Server" command palette (personal)

For team scraping, use the workspace config:

// .vscode/mcp.json
{
  "servers": {
    "crawlforge": {
      "type": "stdio",
      "command": "crawlforge-mcp-server",
      "env": {
        "CRAWLFORGE_API_KEY": "${env:CRAWLFORGE_API_KEY}"
      }
    }
  }
}

Then export the key in your shell (do not commit it):

export CRAWLFORGE_API_KEY="cf_live_your_key_here"

Or use ${input:apiKey} and VS Code will prompt once per workspace.

Step 4: Verify Tools Are Available

1. Open Copilot Chat.
2. Click the tool icon in the chat header.
3. Confirm crawlforge is listed with 31 tools. Uncheck any you want to hide.

If the list is empty, jump to Troubleshooting.

Step 5: Your First Scrape

In Copilot Chat (agent mode), paste:

The #crawlforge hint nudges Copilot toward the right tool. Copilot calls fetch_url (1 credit), receives HTML, parses titles, and returns them inline.

Full Example: Generate a REST Client from Live Docs

Here is a concrete workflow: auto-generate a typed Stripe client from the live documentation.

Prompt Copilot agent:

Copilot issues this MCP call:

// What Copilot sends via MCP to CrawlForge
{
  "tool": "extract_content",
  "arguments": {
    "url": "https://docs.stripe.com/api/charges/create",
    "options": { "format": "markdown" }
  }
}
// Response: clean markdown of the endpoint docs

Copilot reads the markdown and writes:

// src/clients/stripe-charges.ts
import { z } from 'zod';

export const CreateChargeParams = z.object({
  amount: z.number().int().positive(),
  currency: z.string().length(3),
  source: z.string().optional(),
  customer: z.string().optional(),
  description: z.string().max(500).optional(),
  receipt_email: z.string().email().optional(),
  statement_descriptor: z.string().max(22).optional(),
});

export type CreateChargeParams = z.infer<typeof CreateChargeParams>;

export async function createCharge(params: CreateChargeParams) {
  const validated = CreateChargeParams.parse(params);
  const body = new URLSearchParams();
  for (const [key, value] of Object.entries(validated)) {
    if (value !== undefined) body.append(key, String(value));
  }

  const response = await fetch('https://api.stripe.com/v1/charges', {
    method: 'POST',
    headers: {
      'Authorization': `Bearer ${process.env.STRIPE_SECRET_KEY}`,
      'Content-Type': 'application/x-www-form-urlencoded',
    },
    body,
  });

  if (!response.ok) {
    const error = await response.json();
    throw new Error(`Stripe error: ${error.error?.message ?? response.statusText}`);
  }

  return response.json();
}

Cost: 2 credits (one extract_content call). Repeat for every Stripe endpoint and you have a full typed client derived from live docs.

Advanced: Multi-Tool Workflows

Copilot agents excel at chaining tools. Example prompt:

Copilot runs the three MCP calls sequentially, feeds results forward, and writes the markdown. Total cost: ~11 credits (5 + 2 + 2 + 2).

Credit Quick Reference

Troubleshooting

Tools list is empty -- Agent mode is off. Enable chat.agent.enabled in settings and switch chat mode to "Agent."

"Spawn ENOENT: crawlforge-mcp-server" -- VS Code cannot find the binary. Use an absolute path in .vscode/mcp.json: "command": "/usr/local/bin/crawlforge-mcp-server".

Copilot ignores the MCP server -- Prefix your prompt with #crawlforge or explicitly name a tool: "Use fetch_url to...". Copilot sometimes picks built-in tools by default.

401 Unauthorized -- The env var is not reaching the server. Check echo $CRAWLFORGE_API_KEY in the same shell that launched VS Code. On macOS, GUI-launched VS Code does not inherit shell env -- launch via code . from the terminal.

Workspace MCP config not loading -- VS Code does not auto-trust .vscode/mcp.json. Open the file, click the "Trust" notification, then reload the window.

Next Steps

• Read the 31-tools overview to see the full toolkit
• Study the MCP protocol explainer for how VS Code talks to servers
• See getting started docs for the REST API
• Compare to Firecrawl alternative if you are evaluating scraping vendors

Start free with 1,000 credits at crawlforge.dev/signup.