# devicecloud MCP server

> Triage failing Maestro test runs by pulling failure reasons, screenshots, and logs directly into your AI assistant for automated debugging.

- Repository: https://github.com/RubenGlez/devicecloud-mcp
- Page: https://hostedmcp.org/servers/rubenglez/devicecloud-mcp
- Transport: stdio
- Stars: 0
- License: MIT
- Latest version: 0.3.3

## Install

### Claude Code

```sh
claude mcp add --env 'DEVICE_CLOUD_API_KEY=<YOUR_DEVICE_CLOUD_API_KEY>' devicecloud-mcp -- npx -y devicecloud-mcp
```

### Cursor (`~/.cursor/mcp.json`)

```json
{
  "mcpServers": {
    "devicecloud-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "devicecloud-mcp"
      ],
      "env": {
        "DEVICE_CLOUD_API_KEY": "<YOUR_DEVICE_CLOUD_API_KEY>"
      }
    }
  }
}
```

### VS Code (`.vscode/mcp.json`)

```json
{
  "servers": {
    "devicecloud-mcp": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "devicecloud-mcp"
      ],
      "env": {
        "DEVICE_CLOUD_API_KEY": "<YOUR_DEVICE_CLOUD_API_KEY>"
      }
    }
  }
}
```

### VS Code CLI

```sh
code --add-mcp '{"name":"devicecloud-mcp","type":"stdio","command":"npx","args":["-y","devicecloud-mcp"],"env":{"DEVICE_CLOUD_API_KEY":"<YOUR_DEVICE_CLOUD_API_KEY>"}}'
```

### Claude Desktop (`claude_desktop_config.json`)

```json
{
  "mcpServers": {
    "devicecloud-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "devicecloud-mcp"
      ],
      "env": {
        "DEVICE_CLOUD_API_KEY": "<YOUR_DEVICE_CLOUD_API_KEY>"
      }
    }
  }
}
```

### Codex

```sh
codex mcp add devicecloud-mcp --env 'DEVICE_CLOUD_API_KEY=<YOUR_DEVICE_CLOUD_API_KEY>' -- npx -y devicecloud-mcp
```

### Codex config.toml (`~/.codex/config.toml`)

```toml
[mcp_servers.devicecloud-mcp]
command = "npx"
args = ["-y", "devicecloud-mcp"]

[mcp_servers.devicecloud-mcp.env]
DEVICE_CLOUD_API_KEY = "<YOUR_DEVICE_CLOUD_API_KEY>"
```

### Gemini CLI

```sh
gemini mcp add -s user -e 'DEVICE_CLOUD_API_KEY=<YOUR_DEVICE_CLOUD_API_KEY>' devicecloud-mcp npx -- -y devicecloud-mcp
```

### Gemini settings.json (`~/.gemini/settings.json`)

```json
{
  "mcpServers": {
    "devicecloud-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "devicecloud-mcp"
      ],
      "env": {
        "DEVICE_CLOUD_API_KEY": "<YOUR_DEVICE_CLOUD_API_KEY>"
      }
    }
  }
}
```

## Environment variables

| Name | Required | Secret | Description |
|---|---|---|---|
| `DEVICE_CLOUD_API_KEY` | yes | yes | DeviceCloud API key — generate one at console.devicecloud.dev/settings |

## Tools (10)

- `diagnose_run`
- `suite_health`
- `list_uploads`
- `get_upload_status`
- `get_results`
- `get_junit_report`
- `get_html_report`
- `download_artifacts`
- `list_flow_analytics`
- `get_flow_runs`

## FAQ

### Can this server trigger new test runs?

No, the server is read-only. Triggering and re-running tests must be handled through your CI or the DeviceCloud dashboard.

### How do I install the server?

The server runs on demand via npx and requires Node.js 22 or higher.

### What information can the assistant retrieve from a failed run?

The assistant can access failure reasons, failure screenshot paths, JUnit XML reports, and raw artifacts like logs and video.

### How can I distinguish between flaky tests and broken ones?

You can use the suite health and flow analytics tools to classify flows as healthy, flaky, broken, or regression based on pass-rate analytics.
