Wopee MCP

AI-powered autonomous testing for your apps -- connect Claude, Cursor, or any MCP-compatible AI agent to Wopee.io and generate test cases, user stories, and run autonomous tests in seconds. Its 9 documented tools cover wopee, artifact, analysis, dispatch. It runs locally over stdio via the published package.

People connecting web scraping tools to Claude, Cursor, VS Code, or another MCP client. The project is written in TypeScript.

VERIFIED ACTIVE

LAST COMMIT 2026-08-20 · ★ 5 · #18 OF 78 MAINTAINED WEB SCRAPING · VERIFIED 2026-08-25

MIT · TypeScript servers · how we verify → /methodology

01 · Install Wopee MCP

before you install - you'll need

Set WOPEE_PROJECT_UUID, WOPEE_API_KEY, HTTPS_PROXY, NODE_EXTRA_CA_CERTS, NODE_TLS_REJECT_UNAUTHORIZED before connecting.

Claude Code

claude mcp add wopee-io-wopee-mcp -- npx -y wopee-mcp

Claude Desktop / Cursor / VS Code - add to config

{
  "mcpServers": {
    "wopee-io-wopee-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "wopee-mcp"
      ]
    }
  }
}

Same JSON for Cursor. For VS Code, rename the top-level key from `mcpServers` to `servers`.

Using another client? Same JSON, different key

Claude Desktop · mcpServers

Cursor · mcpServers

VS Code · servers

Windsurf · mcpServers

Zed · context_servers

Cline · mcpServers

Roo Code · mcpServers

Continue · mcpServers

LibreChat · mcpServers

Gemini CLI · mcpServers

Codex CLI · mcp_servers

Full setup guides: every client.

02 · Evidence

Security posture

What to check before giving this server access to your agent - from the registry, GitHub, and our own probes. We don't score safety; we show what's verifiable.

runs as local process (stdio) - runs on your machine with your user's permissions

license MIT - declared in the repository

npm package wopee-mcp - unscoped; check the name against the project README before installing

registry namespace io.github.Wopee-io is GitHub-verified and matches the repo owner

03 · What Wopee MCP can do

Prose above is summarized from the project's README and registry record - no invented capabilities.

What you can build

With this server connected, an agent can fetch all analysis suites for your project. This is a good starting point to see what suites are available, generate a specific file(artifact) for the selected suite, fetch the enquired file(artifact) from the selected suite, and fetch executed test cases and their results for a given analysis suite. Use this to check the status and report of dispatched agent runs.

The 9 tools it gives your agent

Extracted from the project's README - what wopee-mcp lets an agent do.

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

Limitations (from the README)

- Most tools require a suiteUuid. Always start by fetching or creating a suite. - wopee_dispatch_analysis tool will go through whole cycle of processing - crawling the application and generating all of the files(artifacts) one by one. - It is advisable to use cmd.wopee.io for a convenient visual representation of the generated data and results of the agent runs.

Latest releases

v1.30.0 · 2026-08-20

1.30.0 (2026-08-20) · dispatch:report the run handles a caller needs to track its dispatch · backlog#4382. The dispatch result told a caller its suite and analysis uuids · but not which row or which GitHub Actions run…

v1.29.1 · 2026-08-19

1.29.1 (2026-08-19) · artifact:compact tests.json before it reaches the model(005a298), closesautonomous-testing/backlog#4252api#904autonomous-testing/backlog#4252 · The api now commits the USER_STORIES artifact…

v1.29.0 · 2026-07-21

1.29.0 (2026-07-21) · add wopee_fetch_test_inventory tool for chat test counts and statuses(20514a1), closesautonomous-testing/backlog#4290autonomous-testing/backlog#4125 · Composes fetchAnalysisSuites +…

04 · Who maintains Wopee MCP

wopee-mcp is maintained by wopee-io. It's the only MCP server we track from this author; the repo dates to Sep 2025.

05 · Facts

category
web scraping - ranked #18 of 78 actively-maintained web scraping servers as of 2026-08-25.
release cadence
5 releases in the last 90 days (latest 2026-08-20)
registry
io.github.Wopee-io/wopee-mcp (active, first published 2026-03-30 · 18 versions)
packages
npm:wopee-mcp

06 · Wopee MCP FAQ

Is Wopee MCP still maintained?

Yes - as of 2026-08-25, its last commit was 2026-08-20 and it shipped 5 releases in the last 90 days. We re-verify nightly.

What can Wopee MCP do?

With this server connected, an agent can fetch all analysis suites for your project. This is a good starting point to see what suites are available, generate a specific file(artifact) for the selected suite, fetch the enquired file(artifact) from the selected suite, and fetch executed test cases and their results for a given analysis suite. Use this to check the status and report of dispatched agent runs.

How do I install Wopee MCP?

Run `npx -y wopee-mcp`. The README documents 5 environment variables (WOPEE_PROJECT_UUID, WOPEE_API_KEY, HTTPS_PROXY…) to set first. Set WOPEE_PROJECT_UUID, WOPEE_API_KEY, HTTPS_PROXY, NODE_EXTRA_CA_CERTS, NODE_TLS_REJECT_UNAUTHORIZED before connecting. You can also paste the ready-made client config above.

Does Wopee MCP run locally?

Yes - it's a stdio server: it runs on your machine (via npx) with your user's permissions. Your data stays local unless the server itself calls external APIs.

07 · Alternatives to Wopee MCP