Skip to main content
Glama
scenic-contrib

Scenic MCP

by scenic-contrib
OverviewSchemaSourceRelated ServersDiscussionsAdmin

Related Servers

Alternatives to Scenic MCP

No user-submitted related servers found.

    Related Servers

    • mobile-mcp

      Kavya55
      A
      license
      A
      quality
      B
      maintenance
      A Model Context Protocol server for mobile automation and development, offering a single API to control iOS and Android devices (simulators, emulators, real devices) through accessibility trees and coordinate-based interactions. It lets AI agents launch apps, tap, swipe, type, capture screenshots, and extract structured data from native mobile apps.
      23
      29,930 npm
      Apache 2.0

    • Playwright MCP Server

      b3nw
      F
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to perform web automation tasks by connecting to remote Playwright/browserless instances, supporting navigation, screenshots, HTML extraction, and element interaction.
      10
      4
      -

    • Mobile Next MCP

      EmpathySlainLovers
      A
      license
      A
      quality
      D
      maintenance
      A Model Context Protocol server that enables scalable mobile automation for iOS and Android through a platform-agnostic interface, allowing LLMs to interact with mobile applications via accessibility snapshots or screenshot-based inputs.
      19
      29,930 npm
      2
      Apache 2.0

    • ios-sim-mcp

      artmamedov
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server for iOS Simulator automation. Enables AI assistants to visually interact with iOS apps running in the simulator.
      22 npm
      1
      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.5/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: connection testing, status checking, viewport inspection, keyboard input, mouse clicking, and mouse movement. The descriptions make it easy to differentiate between these functions, eliminating any ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with underscores (e.g., connect_scenic, get_scenic_status, inspect_viewport). The naming is predictable and readable throughout the set, with no deviations in style.

    Tool Count5/5

    With 6 tools, this server is well-scoped for interacting with a Scenic application via TCP. Each tool earns its place by covering essential functions like connection management, input simulation, and display inspection, without being too sparse or bloated.

    Completeness4/5

    The toolset provides solid coverage for basic Scenic application interaction, including connection, status, input, and display. A minor gap exists in not having tools for more advanced interactions like drag-and-drop or multi-touch gestures, but core workflows are well-supported.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources