Wopee

MCP server by Wopee.io

Dispatch AI testing agents and crawls for web apps on Wopee.io, and fetch test artifacts, results and status.

Runs locally (Runs on your machine: its page has the install command)Runs with npxNeeds an API key

Install Wopee

Runs on your machine. Your client starts it with this command:

npx -y wopee-mcp

Needs Node.js on your computer. The setup steps below show where the command goes in each client.

  • WOPEE_API_KEY secret Wopee.io API key for authentication
  • WOPEE_PROJECT_UUID optional UUID of the Wopee.io project to work with
  • WOPEE_API_URL optional Wopee.io API base URL (defaults to https://api.wopee.io)

Share this server

Opens this page, with the install command and setup steps.

mcp.tc/i/wopee

About

Connects an AI assistant to Wopee.io, a platform for autonomous testing of web apps. You can list analysis suites, dispatch or rerun analysis and crawling runs with extra instructions and variables, create blank suites, and fetch generated artifacts such as test cases and user stories, along with run status.

Runs locally over stdio with npx wopee-mcp and needs Node.js 18 or higher. A Wopee.io API key is required, created in the project settings at cmd.wopee.io. A project UUID can be set, and corporate proxy variables are supported.

What you can do

  • List analysis suites for a Wopee.io project
  • Dispatch a new analysis or crawling suite with custom instructions
  • Rerun an existing suite fully or crawling only
  • Pass extra environment variables to an analysis run
  • Create a blank suite for manual setup
  • Fetch test artifacts and run status

Tools

Wopee lists its tools only to clients with a key, so we can’t show them here.

Example prompts

  • Fetch all existing analysis suites for my project

  • Dispatch a new analysis suite and focus on the checkout flow

  • Rerun only the crawling phase for this suite

  • Create a blank analysis suite for my project

Set up

Every client starts Wopee on your machine with the same command. Pick yours; the page remembers your choice.

Claude Code

  1. Run this in a terminal, in your project folder:
claude mcp add --transport stdio wopee --env "WOPEE_API_KEY=<YOUR_WOPEE_API_KEY>" -- npx -y wopee-mcp
  1. Start Claude Code and type /mcp. wopee should show as connected.

Add --scope user to make it available in every project. Replace the placeholders with your own values.

Claude Desktop

  1. Open Settings → Developer → Edit Config. It opens claude_desktop_config.json. Add:
claude_desktop_config.json
{
  "mcpServers": {
    "wopee": {
      "command": "npx",
      "args": [
        "-y",
        "wopee-mcp"
      ],
      "env": {
        "WOPEE_API_KEY": "<YOUR_WOPEE_API_KEY>"
      }
    }
  }
}
  1. Save the file and restart Claude Desktop. Replace the placeholders with your own values.

Needs Node.js on your computer. The file lives in ~/Library/Application Support/Claude/ on macOS and %APPDATA%\Claude\ on Windows.

Cursor

Or add it by hand to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (this project):

mcp.json
{
  "mcpServers": {
    "wopee": {
      "command": "npx",
      "args": [
        "-y",
        "wopee-mcp"
      ],
      "env": {
        "WOPEE_API_KEY": "<YOUR_WOPEE_API_KEY>"
      }
    }
  }
}

Needs Node.js on your computer. Replace the placeholders with your own values.

VS Code

Add it to .vscode/mcp.json. VS Code asks for the secret the first time and stores it securely:

.vscode/mcp.json
{
  "servers": {
    "wopee": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "wopee-mcp"
      ],
      "env": {
        "WOPEE_API_KEY": "${input:wopee-api-key}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "wopee-api-key",
      "description": "WOPEE_API_KEY",
      "password": true
    }
  ]
}

Needs Node.js on your computer.

Devin Desktop

  1. Add it to ~/.config/devin/mcp_config.json (macOS and Linux) or %APPDATA%\devin\mcp_config.json (Windows):
mcp_config.json
{
  "mcpServers": {
    "wopee": {
      "command": "npx",
      "args": [
        "-y",
        "wopee-mcp"
      ],
      "env": {
        "WOPEE_API_KEY": "<YOUR_WOPEE_API_KEY>"
      }
    }
  }
}
  1. Refresh the MCP server list in Cascade. Replace the placeholders with your own values.

Devin Desktop is the new name for Windsurf.

Codex

codex mcp add wopee --env "WOPEE_API_KEY=<YOUR_WOPEE_API_KEY>" -- npx -y wopee-mcp

Or edit ~/.codex/config.toml directly:

config.toml
[mcp_servers.wopee]
command = "npx"
args = ["-y", "wopee-mcp"]
env = { WOPEE_API_KEY = "<YOUR_WOPEE_API_KEY>" }

Needs Node.js on your computer. Replace the placeholders with your own values.

Gemini CLI

gemini mcp add -e "WOPEE_API_KEY=<YOUR_WOPEE_API_KEY>" wopee npx -- -y wopee-mcp

This adds it to the current project. Add -s user to use it everywhere.

Any client

Most clients that start local servers accept this shape:

