
Devicecloud
Connects Claude to DeviceCloud's test infrastructure API so you can query Maestro mobile test runs without leaving your editor. You get read-only access to recent uploads, per-flow pass/fail status, JUnit XML reports, HTML reports with failure screenshots, raw artifacts (logs, video), and analytics like pass rate trends over a lookback window. Useful when debugging flaky tests or triaging CI failures. The assistant can filter uploads by commit SHA, drill into specific flow files to see run history, and pull the exact screenshot where a test broke. Requires a DeviceCloud API key from your account settings. Works with any stdio-capable MCP client.
- tools
- 10
- auth
- Secret needed
- transport
- STDIO
- env var
- 1
- last updated
- Nov 7, 2026
Tools
10 toolsPublic tool metadata for what this MCP can expose to an agent.
diagnose_runOne-call triage of a run (uploadId or name): folds retries per flow and returns failed flows with fail reasons, durations, and auto-downloaded failure-screenshot paths, plus a passed/failed/flaky summary and suggested next steps.
One-call triage of a run (uploadId or name): folds retries per flow and returns failed flows with fail reasons, durations, and auto-downloaded failure-screenshot paths, plus a passed/failed/flaky summary and suggested next steps.
No parameter schema in public metadata yet.
suite_healthClassify every 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.
Classify every 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.
No parameter schema in public metadata yet.
list_uploadsList recent uploads. Filter by name (* wildcard), from, to, limit, offset.
List recent uploads. Filter by name (* wildcard), from, to, limit, offset.
No parameter schema in public metadata yet.
get_upload_statusOverall status + per-test status, duration, failReason. Provide uploadId or name.
Overall status + per-test status, duration, failReason. Provide uploadId or name.
No parameter schema in public metadata yet.
get_resultsPer-flow rows for one upload: id, test_file_name, status, fail_reason, duration_seconds, retry_of. Optional client-side status filter.
Per-flow rows for one upload: id, test_file_name, status, fail_reason, duration_seconds, retry_of. Optional client-side status filter.
No parameter schema in public metadata yet.
get_junit_reportRaw JUnit XML for an upload.
Raw JUnit XML for an upload.
No parameter schema in public metadata yet.
get_html_reportDownloads and auto-unzips the HTML report. Returns the extraction dir and an inventory with failureScreenshots[] highlighted.
Downloads and auto-unzips the HTML report. Returns the extraction dir and an inventory with failureScreenshots[] highlighted.
No parameter schema in public metadata yet.
download_artifactsZip of raw artifacts (logs, screenshots, video). results: FAILED (default) or ALL. Saves to /tmp by default; not auto-unzipped.
Zip of raw artifacts (logs, screenshots, video). results: FAILED (default) or ALL. Saves to /tmp by default; not auto-unzipped.
No parameter schema in public metadata yet.
list_flow_analyticsPer-flow pass rate, run counts, avg duration over a lookback window (default 14 days).
Per-flow pass rate, run counts, avg duration over a lookback window (default 14 days).
No parameter schema in public metadata yet.
get_flow_runsIndividual run history for one flow file (fileName required). Returns status, duration, failReason, and the uploadId each run belongs to.
Individual run history for one flow file (fileName required). Returns status, duration, failReason, and the uploadId each run belongs to.
No parameter schema in public metadata yet.
Sponsors
Configuration
DEVICE_CLOUD_API_KEY*secretDeviceCloud API key — generate one at console.devicecloud.dev/settings
Readme
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:
Details
- Repository
- github.com/rubenglez/devicecloud-mcp
- Category
- Monitoring & Observability
- Package
devicecloud-mcp- Transport
- STDIO
- Auth
- Required
- Registry
- MCP registry, active