Skip to main content
Glama
callstack

agent-device

Official
by callstack
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to agent-device

No user-submitted related servers found.

    Related Servers

    • Taproom

      batteryshark
      A
      license
      Not graded
      quality
      B
      maintenance
      Discovers and manages portable agent capabilities (skills and MCP servers) from configurable collections, providing search, inspection, and local installation via CLI and MCP tools.
      1
      MIT

    • antigravity-mcp

      alvarosw
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible coding agents to run the local Antigravity CLI as a coding agent, manage conversation context and common options, and inspect usage, quota, models, version, help, and read-only slash commands.
      18 npm
      MIT

    • jwx-mcp

      JustworxCloud
      F
      license
      A
      quality
      C
      maintenance
      Exposes Justworx devices to AI agents as MCP tools and resources, backed by the public Developer API. Supports local stdio and hosted remote OAuth operation for controlling device IO, rules, and viewing live state.
      6
      -
    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

    B3.1/5.0

    Scored across 57 tools

    Disambiguation3/5

    Many tools have overlapping interaction surfaces (click/press, swipe/gesture/scroll, install/reinstall/install-from-source), but most descriptions explicitly call out boundaries and preferred alternatives, so an agent can usually disambiguate with care.

    Naming Consistency3/5

    Names are all lowercase and hyphenated for compounds, but mix verbs, nouns, and resource names with no consistent verb_noun pattern (e.g., perf, push, devices, install-from-source, is). The style is readable, but not predictable in terms of grammatical role.

    Tool Count1/5

    57 tools is far beyond the 25+ threshold and into the extreme range; while the domain is broad, this surface will impose a large selection burden on agents.

    Completeness4/5

    The set covers device lifecycle, app install/open/close, UI query/interact/wait, snapshots/screenshots, logging/network/perf, and replay/test workflows. Minor gaps like uninstall or richer device information exist, but the core automation lifecycle is well covered.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources