Skip to main content
Glama
sanchorelaxo

OpenSimulator MCP Server

by sanchorelaxo
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to OpenSimulator MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP3

      emrgim
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables users to control grandMA3 consoles through official OSC /cmd commands, with an admin UI for IP scanning, object/action permissions, chat integration, and MCP stdio access.
      MIT

    • Horizon MCP Server

      matt-coppinger
      A
      license
      A
      quality
      B
      maintenance
      Enables management of Omnissa Horizon VDI infrastructure through the Horizon REST API, offering tools for inventory, monitoring, configuration, entitlements, Active Directory, and help desk operations.
      72
      MIT

    • Resonite MCP

      sandraschi
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables natural language control of the Resonite social VR platform, allowing users to command worlds, customize avatars, inspect sessions, spawn inventory assets, and monitor telemetry through AI chat assistants.
      8
      MIT

    • factorio-mcp

      phiresky
      F
      license
      A
      quality
      D
      maintenance
      Enables control and inspection of a Factorio 2.0 server via RCON, with tools for administration, player management, game state queries, and Lua execution.
      19
      -

    • mcsm-mcp

      siwuli
      A
      license
      A
      quality
      C
      maintenance
      Enables management of Minecraft servers through the MCSManager panel API, including listing instances, checking status, starting/stopping/restarting/force-stopping, sending console commands, and waiting for status changes.
      10
      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

    B3.4/5.0

    Scored across 3 tools

    Disambiguation5/5

    The three tools have clearly distinct purposes: 'get' for read-only/info/show commands, 'set' for mutating/management commands, and 'run' as a fallback for any raw console commands not covered by the other two. There is no overlap or ambiguity between them, making it easy for an agent to select the correct tool based on the intended action.

    Naming Consistency5/5

    All tool names follow a simple, consistent verb pattern: 'get', 'run', and 'set'. They are short, clear, and uniformly styled without any mixing of conventions, making them predictable and easy to understand for an agent.

    Tool Count3/5

    With only 3 tools, the server feels thin for managing an OpenSimulator console, which typically involves many commands. However, the tools are well-scoped to cover read, write, and raw command categories, making the count borderline but functional for basic operations.

    Completeness4/5

    The tools provide a complete surface for the domain by categorizing commands into read-only ('get'), mutating ('set'), and a catch-all ('run') for any other console commands. This covers the core workflows of OpenSimulator management, though some specific operations might require using the raw 'run' tool instead of dedicated tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources