Skip to main content
Glama
erkankrcr

kasm-workspaces-mcp

by erkankrcr
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to kasm-workspaces-mcp

No user-submitted related servers found.

    Related Servers

    • Kasm MCP Server v2

      roguedev-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to manage and interact with Kasm Workspaces containerized desktop infrastructure, providing tools for session management, command execution, file operations, and user management via the Model Context Protocol.
      5
      MIT

    • kasm-use

      rchurro
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to see and drive Kasm Workspaces desktops by starting and stopping sessions, taking screenshots, and performing clicks, typing, key presses, and scrolling through MCP clients or as a native Hermes Agent plugin.
      8
      166 PyPI
      1
      MIT

    • K8s MCP Server

      apecloud
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs like Claude to securely execute Kubernetes CLI tools (kubectl, helm, istioctl, argocd) across multiple clusters through dynamic kubeconfig support, allowing natural language Kubernetes management and operations.
      5
      MIT

    • VAST MCP Server

      jim-coyne
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables LLMs to manage VAST Data storage infrastructure, including views, quotas, snapshots, and network configurations, through natural language commands.
      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.2/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: lifecycle operations (create/pause/resume/destroy), status/list, share link, screenshot, command execution, and workspace listing. No two tools appear to overlap in purpose.

    Naming Consistency4/5

    Tool names mostly follow verb_noun in snake_case (create_kasm_session, destroy_kasm_session, pause_kasm_session, resume_kasm_session). Minor inconsistency exists: some use 'kasm_session' while others use just 'session' (get_session_status, get_session_screenshot) and 'user_sessions' (list_user_sessions), but the pattern remains predictable.

    Tool Count5/5

    Ten tools is a well-scoped count for a Kasm session management server. Each tool provides a meaningful operation without redundant or unnecessary functions, making it neither too thin nor too heavy.

    Completeness4/5

    The toolset covers the main session lifecycle (create, destroy, pause, resume, status, list) plus sharing, screenshots, command execution, and available workspaces. Minor gaps exist, such as no update/rename session or share revocation, but the core workflows for Kasm session management are complete.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources