MCP.Market

Devicecloud MCP server

by RubenGlez·io.github.RubenGlez/devicecloud·v0.3.2
No reviews yet

Triage failing DeviceCloud Maestro test runs: fail reasons, screenshots, flaky-flow analytics

B78/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars27 downloads/wk

Reviews

Write one

Nobody has reviewed Devicecloud yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Devicecloud tools (10, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • diagnose_runwrite action

    Triage one DeviceCloud run in a single call. Resolves the upload, folds retries per flow, and returns the failed flows with fail reasons, durations, and failure-screenshot paths (auto-downloaded from the HTML report), plus a passed/failed/flaky summary and suggested next steps. The highest-signal tool for debugging a red CI run — use this first, then read the screenshots and fix the flow or app co

  • download_artifacts

    Download raw run artifacts (logs, screenshots, videos) as a ZIP. Use when the HTML report doesn't contain enough detail (e.g. need full logcat, video recording, or non-failure screenshots).

  • get_flow_runs

    List individual runs for a specific Maestro flow file. Returns id, status, createdAt, durationSeconds, failReason, testUploadId, uploadName per run. Use to drill into the history of one flow — e.g. after list_flow_analytics surfaces a flaky or broken flow.

  • get_html_report

    Download AND auto-unzip the HTML report (HTML + screenshots + logs) for an upload. Returns the local extraction directory and an inventory of files, with failure screenshots highlighted at the top — those are typically the highest-signal artifact for debugging.

  • get_junit_report

    Fetch the JUnit XML report for an upload. Returns raw XML.

  • get_results

    List individual flow results for an upload. Each result includes id, test_file_name, status, fail_reason, duration_seconds, retry_of. Optional client-side status filter.

  • get_upload_statuswrite action

    Get status summary for one upload. Returns overall status plus per-test name, status, durationSeconds, failReason. Provide either uploadId or name (most recent matching name wins).

  • list_flow_analytics

    Aggregated pass-rate and run-count analytics per Maestro flow file over a lookback window. Use to identify flaky flows (low pass_rate but many passed_runs) vs. genuinely broken flows. Returns flow_name, file_name, pass_rate, passed_runs, failed_runs, total_runs, avg_duration, last_run_at, tags, daily_data per flow.

  • list_uploads

    List Maestro uploads from DeviceCloud. Filter by name (supports * wildcard), date range, and pagination. Returns id, name, created_at, consoleUrl per upload.

  • suite_health

    Classify every Maestro flow over a lookback window into healthy, flaky, broken, or regression, ranked worst-first, so you can tell whether a failure is worth fixing before diving in. Regressions (a flow that was passing and recently started failing) are surfaced first, since a recent change likely broke them. Use this to prioritize, then diagnose_run to fix a specific run. Filters mirror list_flow

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 61 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Devicecloud compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 48,255 servers
Tools
10
the typical server has 7
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
27
more than 14% of 12,191 servers with a package

What its tools let an agent do: 8 read · 2 change

Install Devicecloud in Claude Code, Cursor or VS Code

Runs npx -y devicecloud-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add devicecloud -- npx -y devicecloud-mcp
Add to Cursor

What the publisher says

From the Devicecloud repository's README, as published. We do not edit it. Read it on GitHub

devicecloud-mcp

Triage failing DeviceCloud runs so your agent can fix them, without opening the dashboard.

When a DeviceCloud run goes red in CI, the reason why is buried in the web dashboard: the fail reason, the failure screenshot, the logs. This server pulls all of it straight into your editor, so your AI assistant (Claude Code, Cursor, Claude Desktop, etc.) can read the evidence, find the root cause, and fix the flow or app code. You commit, CI re-runs, and the dashboard stays closed.

DeviceCloud is a platform for running Maestro flows on real devices. Your CI triggers the runs; this server is how you debug the ones that fail.

It lets the assistant:

  • diagnose a run in one call: failed flows, fail reasons, failure-screenshot paths, and a passed/failed/flaky summary, ready to act on
  • rank suite health: classify every flow as healthy, flaky, broken, or regression over a window so you know what's worth fixing first
  • list recent uploads, filter by name (commit message + short SHA) or date
  • read per-flow status and failReason for any upload
  • pull the JUnit XML report
  • download and auto-unzip the HTML report (with failure screenshots highlighted)
  • download raw artifacts (logs, screenshots, video) as a zip
  • spot flaky vs genuinely-broken flows with per-flow pass-rate analytics
  • drill into run history for a specific flow file

The server is read-only against the DeviceCloud REST API: no dcd CLI dependency, and nothing an agent does can trigger billable runs. Triggering and re-running tests stay with your CI; cancelling a run stays in the dashboard.

Install

Requires Node.js 22+ — check with node --version. There's no separate install step; the server runs on demand via npx.

Add this to your MCP client config:

{
  "mcpServers": {
    "devicecloud": {
      "command": "npx",
      "args": ["-y", "devicecloud-mcp"],
      "env": {
        "DEVICE_CLOUD_API_KEY": "<your-key>"
      }
    }
  }
}

Get your API key at console.devicecloud.dev/settings.

Claude Code: add it with one command

Skip editing JSON — register the server in one step:

claude mcp add devicecloud --env DEVICE_CLOUD_API_KEY=<your-key> -- npx -y devicecloud-mcp

Add -s user to make it available in every project instead of only the current one.

Configure your assistant

The config block above is the same for every client; only the file location differs.

Claude Code (project-scoped, .mcp.json)

Add to a .mcp.json at the root of any project where you want the tools available:

{
  "mcpServers": {
    "devicecloud": {
      "command": "npx",
      "args": ["-y", "devicecloud-mcp"],
      "env": {
        "DEVICE_CLOUD_API_KEY": "${DEVICE_CLOUD_API_KEY}"
      }
    }
  }
}

Then export the key from your shell profile so Claude Code's child process inherits it:

# ~/.zshrc or ~/.bashrc
export DEVICE_CLOUD_API_KEY="<your-key>"

Setting it only in an interactive shell isn't enough; Claude Code spawns the MCP from its own environment, so the variable needs to be in the profile.

Claude Code (user-scoped, ~/.claude.json)

If you want it available everywhere instead of per-project, add the same devicecloud block under mcpServers in ~/.claude.json.

Claude Desktop

Edit ~/Library/Application Support/Claude/claudedesktopconfig.json (macOS) or %APPDATA%\Claude\claudedesktopconfig.json (Windows). Restart Claude Desktop after saving; a tools icon appears in the chat input once the server connects.

Cursor

Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json at the project root (project-scoped).

Windsurf

Edit ~/.codeium/windsurf/mcp_config.json.

Other MCP-compatible clients

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Devicecloud: common questions

Is Devicecloud MCP server safe?
Mostly: it is graded B (78/100). Read the Devicecloud safety report
How do I install Devicecloud?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Devicecloud need an API key?
Yes. The registry entry asks for DEVICE_CLOUD_API_KEY.
Is Devicecloud maintained?
The last commit was 102 days ago (2026-07-25). The latest release is v0.3.2.
What can I use instead of Devicecloud?
Servers from other publishers that do the same job: Qase Test Management MCP server.
How does Devicecloud compare with other MCP servers?
safety score 78/100 (higher than 57% of 48,255 servers); tools 10 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Devicecloud

Same job from other publishers: the closest match first, then the best rated.

  • Qase Test Management
    Official MCP server for Qase — manage test cases, runs, suites, defects via AI tools.
    A