Skip to main content
Glama

Related Servers

Alternatives to GPT Commander

No user-submitted related servers found.

    Related Servers

    • 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
      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
      23 npm
      3
      MIT
    • A
      license
      C
      quality
      C
      maintenance
      A privacy-first MCP server that provides local LLM-enhanced tools for code analysis, security scanning, and automated task execution using backends like Ollama and LM Studio. It enables symbol-aware code reviews and workspace exploration while ensuring that all code and analysis remain strictly on your local machine.
      36
      ISC
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives AI agents terminal execution, Python scripting, file management, and code search tools so they can carry out real development tasks. It exposes bash, Python, glob, grep, and file/folder operations over MCP for coding assistants and codebase exploration.
      1
      MIT

    TDQS

    C2.4/5.0

    Scored across 40 tools

    Disambiguation2/5

    Several tools have overlapping purposes: start_search and search_code both use ripgrep, and ide_symbol_search and find_symbol both use the IDE/LSP symbol index. This creates ambiguity in tool selection, especially for agents trying to choose the right search or symbol tool.

    Naming Consistency4/5

    Most tools follow a verb_noun snake_case pattern (e.g., read_file, kill_process, list_sessions, dev_server_start). However, memory_note is a noun phrase rather than a verb, and a few tools are bare verbs (lint, format, build), creating minor inconsistency.

    Tool Count2/5

    At 40 tools, the surface is very large. While the server aims to cover many domains, there are redundant tools (e.g., start_search/search_code, ide_symbol_search/find_symbol) that inflate the count and could be consolidated, making the tool set feel heavy and less focused.

    Completeness3/5

    Core workflows such as file operations, process management, IDE integration, and project commands are well covered. However, there are notable gaps: no file delete/rename, no memory retrieval (only memory_note), and git tools stop short of an actual commit, leaving some workflows incomplete.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues