Skip to main content
Glama

Related Servers

Alternatives to unfour

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Secure local development platform that exposes controlled developer capabilities (FS, Git, search, command execution) to AI assistants via MCP with deny-by-default security and audit logging.
      -
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local-first MCP server that enables AI-assisted coding through workspace-scoped tools for file reading/editing, command execution, jobs, Git, LSP, media, browser, and desktop workflows. It enforces OAuth, workspace ACL, trust policies, and file/secret guards so owners can safely grant inspect, edit, or trusted capabilities.
      32 npm
      MIT
    • A
      license
      C
      quality
      B
      maintenance
      Local-first MCP runtime for coding agents with bounded workspace access, content-preconditioned writes, AST search, LSP navigation and diagnostics, and Git status/diff. Designed to give coding agents useful repository access without treating unrestricted shell access as the default integration boundary.
      13
      3
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Production-grade MCP server that gives AI agents safe access to your local dev environment: filesystem, databases, processes, and OpenAPI specs.
      15
      41 npm
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable chat clients like ChatGPT, Claude, and Cursor to read, search, edit, and run commands on a local machine, including git operations and browser automation. Runs as a local daemon with workspace path jails, safety modes, checkpoints, and human-in-the-loop approval for edits and shell commands.
      MIT

    TDQS

    B3.4/5.0

    Scored across 72 tools

    Disambiguation4/5

    The domain.action naming and detailed descriptions generally make each tool's purpose distinct, and cross-references such as run_diagnostic vs exec help. However, with 72 tools there are minor overlaps, e.g. generic connection.list vs ssh.list_connections/db.list_connections, and multiple history/list surfaces that could be confused.

    Naming Consistency5/5

    All tools follow a consistent snake_case namespaced pattern: unfour.<domain>.<action>. Verbs are used predictably (list, get, create, update, delete, run, etc.), with only expected noun-style exceptions like current and health.

    Tool Count1/5

    72 tools is far beyond a practical, well-scoped set for an agent. Even across several domains, this volume is excessive and many fine-grained CRUD/list operations could be consolidated or exposed through resource parameters.

    Completeness4/5

    Coverage is broad across workspaces, API requests/environments, SSH connections/tasks/files, database connections/tables/query/export, Flow runs, activity, and health. Minor gaps exist, such as no workspace create/delete tools and no explicit API folder CRUD, but core workflows are covered.

    Maintenance

    ActivityActive
    ResponsivenessNo issues