Skip to main content
Glama
Sign In
Insta360 Studio MCP

Insta360 Studio MCP

by MuhammdQasim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to Insta360 Studio MCP

No user-submitted related servers found.

    Related Servers

    • windows-computer-use-mcp

      hiphopanda
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides desktop automation tools for Windows, enabling mouse and keyboard control, screenshots, clipboard management, and application interaction via the MCP protocol.
      83 npm
      MIT

    • Infinite_computer_use_mcp

      olter-tn
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable AI assistants to control a Windows computer through GUI automation, file and process operations, PowerShell commands, durable background jobs, and binary file transfer with downloadable exports.
      MIT

    • Computer-Controller-Bridg

      Dobona
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients on Windows to control the local mouse, keyboard, and screen understanding via MCP stdio, allowing automated workflows like viewing the screen, locating elements, clicking, typing, and verifying results.
      1
      Apache 2.0

    • win-rdp-mcp

      stubbedev
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables remote control of a Windows desktop via MCP, including screenshots, mouse and keyboard, window management, PowerShell, files, services, registry, scheduled tasks, event log, and network checks.
      16 npm
      2
      MIT

    • Computer Use MCP

      A8Cl233395
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to observe and control Windows desktop applications by reading UIA element trees and capturing screenshots, then acting through UIA patterns or synthesized mouse and keyboard input. It runs standalone on an interactive Windows session, without requiring the original host application.
      1
      -
    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.3/5.0

    Scored across 21 tools

    Disambiguation4/5

    Most tools clearly target distinct actions or resources: UI primitives, window lifecycle, media info, and export verification. A few pairs such as studio_wait vs studio_wait_ready and studio_status vs studio_capabilities could be confused, but their descriptions draw clear boundaries.

    Naming Consistency4/5

    All tools use the studio_ prefix and snake_case, with a strong verb_noun pattern for actions. Minor deviations are the noun-phrase read-only tools like studio_status, studio_media_info, and studio_capabilities.

    Tool Count3/5

    Twenty-one tools is heavy for this domain, though most correspond to distinct desktop-automation primitives and verification steps. The set is plausible but sits at the upper end of what feels comfortably scoped.

    Completeness4/5

    The surface covers launch, window selection, observation, input primitives, import, export checkpointing, verification, and media inspection. Gaps are minor, such as no direct export trigger or project save/close operation, with those steps left to generic UI interaction.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources