Investigate iOS and Android crashes and failed UI tests from your coding agent.
MCP Score How we grade
From what our daily checks can see without credentials, last checked 21 Nov 2026.
| Reliability Answered 5 of 5 daily checks. |
30 / 30 |
| Speed Typical response 100 ms. |
20 / 20 |
| Tool docs 17 of 17 tools have a full description; 34 of 34 inputs have a description. |
25 / 25 |
| Stability No tool rewrites in 30 days. |
15 / 15 |
| Listing Complete registry listing. |
10 / 10 |
Connect Remote server
claude mcp add --transport http mcp https://api.appelium.com/v1/mcp --header "X-Appelium-Token: <X_APPELIUM_TOKEN>"
{
"mcpServers": {
"mcp": {
"url": "https://api.appelium.com/v1/mcp",
"headers": {
"X-Appelium-Token": "<X_APPELIUM_TOKEN>"
}
}
}
}
{
"servers": {
"mcp": {
"type": "http",
"url": "https://api.appelium.com/v1/mcp",
"headers": {
"X-Appelium-Token": "<X_APPELIUM_TOKEN>"
}
}
}
}
Settings > Connectors > Add custom connector
URL: https://api.appelium.com/v1/mcp
Replace the values in angle brackets with your own. Keys stay on your machine; we never see them.
Tools 17 found in our last check
list_applicationsList 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.
get_top_crash_groupsReturn 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…
get_crash_groupFetch 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 k…
get_crash_group_statsReturn 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`.
resolve_crash_report_urlResolve a Dashboard crash-report URL or path into `crashGroupId` and `crashReportId`. Supports both application-level and workspace-level routes: /{workspaceSlug}/apps/{applicationSlug}/crash-groups/{crashGroupSerialNumber}/crash-reports/{crashReportSerialNumber} /{workspaceSlug…
get_crash_report_detailsFetch full metadata for a single crash report and its symbolicated call stack. Returns the report details (device, OS, app version, locale, userIdentifier, exceptionMessage, report/attachment/activity-log file metadata), whether activity logs are attached, and any linked `testEx…
list_crash_reportsList 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…
get_crash_report_logsReturn 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.…
resolve_test_execution_urlResolve a Dashboard test-execution URL or path of the form /{workspaceSlug}/apps/{applicationSlug}/test-executions/{testExecutionSerialNumber} into the `applicationId` and `testExecutionId` used by downstream test-execution tools. Use this first when you start from a Dashboard t…
get_test_execution_failure_groupsReturn the failure groups present in a test execution, ranked by the number of failures in that execution. Each result has the `TestFailureGroupContent` shape, including `numberOfFailures` calculated only from runs in the requested test execution. Use resolve_test_execution_url…
get_test_execution_run_summariesReturn 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`, `environmentNa…
get_test_failure_groupLook 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` (/{wo…
get_test_failure_group_historyReturn 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, e…
resolve_test_run_urlResolve a Dashboard test-run URL or path of the form /{workspaceSlug}/apps/{applicationSlug}/test-executions/{testExecutionSerialNumber}/runs/{testRunSerialNumber} into the `testRunId` for downstream test-reporting tools. Use this first when you start from a Dashboard URL, then…
get_test_run_detailsFetch 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`, `accessibil…
get_test_failure_call_stackReturn 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 thi…
get_test_run_logsReturn 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 aft…
Headers
| Name | Description |
|---|---|
X-Appelium-TokenRequired, secret | Personal Appelium API key |
Details
| Endpoint | https://api.appelium.com/v1/mcp (Streamable HTTP) |
| First published | 17 Nov 2026 |
| Last updated | 17 Nov 2026 |
| Registry name | com.appelium/mcp |
More developer tools servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
