Skip to main content
Glama

Related Servers

Alternatives to PersonalMCP

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to manage a workspace through file reading, writing, editing, searching, Bash/Python execution, and job control, with optional desktop GUI and Cloudflare Tunnel access.
      12
      4
      -
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to safely read, write, edit, search, and optionally run commands within one or more named project workspaces, while maintaining a work journal and tracking changes.
      19
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables managed access to workspace file operations, background tasks, Skills, and upstream MCP services through a unified web console with workspace-bound keys and explicit tool permissions.
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP clients to manage files in an isolated workspace and perform lightweight Git operations through a protected Streamable HTTP endpoint, including listing, reading, writing, searching, replacing, and deleting files plus checking status and diffs.
      1
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      Exposes a secure, path-confined bridge to a local workspace and git remotes, enabling MCP clients to search, read, write, reset files, and perform git operations.
      -

    TDQS

    C2.9/5.0

    Scored across 68 tools

    Disambiguation3/5

    Tools are grouped into clear domains, but several within-domain pairs overlap heavily: git_status vs git_repository_status, git_log vs git_recent_history, and git_diff vs git_diff_summary vs git_diff_stat. Descriptions help distinguish bounded/read-only variants, but an agent could still easily misselect among them.

    Naming Consistency3/5

    All names are snake_case, which is consistent, but the structural convention is mixed: verb_noun (list_directory, read_text_file), noun_verb (todo_list, git_status), and noun_noun (service_status, git_repository_status) all appear. The domain prefixes help readability, but there is no single predictable pattern.

    Tool Count1/5

    With 68 tools, the surface is extremely large even for a broad personal automation server, and several tools duplicate existing read-only git functionality. This is squarely in the 50+ extreme-count range and makes discovery and selection harder.

    Completeness4/5

    The server covers filesystem, search, shell, Python tooling, git, data conversion, web/API testing, diagnostics, todos, and system inspection with broad lifecycle support. The main gaps are git network/workflow operations such as clone/fetch/pull/merge and service or process control, though run_command provides a workaround.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing