Skip to main content
Glama
mehrdad03

LocalDev MCP

by mehrdad03

Related Servers

Alternatives to LocalDev MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive Model Context Protocol server implementation that enables AI assistants to interact with file systems, databases, GitHub repositories, web resources, and system tools while maintaining security and control.
      23 npm
      2
      MIT
    • 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.
      515 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A universal AI-powered testing server built on the Model Context Protocol (MCP). Allows AI agents to inspect, execute, test, monitor, debug, and report on software projects.
      3
      GNU Lesser General Public v2.1 only
    • F
      license
      Not graded
      quality
      C
      maintenance
      A secure Model Context Protocol server providing HTTP endpoints for AI agent tool execution, including file system operations, shell commands, and LLM-based code generation.
      1
      -

    TDQS

    B3.4/5.0

    Scored across 49 tools

    Disambiguation4/5

    Descriptions are detailed enough to distinguish tools, even those in overlapping domains like test runners (run_phpunit, run_pest) or file modification (replace_text, apply_patch). Some confusion is possible between multiple database-inspection tools, but their scopes are clearly defined.

    Naming Consistency4/5

    Most tools use a consistent verb_noun pattern (e.g., list_projects, read_file, create_file). There are minor deviations like 'laravel_tinker_execute' (should be execute_laravel_tinker) and 'local_secret_operation', but overall the pattern is predictable.

    Tool Count3/5

    49 tools is high for a server, but the broad scope of local development (file ops, Laravel, Node, Git, testing) justifies the count. It borders on too many, but each tool serves a specific purpose and the set is well-organized.

    Completeness4/5

    The server covers a comprehensive range: file CRUD, Git operations, project inspection, Laravel artisan and database commands, testing (PHPUnit, Pest), and more. Minor gaps exist (e.g., no tool for custom linters beyond ESLint), but core development workflows are fully supported.

    Maintenance

    ActivityStale
    ResponsivenessNo issues