Skip to main content
Glama
devicebase

Devicebase MCP Server

Official
by devicebase
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Devicebase MCP Server

No user-submitted related servers found.

    Related Servers

    • adb_mcp_server

      wolfcoming
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables remote control of Android devices via ADB, including screen operations, input, app management, file transfer, and advanced tools like UI testing and performance analysis.
      25
      MIT

    • @qirabot/mcp

      qirabot
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to control mobile and desktop devices with natural language, including running automation tasks, taking screenshots, and managing devices.
      6
      5 npm
      MIT

    • AutoBot MCP

      yz0903
      F
      license
      B
      quality
      D
      maintenance
      Enables remote control and automation of Android devices through the Model Context Protocol, supporting UI interactions, app management, ADB commands, screenshots, and device information retrieval via AutoBot API.
      53
      -

    • Karagöz

      yagizdo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to automate Android and iOS devices, including emulators and physical devices, by capturing screenshots, reading UI accessibility trees, performing touch and text input, and managing app lifecycle and logs.
      MIT
    • vibeview by vibeview

      vibeviewofficial

      vibeview
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables coding agents to verify work on live cloud devices by uploading builds, starting sessions, driving UI through UI-tree refs, reading logs, and taking screenshots on iOS, Android, Apple TV, and Android TV.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.6/5.0

    Scored across 55 tools

    Disambiguation5/5

    Each tool targets a distinct platform and action (e.g., mobile_tap vs. mobile_long_press vs. mobile_swipe; browser_fill vs. browser_input; computer_click vs. computer_drag). The platform prefixes and action-specific verbs make tool boundaries immediately clear, with only extremely minor overlap that the descriptions resolve.

    Naming Consistency5/5

    Naming follows a strict <platform>_<verb>[_<noun>] convention throughout (mobile_, browser_, computer_), with global tools (list_devices, screenshot) being the only unprefixed ones, which is natural given their cross-platform nature. Verb choice per action is consistent and predictable.

    Tool Count4/5

    55 tools is large, but the server intentionally spans three distinct platform families (mobile, browser, computer), each with its own interaction primitives. The total count is justified by the breadth of scope, though it borders on heavy and could plausibly be split into separate per-platform servers.

    Completeness4/5

    Core lifecycle and interaction coverage is solid across all three platforms: navigation, input, state inspection, app/process control, and shell access. Minor gaps exist (e.g., no mobile app uninstall, no explicit browser element-wait primitive, limited window management on desktop), but agents can work around them with existing tools like mobile_bash, browser_exists, and computer_execute.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources