MCP server
by pyscout
WebScout automates chat API analysis using Selenium for software testing and packet analyzer tools to reveal hidden endp
Automates the reverse engineering of chat interfaces by controlling a browser, capturing network traffic, and identifying streaming API endpoints without needing official documentation.
WebScout is a community-built MCP server published by pyscout that provides AI assistants with tools and capabilities via the Model Context Protocol. WebScout automates chat API analysis using Selenium for software testing and packet analyzer tools to reveal hidden endp It is categorized under browser automation, search web. This server exposes 14 tools that AI clients can invoke during conversations and coding sessions.
You can install WebScout in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
MIT
WebScout is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
Fetch and extract information from websites automatically
Example
Research competitor pricing, scrape product reviews, monitor news mentions
Automate 5-10 hours/week of manual web research
Track website changes, new content, price updates
Example
Monitor competitor blog for new posts, track stock availability, watch for pricing changes
Stay informed without manual checking, never miss important updates
Extract structured data from multiple websites
Example
Compile product listings from 10 e-commerce sites, aggregate job postings, collect real estate data
Build datasets 100x faster than manual copying
Share your MCP server with the developer community
WebScout is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
According to our notes, WebScout benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
WebScout reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
Useful MCP listing: WebScout is the kind of server we cite when onboarding engineers to host + tool permissions.
Useful MCP listing: WebScout is the kind of server we cite when onboarding engineers to host + tool permissions.
We wired WebScout into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
WebScout reduced integration guesswork — categories and install configs on the listing matched the upstream repo.
We evaluated WebScout against two servers with overlapping tools; this profile had the clearer scope statement.
WebScout has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
Useful MCP listing: WebScout is the kind of server we cite when onboarding engineers to host + tool permissions.
showing 1-10 of 75
WebScout MCP is a powerful Model Context Protocol (MCP) server designed for reverse engineering web applications, particularly chat interfaces and streaming APIs. It provides comprehensive browser automation tools to discover, analyze, and capture network traffic from complex web applications.
reverse_engineer_chat - Automated analysis of chat interfaces with streaming endpoint discoverystart_network_capture - Begin comprehensive network traffic monitoringstop_network_capture - End capture and retrieve all collected dataget_network_capture_status - Check capture session status and statisticsclear_network_capture - Clear captured data without stopping the capture sessioninitialize_session - Create a new browser session for interactive operationsclose_session - Clean up browser resources and end sessionnavigate_to_url - Navigate to different URLs within a sessionswitch_tab - Switch between open browser tabsclick_element - Click buttons, links, or any interactive elementsfill_form - Fill out form fields with automatic submission optionswait_for_element - Wait for dynamic elements to appear before continuingtake_screenshot - Capture screenshots of viewport, full page, or specific elementsget_current_page_info - Retrieve comprehensive page information and tab details# Clone the repository
git clone https://github.com/pyscout/webscout-mcp
cd webscout-mcp
# Install dependencies
npm install
# Install Playwright browsers for automation
npx playwright install
Add WebScout MCP to your MCP client configuration:
{
"mcpServers": {
"webscout-mcp": {
"command": "npx",
"args": ["-y", "webscout-mcp"]
}
}
}
# Start the MCP server directly
npm start
# Or run with node
node src/index.js
# Run with visible browser for debugging
node src/index.js # Set headless: false in session initialization
// Initialize session and analyze a chat interface
const session = await initializeSession("https://chat.example.com");
const analysis = await reverseEngineerChat("https://chat.example.com", "Hello", 8000);
console.log("Found endpoints:", analysis.length);
await closeSession(session.sessionId);
// Handle login and navigate to protected content
const session = await initializeSession("https://app.example.com/login");
await fillForm(session.sessionId, [
{ selector: 'input[name="email"]', value: "user@example.com" },
{ selector: 'input[name="password"]', value: "password123" }
], 'button[type="submit"]');
await waitForElement(session.sessionId, ".dashboard", 10000);
const screenshot = await takeScreenshot(session.sessionId);
await closeSession(session.sessionId);
// Monitor all network activity on a page
const session = await initializeSession("https://api.example.com");
await startNetworkCapture(session.sessionId, {
capturePostOnly: false,
captureStreaming: true,
maxCaptures: 100
});
// Perform actions that generate network traffic
await navigateToUrl(session.sessionId, "https://api.example.com/data");
const captureData = await stopNetworkCapture(session.sessionId);
console.log("Captured requests:", captureData.data.requests.length);
await closeSession(session.sessionId);
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ Chat Interface │───▶│ Browser Automation│───▶│ Network Capture │
│ (Target URL) │ │ (Playwright) │ │ (CDP + Route) │
└─────────────────┘ └──────────────────┘ └─────────────────┘
│ │ │
▼ ▼ ▼
┌─────────────────┐ ┌──────────────────┐ ┌─────────────────┐
│ Message Input │ │ DOM Interaction │ │ Request/Response│
│ Detection │ │ (Auto-fill) │ │ Analysis │
└─────────────────┘ └──────────────────┘ └─────────────────┘
│
▼
┌─────────────────┐
│ Structured Data │
│ Output (JSON) │
└─────────────────┘
The system detects multiple streaming response formats:
data: {"content": "..."}data: {"choices": [{"delta": {"content": "..."}}]}event: message data: {...}token, delta, content fieldsf:{...}, 0:"...", e:{...} patternswebscout-mcp/
├── src/
│ ├── index.js # Main MCP server implementation
│ └── tools/ # Specialized tool modules
│ ├── reverseEngineer.js # Tool exports and coordination
│ ├── reverseEngineerChat.js # Automated chat analysis
│ ├── sessionManagement.js # Browser session lifecycle
│ ├── visualInspection.js # Screenshots and page info
│ ├── interaction.js # Clicking and form filling
│ ├── navigation.js # URL navigation and tab switching
│ └── networkCapture.js # Network traffic monitoring
│ └── utilities/ # Shared utility functions
│ ├── browser.js # Browser automation utilities
│ └── network.js # Network pattern detection
├── package.json # Dependencies and scripts
├── mcp-config.json # MCP client configuration example
└── README.md # This documentation
| Variable | Description | Default |
|---|---|---|
NODE_ENV | Environment mode | development |
DEBUG | Enable debug logging | false |
Update your MCP client's configuration file:
{
"mcpServers": {
"webscout-mcp": {
"command": "npx",
"args": ["-y", "webscout-mcp"],
"env": {
"NODE_ENV": "production"
}
}
}
}
Or for VS Code MCP configuration (mcp.json):
{
"servers": {
"webscout-mcp": {
"command": "npx",
"args": ["-y", "webscout-mcp"],
"type": "stdio"
}
}
}
Interact with services that don't offer APIs
Example
Check form submissions, validate website functionality, test user flows
Automate interactions with any website, even without API
Prerequisites
Time Estimate
20-40 minutes including configuration and testing
Steps
Troubleshooting
✓ Do
✗ Don't
💡 Pro Tips
Architecture
MCP server handles HTTP requests, HTML parsing, JavaScript rendering (if headless browser), and returns structured data to Claude.
Protocols
Compatibility
✓ Use when
Use for research automation, content monitoring, data aggregation from multiple sources, and when official APIs don't exist. Best for read-only information gathering.
✗ Avoid when
Avoid for sites with APIs (use API instead), sites that explicitly forbid scraping, when data is copyrighted, or for login-required content without proper authorization.