{"id":"com.appelium/mcp","slug":"com-appelium-mcp","title":"Appelium","description":"Investigate iOS and Android crashes and failed UI tests from your coding agent.","version":"1.0.1","publisher":{"kind":"domain","id":"appelium.com","label":"appelium.com","url":"https://appelium.com"},"website":"https://developer.appelium.com/documentation/api/mcp/","repository":"","remotes":[{"type":"streamable-http","url":"https://api.appelium.com/v1/mcp","headers":[{"description":"Personal Appelium API key","isRequired":true,"isSecret":true,"name":"X-Appelium-Token"}]}],"packages":[],"published":"2026-11-17","updated":"2026-11-17","status":"online","auth":"","latency_ms":1182,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"list_applications","title":"","description":"List all applications registered in the workspace. Returns the id, name, slug, platform, and current release version for each application. Use the returned `id` or `slug` to scope other tool calls to a specific application.","read_only":true},{"name":"get_top_crash_groups","title":"","description":"Return the top crash groups for a specific application, ranked by total crash occurrences in the requested look-back window. Supports optional filtering to a single application version so agents can answer questions like: \"top 10 crash groups affecting app version 3.4.1\". Agents should call list_applications first to resolve the target application id.","read_only":true},{"name":"get_crash_group","title":"","description":"Fetch a crash group together with its latest symbolicated call stack. Identify the crash group by global numeric `id` (from a previous get_crash_group result) or by the workspace-scoped `serialNumber` shown in the dashboard URL. Recommended: pass `applicationId` whenever it is known so the returned call stack is scoped to the latest crash report of that application, since a crash group is workspac","read_only":true},{"name":"get_crash_group_stats","title":"","description":"Return occurrence statistics for a crash group: total crash count, number of distinct affected devices, and the date range of recorded crashes within the requested look-back window. Identify the crash group by global `id` or workspace-scoped `serialNumber`.","read_only":true},{"name":"resolve_crash_report_url","title":"","description":"Resolve a Dashboard crash-report URL or path into `crashGroupId` and `crashReportId`.\nSupports both application-level and workspace-level routes:\n/{workspaceSlug}/apps/{applicationSlug}/crash-groups/{crashGroupSerialNumber}/crash-reports/{crashReportSerialNumber}\n/{workspaceSlug}/crashes/{crashGroupSerialNumber}/crash-reports/{crashReportSerialNumber}\nUse this first when you start from a Dashboard","read_only":true},{"name":"get_crash_report_details","title":"","description":"Fetch full metadata for a single crash report and its symbolicated call stack. Returns the\nreport details (device, OS, app version, locale, userIdentifier, exceptionMessage,\nreport/attachment/activity-log file metadata), whether activity logs are attached, and any\nlinked `testExecutionId` / `testRunId`. Use this after\nresolve_crash_report_url when you start from a Dashboard crash-report URL.","read_only":true},{"name":"list_crash_reports","title":"","description":"List recent crash report occurrences for a crash group, sorted by crash date descending. Returns per-occurrence details: id, serialNumber, crashDate, appVersion, deviceModel, osVersion, exceptionMessage, userIdentifier, and whether activity logs are available. Pass the returned `id` to get_crash_report_logs to fetch the captured activity log lines.","read_only":true},{"name":"get_crash_report_logs","title":"","description":"Return the activity logs captured before a specific crash report: console prints, app lifecycle events, memory warnings, and network requests/responses. Logs are returned in chronological order, truncated to the 200 entries closest to the crash when the total exceeds that limit. Use list_crash_reports to obtain a crash report `id`, and check the `hasActivityLogs` field to confirm logs are availabl","read_only":true},{"name":"resolve_test_execution_url","title":"","description":"Resolve a Dashboard test-execution URL or path of the form\n/{workspaceSlug}/apps/{applicationSlug}/test-executions/{testExecutionSerialNumber}\ninto the `applicationId` and `testExecutionId` used by downstream test-execution tools.\nUse this first when you start from a Dashboard test-execution URL, then call\nget_test_execution_failure_groups or\nget_test_execution_run_summaries with the returned `tes","read_only":true},{"name":"get_test_execution_failure_groups","title":"","description":"Return the failure groups present in a test execution, ranked by the number of failures in\nthat execution. Each result has the `TestFailureGroupContent` shape, including\n`numberOfFailures` calculated only from runs in the requested test execution. Use\nresolve_test_execution_url first when starting from a Dashboard test-execution\nURL.","read_only":true},{"name":"get_test_execution_run_summaries","title":"","description":"Return the completed, non-skipped test runs in a test execution, ordered by start date. Each result has the `TestRunSummaryContent` shape (result, failure details, iteration, locale, duration, test case and executor identifiers, failure group id) plus `startDate`, `environmentName`, and `appVersion`, so no per-run details call is needed for them. Failure screenshot metadata with presigned URLs is ","read_only":true},{"name":"get_test_failure_group","title":"","description":"Look up a test failure group and return its metadata (`TestFailureGroupContent` with `numberOfFailures` over the last 30 days), the affected test cases, and `latestFailingRun` (with `testRunId` and `testExecutionId`). Identify the group by a pasted Dashboard `dashboardUrl` (/{workspaceSlug}/apps/{applicationSlug}/test-failure-groups/{testFailureGroupSerialNumber}), by `applicationId` + `serialNumb","read_only":true},{"name":"get_test_failure_group_history","title":"","description":"Return the history of a test failure group across test executions within a look-back window. The history covers every execution in which the test cases affected by the group ran (not only the failing ones), so passing executions are included. Each execution entry has its date, environments, app versions, run counts, and an `outcome` of `failed` (failed with this group), `flaky` (failed with this g","read_only":true},{"name":"resolve_test_run_url","title":"","description":"Resolve a Dashboard test-run URL or path of the form\n/{workspaceSlug}/apps/{applicationSlug}/test-executions/{testExecutionSerialNumber}/runs/{testRunSerialNumber}\ninto the `testRunId` for downstream test-reporting tools. Use this first when you start\nfrom a Dashboard URL, then call get_test_run_details,\nget_test_run_logs, or get_test_failure_call_stack with the returned\n`testRunId`.","read_only":true},{"name":"get_test_run_details","title":"","description":"Fetch full metadata for a single test run: result, failureType, failureDescription and location, device, OS, locale, environment, app version, current view, timing, crashReportId, testFailureGroupId, and one-hour presigned media URLs (`screenshot`, `screenRecording`, `accessibilitySnapshot`). Use this after resolve_test_run_url to get the failure summary and media before inspecting the call stack ","read_only":true},{"name":"get_test_failure_call_stack","title":"","description":"Return the call stack(s) captured for a test run: `testCallStack` (where the test failed) and, when the failure was triggered by an application crash, `appCrashCallStack`. Each frame includes image, symbol, file name, line number and whether it belongs to a system image. Use this after get_test_run_details when you want the failing frame or the app-crash stack behind the failure.","read_only":true},{"name":"get_test_run_logs","title":"","description":"Return the activity logs captured during a specific test run: console prints, app lifecycle events, memory warnings, and network requests/responses. Logs are returned in chronological order, truncated to the 200 most recent entries when the total exceeds that limit. Use this after get_test_run_details and get_test_failure_call_stack when you want to inspect the runtime context around the failure.","read_only":true}],"server_info":{"version":"1.0.0","name":"Appelium MCP"},"category":"analytics","tags":["developer","agents","design"],"kind":"remote","source":"registry","submitted":{},"first_party":true,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-11-17","stars":0,"badges":["new"],"sponsor":null,"page":"https://agentsindex.org/agents/com-appelium-mcp/"}