Skip to main content
Glama
Sign In
JevSim

JevSim

by huaaudio
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to JevSim

No user-submitted related servers found.

    Related Servers

    • mobile-mcp

      neko-jpg
      A
      license
      A
      quality
      C
      maintenance
      Enables agents and LLMs to interact with native iOS and Android applications and devices via structured accessibility snapshots or coordinate-based taps, supporting simulators, emulators, and real devices.
      39
      57,882 npm
      Apache 2.0

    • Karagöz

      yagizdo
      A
      license
      B
      quality
      A
      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.
      18
      3
      MIT

    • mobile-mcp

      khoa-le
      A
      license
      A
      quality
      B
      maintenance
      Enables agents and LLMs to automate, inspect, and scrape native iOS and Android apps across simulators, emulators, and real devices through a platform-agnostic interface using accessibility snapshots or screenshot-based coordinates. It provides device, app, screen, input, log, and crash management tools, including optional cloud device reservation.
      34
      57,882 npm
      Apache 2.0

    • glovebox

      vpatel9202
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to drive GUI apps through a persistent JavaScript session where one call batches many actions, returning accessibility-tree text by default and screenshots only on request.
      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

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: status checks environment and credentials, inspect reads the current UI state, and run_steps executes user-defined interaction steps. There is no meaningful overlap that would cause an agent to select the wrong tool.

    Naming Consistency4/5

    All tools share the consistent jevsim_ prefix and use clear, readable snake_case names. The only minor deviation is jevsim_status being a noun rather than a verb_phrase like jevsim_inspect and jevsim_run_steps, but the pattern is still easy to predict.

    Tool Count5/5

    Three tools is well-scoped for this server's apparent purpose: check environment, inspect UI state, and run UI interaction steps. Each tool earns its place and there is no redundancy or bloat.

    Completeness4/5

    The tool set covers the core workflow of connecting, inspecting, and interacting with a simulator or device in a structured way. Minor gaps exist—such as no explicit screenshot or app-launch tool—but agents can likely work around these using the provided inspect and run_steps capabilities.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources