# Add the Wopee.io MCP server to Google Antigravity and Gemini CLI

Connect Google Antigravity or Gemini CLI to your Wopee.io project, so the agent can generate tests, run them with Wopee.io's testing agent and read the verdicts. What the server does: [Wopee.io MCP server](<https://docs.wopee.io/guides/wopee-mcp/index.md>).

Before you start: Node.js 20.18 or newer, and `WOPEE_API_KEY` and `WOPEE_PROJECT_UUID` from **More** › **Settings** › **API Keys** in your project ([how](<https://docs.wopee.io/guides/api-keys/index.md>)).

> [!TIP]
>
> **Let your agent do the setup**
>
> ```text
> Set me up for Wopee.io: follow https://wopee.io/agent-setup/prompt.md, show me the plan first, and ask before changing anything.
> ```
>
> It shows a plan, runs `npx -y @wopee-io/init` after your yes, and you approve in Commander, so your API key never reaches the chat. [What the agent does](<https://docs.wopee.io/agent-setup/index.md>). Rather do it by hand? Follow the steps below.

## Google Antigravity

The Antigravity app, IDE and CLI read the same `mcp_config.json`.

### Antigravity MCP config file location

| Scope | File |
| --- | --- |
| Global | `~/.gemini/config/mcp_config.json` |
| Workspace | `.agents/mcp_config.json` in the workspace |

### Add to mcp\_config.json

```json title="~/.gemini/config/mcp_config.json"
{
  "mcpServers": {
    "wopee": {
      "command": "npx",
      "args": ["-y", "wopee-mcp"],
      "env": {
        "WOPEE_API_KEY": "your-api-key",
        "WOPEE_PROJECT_UUID": "your-project-uuid"
      }
    }
  }
}
```

### Pass your Wopee.io API key securely

Put the entry with the key in the global file, which stays in your home folder. If you use the workspace file `.agents/mcp_config.json` with a real key, add it to `.gitignore`.

### Verify in Antigravity

- CLI: `/mcp`
- IDE: the **...** menu › **MCP Servers** › **Manage** › **View raw config**
- App: **Settings** › **Customizations**

## Gemini CLI

### Add with the Gemini CLI

```shell
gemini mcp add -s user -e 'WOPEE_API_KEY=${WOPEE_API_KEY}' -e 'WOPEE_PROJECT_UUID=${WOPEE_PROJECT_UUID}' wopee npx -y wopee-mcp
```

### Gemini CLI MCP config file location

| Scope | File |
| --- | --- |
| User | `~/.gemini/settings.json` |
| Project | `.gemini/settings.json` in the project |

```json title="~/.gemini/settings.json"
{
  "mcpServers": {
    "wopee": {
      "command": "npx",
      "args": ["-y", "wopee-mcp"],
      "env": {
        "WOPEE_API_KEY": "${WOPEE_API_KEY}",
        "WOPEE_PROJECT_UUID": "${WOPEE_PROJECT_UUID}"
      },
      "timeout": 300000
    }
  }
}
```

### Pass your Wopee.io API key securely

Gemini CLI replaces `$VAR` and `${VAR}` in `env` with values from its environment. Export `WOPEE_API_KEY` and `WOPEE_PROJECT_UUID` before you start `gemini`.

### Verify in Gemini CLI

Run `gemini mcp list`, or `/mcp` in a session. In a folder you have not trusted, local servers stay disconnected until you run `gemini trust`.

## First prompt to try

```text
How many tests do I have in Wopee.io, and which ones have never run?
```

The agent calls `wopee_fetch_test_inventory` and lists the analyses and test cases in your project with their latest status. More prompts: [Prompt library](<https://docs.wopee.io/guides/wopee-mcp/#prompt-library>).

## Troubleshooting

| Problem | Fix |
| --- | --- |
| Gemini CLI: the server stays disconnected | Trust the folder with `gemini trust` |
| `[AUTH_ERROR] WOPEE_API_KEY or WOPEE_AUTH_TOKEN must be set` | The key is missing in `env`, or the variable was not exported before start |
| Generation calls time out | Raise `timeout` (milliseconds) in the server entry; generations can take up to 5 minutes |

All error messages and their fixes: [Troubleshooting](<https://docs.wopee.io/guides/wopee-mcp/troubleshooting/index.md>).

## FAQ

### Where is the Antigravity MCP config file?

`~/.gemini/config/mcp_config.json` for all workspaces, and `.agents/mcp_config.json` in a workspace.

### Where is the Gemini CLI MCP config file?

`~/.gemini/settings.json` for the user, and `.gemini/settings.json` in a project.
