Wopee MCP vs Pagecast — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Wopee MCP vs Pagecast
In-depth architectural comparison of the Wopee MCP and Pagecast MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Wopee MCP
Browser Automation · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Pagecast
Browser Automation · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Verdict Summary: Choose Wopee MCP if you need specialized Browser Automation tools running via a local process. Choose Pagecast if your workspace requires Browser Automation integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Wopee MCP when:
You need dedicated capabilities in the Browser Automation domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: WOPEE_PROJECT_UUID, WOPEE_API_KEY.
Autonomous testing for web apps — dispatch AI agents that open real browsers, execute test cases, and report pass/fail with screenshots. Generate user stories, test cases, and Playwright code from your app context. 8 tools for end-to-end test automation.
Record any browser page as GIF or video. AI-driven demo recording with scroll/click/hover interactions via Playwright + ffmpeg. npx @mcpware/pagecast
Category & Scope
Tools & Capabilities Breakdown
Wopee MCP Tools (9)
wopee_fetch_analysis_suites
Fetches all analysis suites for your project. This is a good starting point to see what suites are available.
wopee_dispatch_analysis
Creates and dispatches a new analysis/crawling suite for your project, or reruns an existing one. Use this to start a fresh analysis session or to re-trigger a previous analysis.
wopee_create_blank_suite
Creates a blank analysis suite for your project. Use this when you want to manually configure and populate a suite rather than having it automatically analyzed.
wopee_generate_artifact
Generates a specific file(artifact) for the selected suite.
wopee_fetch_artifact
Fetches the enquired file(artifact) from the selected suite.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Wopee MCP is categorized under Browser Automation and uses a local stdio subprocess. In contrast, Pagecast belongs to Browser Automation using local stdio subprocess. Select Wopee MCP when you need capabilities focused on browser automation and Pagecast when you require tools for browser automation.
Updates/replaces existing file(artifact) for a specific suite
wopee_dispatch_agent
Dispatches an autonomous testing agent to execute test cases for a selected suite. Tests run **asynchronously** (typically 1-3 minutes). This tool confirms dispatch and returns tracking info — not final results.
wopee_fetch_recent_executions
Fetches the most recent test case executions for the current project (up to 20, newest first). Use this to quickly check the status of recently dispatched tests without needing to remember specific suite UUIDs.
wopee_fetch_executed_test_cases
Fetches executed test cases and their results for a given analysis suite. Use this to check the status and reports of dispatched agent runs.
Pagecast Tools (9)
record_page
Open a URL, start recording. Auto-injects cursor highlight + click ripple
interact_page
scroll, click, hover, type, press keys, select, navigate, waitForSelector — all captured with bounding boxes
stop_recording
Stop and save `.webm` + `-timeline.json` (event timeline with interaction positions)
smart_export
Tooltip overlay** — magnified tooltip close-up on each interaction
cinematic_export
Cinematic crop-pan** — camera follows the action between interaction targets