Skip to main content
Glama
nickvasilescu

Orgo MCP Server

by nickvasilescu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Orgo MCP Server

No user-submitted related servers found.

    Related Servers

    • husk

      Hotragn
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to operate disposable Linux computers via MCP, providing tools for shell, file read/write, directory listing, and port exposure. It also supports browser automation and integration with any MCP-compatible client.
      Apache 2.0

    • rustdesk-mcp-bridge

      jeremiejt38
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to control remote desktops through screen capture, mouse movement, and keyboard input.
      MIT

    • ComputerMate

      one710
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI to control a computer through mouse, keyboard, and screen capture tools, with support for local native and Docker sandboxed environments.
      7 npm
      5
      MIT

    • mcp-incus-vm

      RAGton
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to control and automate Incus/QEMU virtual machines via SSH, supporting mouse/keyboard, screenshots, commands, and lifecycle management.
      MIT

    • fleet

      xeniak123
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to remotely control multiple computers via MCP: run commands, manage files, install software, view and control screens, and execute parallel tasks across machines.
      132 npm
      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.9/5.0

    Scored across 35 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes, but some overlap exists (e.g., orgo_bash vs orgo_exec, orgo_download_file vs orgo_export_file). Descriptions are detailed enough to resolve confusion, but the large number of tools still requires careful reading.

    Naming Consistency5/5

    All tools follow a consistent orgo_verb_noun pattern using snake_case (e.g., orgo_create_computer, orgo_list_projects). The naming is predictable and uniform across the entire set.

    Tool Count3/5

    35 tools is significantly above the typical 3-15 range, but the broad domain (project/computer management, file operations, AI, streaming) justifies most tools. However, some tools could be consolidated (e.g., start/stop/restart per resource).

    Completeness4/5

    The tool surface covers CRUD for projects/computers, file operations, AI completions, streaming, and system interaction. Missing are update operations (e.g., update_computer, update_project) and possibly batch file actions, but core workflows are well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources