Server data from the Official MCP Registry
MCP server for DeviceCloud — query Maestro test uploads, results, analytics, and artifacts.
MCP server for DeviceCloud — query Maestro test uploads, results, analytics, and artifacts.
Valid MCP server (2 strong, 4 medium validity signals). No known CVEs in dependencies. Package registry verified. Imported from the Official MCP Registry.
5 files analyzed · 1 issue found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
This plugin requests these system permissions. Most are normal for its category.
Set these up before or after installing:
Environment variable: DEVICE_CLOUD_API_KEY
Add this to your MCP configuration file:
{
"mcpServers": {
"io-github-rubenglez-devicecloud": {
"env": {
"DEVICE_CLOUD_API_KEY": "your-device-cloud-api-key-here"
},
"args": [
"-y",
"devicecloud-mcp"
],
"command": "npx"
}
}
}From the project's GitHub README.
A small MCP server that exposes DeviceCloud as tools that any MCP-aware assistant — Claude Code, Cursor, Claude Desktop, etc. — can call directly. DeviceCloud is a platform for running Maestro flows on real devices.
It lets the assistant:
failReason for any uploadThe server is read-only against the DeviceCloud API.
nvm install 24 && nvm use 24, or nvm use if you already have itnpm i -g pnpm or corepack enable pnpmgit clone https://github.com/RubenGlez/devicecloud-mcp
cd devicecloud-mcp
nvm use # picks up .nvmrc (Node 24)
pnpm install # also runs the build — dist/ is created automatically
If you just want to use the server without cloning the repo, point your client at npx:
{
"mcpServers": {
"devicecloud": {
"command": "npx",
"args": ["-y", "devicecloud-mcp"],
"env": {
"DEVICE_CLOUD_API_KEY": "<your-key>"
}
}
}
}
This works for Claude Code (.mcp.json), Claude Desktop, Cursor, and Windsurf — wherever you put the config, npx fetches and runs the latest published version automatically.
Pick the section that matches your tool. In every case you need to:
DEVICE_CLOUD_API_KEY through to the spawned process.Replace /ABSOLUTE/PATH/TO/devicecloud-mcp with wherever you put this folder.
.mcp.json)Add this entry to a .mcp.json at the root of any project where you want the tools available:
{
"mcpServers": {
"devicecloud": {
"command": "node",
"args": ["/ABSOLUTE/PATH/TO/devicecloud-mcp/dist/index.js"],
"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.json)If you want it available everywhere instead of per-project, add the same devicecloud block under mcpServers in ~/.claude.json.
Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):
{
"mcpServers": {
"devicecloud": {
"command": "node",
"args": ["/ABSOLUTE/PATH/TO/devicecloud-mcp/dist/index.js"],
"env": {
"DEVICE_CLOUD_API_KEY": "<your-key>"
}
}
}
}
Restart Claude Desktop after saving. A tools icon appears in the chat input once the server connects.
Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json at the project root (project-scoped):
{
"mcpServers": {
"devicecloud": {
"command": "node",
"args": ["/ABSOLUTE/PATH/TO/devicecloud-mcp/dist/index.js"],
"env": {
"DEVICE_CLOUD_API_KEY": "<your-key>"
}
}
}
}
Edit ~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"devicecloud": {
"command": "node",
"args": ["/ABSOLUTE/PATH/TO/devicecloud-mcp/dist/index.js"],
"env": {
"DEVICE_CLOUD_API_KEY": "<your-key>"
}
}
}
}
Any client that supports stdio MCP servers uses the same { command, args, env } shape. Consult the client's docs for the config file location.
Note: OpenAI products (ChatGPT, Codex, the Assistants API) use their own tool protocol and do not support MCP servers.
After restarting your assistant:
List recent DeviceCloud uploads, limit 3.
You should see a JSON-shaped response with an uploads array. If instead you get DEVICE_CLOUD_API_KEY env var is required, the variable isn't reaching the spawned process — re-check that it's exported from your shell profile (not just the current shell).
| Tool | Purpose |
|---|---|
list_uploads | List recent uploads. Filter by name (* wildcard), from, to, limit, offset. |
get_upload_status | Overall status + per-test status, duration, failReason. Provide uploadId or name. |
get_results | Per-flow rows for one upload: id, test_file_name, status, fail_reason, duration_seconds, retry_of. Optional client-side status filter. |
get_junit_report | Raw JUnit XML for an upload. |
get_html_report | Downloads + auto-unzips the HTML report. Returns the extraction dir and an inventory with failureScreenshots[] highlighted (these are the highest-signal debugging artifact). |
download_artifacts | Zip of raw artifacts (logs, screenshots, video). results: "FAILED" (default) or "ALL". Saves to /tmp by default; not auto-unzipped. |
list_flow_analytics | Per-flow pass rate, run counts, avg duration over a lookback window (default 14 days). Useful to tell flakes from genuinely-broken flows. |
get_flow_runs | Individual run history for one flow file (fileName required). Returns status, duration, failReason, and the uploadId each run belongs to. Use to drill into a specific flow after list_flow_analytics. |
Uploads are typically named after the commit or build that triggered them. A common convention is to include the short SHA:
fix(login): handle expired session (a1b2c3d4)
Filter with name = "*a1b2c3d4*" to find every upload for a specific commit. The wildcard is *, not %.
DeviceCloud uploads are created when you trigger a run — via the CLI, a CI step, the GitHub Action, or the API directly. Whether a given commit has an upload depends entirely on your CI setup. If list_uploads returns nothing for a SHA you expect, the run probably wasn't triggered for that commit.
DEVICE_CLOUD_API_KEY env var is required — the variable isn't visible to the spawned MCP. Export it from ~/.zshrc / ~/.bashrc, restart your assistant.unzip failed (from get_html_report) — the unzip binary is missing or crashed. Install with brew install unzip (macOS ships with it; Linux usually does too).list_uploads for your SHA — a run probably wasn't triggered for that commit. See "When uploads do and don't exist" above.devicecloud-mcp/
├── src/
│ ├── index.ts # server entry point
│ ├── utils.ts # pure functions (stripCRLF, filterResults)
│ └── index.test.ts # unit tests
├── dist/ # compiled output (built by pnpm install)
├── .github/workflows/
│ └── ci.yml # type-check, build, test on every push
├── package.json
├── tsconfig.json
├── pnpm-lock.yaml
├── .nvmrc
├── .npmrc
├── pnpm-workspace.yaml
├── LICENSE
├── .gitignore
└── README.md
pnpm install compiles src/ to dist/ automatically via the prepare script. The repo uses pnpm — pnpm-lock.yaml is the lockfile.
Be the first to review this server!
by Modelcontextprotocol · Developer Tools
Web content fetching and conversion for efficient LLM usage
by Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
by Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.