LocalDev MCP
Related Servers
Alternatives to LocalDev MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceA 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.39 npm2MIT
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP server that provides project context, verification gates, and structured tools for coding agents to discover knowledge, run diagnostics, and execute allowlisted commands within a repository.10 npmMIT
- AlicenseNot gradedqualityAmaintenanceA 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.48 npmMIT
- AlicenseNot gradedqualityDmaintenanceA 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.3GNU Lesser General Public v2.1 only
- FlicenseNot gradedqualityCmaintenanceA 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-
- FlicenseNot gradedqualityAmaintenanceExposes a governed suite of 38 tools through a single OAuth-gated MCP endpoint, letting web-based AI chats (Claude, ChatGPT, Grok) and local IDEs read and edit files, run whitelisted shell commands, search content, use Git, inspect SQLite and localhost APIs, drive browser automation and DevTools, manage background tasks and ports, and access clipboard or desktop notifications on your own machine. A strict command whitelist and folder-level access controls keep the sessions safe by default.-
TDQS
Scored across 49 tools
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.
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.
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.
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.