Agents Index

Appelium

OnlineNew

Investigate iOS and Android crashes and failed UI tests from your coding agent.

Visit publisherConnectJSON

What it can do: 17 tools

  • list_applications read-onlyList 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 applicati
  • get_top_crash_groups read-onlyReturn 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
  • get_crash_group read-onlyFetch 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 dashbo
  • get_crash_group_stats read-onlyReturn 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
  • resolve_crash_report_url read-onlyResolve a Dashboard crash-report URL or path into `crashGroupId` and `crashReportId`. Supports both application-level and workspace-level routes: /{workspaceSlug}/apps/{applicationSlug}/crash-groups/{crashGroupSerialNumb
  • get_crash_report_details read-onlyFetch 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),
  • list_crash_reports read-onlyList 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,
  • get_crash_report_logs read-onlyReturn 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 entr
  • resolve_test_execution_url read-onlyResolve 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-execut
  • get_test_execution_failure_groups read-onlyReturn 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 th
  • get_test_execution_run_summaries read-onlyReturn 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 iden
  • get_test_failure_group read-onlyLook 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`). Id
  • get_test_failure_group_history read-onlyReturn 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 ex
  • resolve_test_run_url read-onlyResolve 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
  • get_test_run_details read-onlyFetch 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 presign
  • get_test_failure_call_stack read-onlyReturn 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, li
  • get_test_run_logs read-onlyReturn 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 rec

Connect it

Claude Code
claude mcp add --transport http appelium https://api.appelium.com/v1/mcp
Claude.ai / ChatGPT
Settings → Connectors → Add custom connector
URL: https://api.appelium.com/v1/mcp
Cursor (~/.cursor/mcp.json)
{
  "mcpServers": {
    "appelium": {
      "url": "https://api.appelium.com/v1/mcp"
    }
  }
}
VS Code (.vscode/mcp.json)
{
  "servers": {
    "appelium": {
      "type": "http",
      "url": "https://api.appelium.com/v1/mcp"
    }
  }
}

Questions

What does Appelium do?

Investigate iOS and Android crashes and failed UI tests from your coding agent. It exposes 17 tools to AI assistants.

What tools does Appelium provide?

17 tools, including list_applications, get_top_crash_groups, get_crash_group, get_crash_group_stats, resolve_crash_report_url, get_crash_report_details, list_crash_reports, get_crash_report_logs, resolve_test_execution_url, get_test_execution_failure_groups, get_test_execution_run_summaries, get_test_failure_group….

How do I connect Appelium to Claude, ChatGPT or Cursor?

Add the remote MCP endpoint https://api.appelium.com/v1/mcp as a custom connector or MCP server. Copy-paste setup is on this page.

Does Appelium require an account or API key?

No sign-in was needed to list its tools. Individual tools may still need an account or API key.

Is Appelium online?

As of 2026-11-19 our probe found it online. It answered 100% of our last 3 checks.

Who publishes Appelium?

appelium.com. The official MCP Registry verified that the publisher controls this domain before accepting the listing.

Similar in Analytics & BI