MegaLinter MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| megalinter_quick_actionB | Interactive shortcut tool for short requests (for example: quick scan, security scan, summarise errors, list python security linters). |
| megalinter_runA | Run Ox Security MegaLinter using mega-linter-runner with full low-level control. For short prompts, use megalinter_quick_action. |
| megalinter_write_configB | Generate a minimal .mega-linter.yml configuration file. |
| megalinter_list_flavorsB | List commonly used MegaLinter flavors. |
| megalinter_get_lintersA | Discover available linters by language, security category, or auto-fix capability. |
| megalinter_get_security_infoA | Get comprehensive information about security-focused linters organized by category (SAST, secrets, supply-chain, container, infrastructure). |
| megalinter_get_reportersA | List all available MegaLinter reporters and their configuration options. |
| megalinter_parse_reportsA | Parse MegaLinter JSON or SARIF reports from the reports directory. Returns structured report data for analysis. |
| megalinter_get_issue_summaryC | Analyze and summarize issues from MegaLinter reports by severity, linter, and category. Enables filtering and targeted remediation. |
| megalinter_get_security_recommendationsB | Generate security-focused recommendations based on active linters and common threat categories (SAST, secrets, container, infrastructure). |
| megalinter_help_quickA | Get context-aware help and examples based on your current repository. Suggests relevant commands for detected languages and frameworks. |
| scanB | Ultra-short alias for quick scan. Same as megalinter_quick_action with action='scan'. |
| summaryA | Ultra-short alias for error summary. Same as megalinter_quick_action with action='summary'. |
| help_quickB | Ultra-short alias for context-aware help. Same as megalinter_help_quick. |
| parseB | Ultra-short alias for report parsing. Same as megalinter_quick_action with action='parse'. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.