Skip to main content
Glama
Agent Workstation
by zix-chen

Related Servers

Alternatives to Agent Workstation

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to execute commands, edit files, run Git workflows, and perform validated independent reviews in real development environments through Docker-based runtimes with separated developer and auditor permissions.
      MIT
    • A
      license
      D
      quality
      C
      maintenance
      Enables controlled local developer operations including file and process management, shell execution, SSH, WSL, Docker, Git, browser and desktop automation, media processing, and asynchronous jobs through MCP.
      146
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding apps to perform safe, audited git work on isolated task branches, run a project's own tests and checks, and execute multi-step workflows with terminal-only approval gates across any MCP client. Every command, file access, and cross-tool call is permission-checked, shell-free, and logged, with no pushes or destructive git operations.
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables teams to onboard remote MCP servers, enforce function-level permissions and credential modes, and let developers expose permitted tools through a unified MCP endpoint with search and execute functions while auditing usage.
      MIT

    TDQS

    B3.4/5.0

    Scored across 19 tools

    Disambiguation4/5

    Most tools have clearly distinct resource+action purposes, such as file reading/listing/searching versus command execution and Git inspection. The main overlap is between apply_patch and apply_changes, which both modify files and could require an agent to read descriptions carefully before choosing one.

    Naming Consistency4/5

    Tool names consistently use snake_case and mostly follow predictable prefixes such as read_, list_, search_, apply_, git_, and exec_. Minor deviations exist (server_info and workspace_guide are noun-based rather than verb_noun), but the naming remains readable and coherent.

    Tool Count4/5

    The 19 tools fit a broad workspace-agent scope covering file operations, patching, command execution, process management, Git inspection, image viewing, and guidance. It is slightly on the heavy side relative to a typical 3-15 tool server, but each cluster addresses a real capability.

    Completeness4/5

    The surface covers core workspace lifecycle operations: read/list/search, create/write/edit/delete via apply_changes, patching via apply_patch, command execution and management, and key Git read operations. Minor gaps such as dedicated Git commit/stage tools or simple directory metadata operations can be handled through exec_command, so the set is largely complete for its purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo recent community issues