MegaLinter MCP Server
Related Servers
Alternatives to MegaLinter MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceProvides MCP tools for fetching GitHub PR diffs, searching codebases, running unit tests, and linting code, enabling automated code review and CI/CD workflows.MIT
- FlicenseNot gradedqualityDmaintenanceEnables dependency, security, and coding convention checks for Python and Java projects via MCP tools. Supports local paths or Git URLs.-
- -licenseNot gradedqualityNot gradedmaintenanceProvides comprehensive code quality tools including linting, security scanning, TypeScript checking, and testing through a single MCP server. Integrates multiple quality analysis tools like Biome, ESLint, and Playwright for streamlined development workflows.-
- AlicenseNot gradedqualityCmaintenanceMCP server to lint and validate Kubernetes-related manifests(Helm, FluxCD, ArgoCD, Kustomize, etc.)57 PyPIMIT
- AlicenseNot gradedqualityBmaintenanceProvides MCP tools for local code validation with execution evidence, enabling users to run planned checks on projects and receive JSON results that distinguish passing, failing, and incomplete outcomes.34 npmMIT

yotta-dev-mcpofficial
AlicenseNot gradedqualityBmaintenanceProvides deterministic local development tools over stdio MCP, including repository mapping, code review, secret and dependency scanning, release checks, whitelisted checks, scaffolding, and workflow state tracking.185 npmMIT
TDQS
Scored across 15 tools
Multiple tools are direct aliases (e.g., help_quick and megalinter_help_quick; parse, scan, summary for megalinter_quick_action), creating ambiguity about which to use. While the descriptions mention the aliasing, it adds unnecessary overlap.
Most tools follow a consistent megalinter_verb_noun pattern, but the inclusion of aliases like help_quick, parse, scan, and summary breaks the pattern, mixing short and full names.
With 15 tools, the count is at the high end of well-scoped. However, some tools are redundant due to aliases, so not every tool earns its place, but overall the scope is reasonable.
The tool surface covers the core lifecycle: listing, running, parsing reports, writing config, and security recommendations. Minor gaps like updating config or managing multiple runs are absent, but essential functionality is present.