{
  "mcpServers": {
    "wopee": {
      "command": "npx",
      "args": [
        "-y",
        "wopee-mcp"
      ],
      "env": {
        "WOPEE_API_KEY": "<YOUR_WOPEE_API_KEY>"
      }
    }
  }
}

Zed puts servers under context_servers in its settings, with the same command, args and env fields.

Needs Node.js on your computer. Replace the placeholders with your own values.

Embed

Show Wopee in a README or on your site. Each embed links to this page, uses the server’s own install command, and sets no cookies. How embeds work

The card, the iframe and the JSON are in English. Add ?lang=it, fr, de or es to their address for another language.

README badge

Badge preview, lightBadge preview, dark
Markdown
[![Wopee on mcp.tc](https://mcp.tc/i/wopee/badge.svg)](https://mcp.tc/i/wopee)
HTML
<a href="https://mcp.tc/i/wopee"><img src="https://mcp.tc/i/wopee/badge.svg" alt="Wopee on mcp.tc" height="20"></a>

It follows the reader’s light or dark mode. Add ?theme=light or ?theme=dark to fix it, or ?style=compact to show the mark without the word.

Website card

HTML
<script src="https://mcp.tc/w/wopee.js" async></script>

The card appears where the tag is. Add data-theme="dark" or data-size="compact" to the tag to change it. The file holds everything it needs, so it makes no other requests and sets no cookies.

iframe

HTML
<iframe src="https://mcp.tc/embed/wopee" title="Wopee on mcp.tc" width="420" height="200" loading="lazy" allow="clipboard-write" style="border:0;border-radius:8px;max-width:100%"></iframe>

Use it on pages that don’t allow scripts. Add ?theme=light or ?theme=dark to the address to fix the colors.

JSON

The listing as data for your own pages and tools: name, tagline, install command, tools and the “Add to” links. Any site can read it (CORS is open).

https://mcp.tc/i/wopee.json

What each field means

AI prompt

Paste this into an AI coding assistant, such as Claude Code or Cursor, and it adds the Wopee card to your site.

Markdown
Add the mcp.tc card for Wopee, an MCP server, to my website. It is one static script: no build step, no package to install, no cookies.

Put this tag where the card should appear. The card renders right before it:

```html
<script src="https://mcp.tc/w/wopee.js" async></script>
```

To show the card somewhere else, put this placeholder there and load the same script once, for example before `</body>`. Keep the link inside: visitors without JavaScript see it.

```html
<div data-mcptc="wopee"><a href="https://mcp.tc/i/wopee">Wopee on mcp.tc</a></div>
```

Options:
- `data-theme="light"` or `"dark"` on the tag or the placeholder fixes the colors. Without it, the card follows the visitor’s light or dark mode.
- `data-size="compact"` gives a smaller card without the tagline.
- The CSS variable `--mcptc-max-width` on the placeholder or a parent sets the width (default `520px`).
- `?lang=` on the script URL sets the card’s language: `en`, `it`, `fr`, `de` or `es`.

If the site has a Content Security Policy, allow `script-src https://mcp.tc` and `img-src data:` (the icon is inline).

For a README or other Markdown docs, use the badge instead:

```markdown
[![Wopee on mcp.tc](https://mcp.tc/i/wopee/badge.svg)](https://mcp.tc/i/wopee)
```

Reference: https://mcp.tc/embed

Change history

This server runs on your computer, so we follow its npm package: each new version shows up here, with edits by its owner.

Follow Wopee and we’ll email you when something changes.

  1. , Automatic check

    Tracking started: version 1.30.2.

FAQ

Can I paste mcp.tc/i/wopee into my MCP client?

No. Wopee runs on your own computer, started by your client, so it has no web address to connect to. The quick link is the page to share; the install command is npx -y wopee-mcp.

Does Wopee need an API key?

Yes. It reads WOPEE_API_KEY from its environment, and WOPEE_API_KEY is a secret. Put the value in your client’s config on your own machine, never in a shared file.

Is Wopee a remote or a local server?

Local. Your client starts it as a process on your computer with npx -y wopee-mcp, which needs Node.js.

What can Wopee do?

You can list analysis suites for a Wopee.io project, dispatch a new analysis or crawling suite with custom instructions and rerun an existing suite fully or crawling only.

Which clients can use it?

Any client that starts local servers: Claude Code, Claude Desktop, Cursor, VS Code, Devin Desktop, Codex, Gemini CLI, Zed and others. claude.ai and ChatGPT only connect to remote servers.

Does mcp.tc track changes to Wopee?

Partly. It runs on your computer, so we follow its npm package: its History tab shows each new version and edits by its owner. Follow the listing to get an email when it changes.

Who wrote this page?

mcp.tc’s robot read Wopee’s public metadata (its package and repository pages), and an AI model drafted the text from it. A person reviews anything the checks can’t confirm. The text can still be wrong, so if you spot a mistake, use Report this listing on this page.

mcp.tc isn’t affiliated with Wopee.io. This page was built from Wopee’s public metadata, last checked on 5 Oct 2026, and an AI model wrote the description, so it can be wrong. Names and marks belong to their owners. Something off? Report this listing.