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
      B
      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.
      419 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
      55 npm
      4
      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-namespaced names (api/db/ssh/flow/workspace) plus explicit verb+noun phrasing make nearly every tool's target resource and action clear, and descriptions reinforce the boundaries (read-only vs mutating vs confirmation-gated). A few pairs remain genuinely confusable: unfour.api.get_history vs unfour.api.list_history, unfour.connection.list vs unfour.db.list_connections/unfour.ssh.list_connections, and the identically-described db.update_connection and ssh.update_connection.

    Naming Consistency4/5

    Strong, predictable domain.verb_noun convention throughout (api.create_request, ssh.delete_task, workspace.update_variable). Minor deviations are noun-only tools like workspace.current, system.health, activity.list, and connection.list, which break the verb pattern but stay readable and unambiguous within their namespace.

    Tool Count2/5

    72 tools across eight sub-domains is very heavy for a single MCP surface and requires an agent to route through many near-sibling options before acting. While the sub-domain grouping is logical, the sheer breadth pushes well past the comfortable 3-15 range and raises selection cost substantially.

    Completeness4/5

    Coverage is broad and lifecycle-complete for most resources: variables, collections, requests, environments and env vars, DB/SSH connections, SSH tasks and runs, and flows all have list/get/create/update/delete plus execution and history. Gaps exist around API folders (referenced in cascade deletes but no create/list/update tool), no get_collection, and no per-connection get for SSH, but agents can work around these via list tools.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues