# megalinter [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/DownAtTheBottomOfTheMoleHole/megalinter-mcp  
**GitHub Stars:** 3  
**npm Downloads (last month):** 1064  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/megalinter

## Description
MCP server for running Ox Security MegaLinter via mega-linter-runner

## Tools
Capabilities this server exposes over MCP:

- **megalinter_quick_action** — Handle short natural requests with defaults
- **scan** — Ultra-short alias for quick scan
- **summary** — Ultra-short alias for error summary
- **parse** — Ultra-short alias for report parsing
- **help_quick** — Ultra-short alias for context-aware help
- **megalinter_help_quick** — Context-aware suggestions for your project
- **megalinter_run** — Run linting and produce report artefacts
- **megalinter_write_config** — Generate baseline `.mega-linter.yml
- **megalinter_list_flavors** — Identify an appropriate flavour for your stack
- **megalinter_get_linters** — Filter linters by language, security, and auto-fix support
- **megalinter_get_security_info** — View security linters grouped by SAST, secrets, container, and IaC
- **megalinter_get_reporters** — Select output/reporting formats for local and CI workflows
- **megalinter_parse_reports** — Read JSON or SARIF reports in structured form
- **megalinter_get_issue_summary** — Summarise issue totals and top failing linters
- **megalinter_get_security_recommendations** — Produce practical shift-left security actions

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "megalinter": {
    "command": "npx",
    "args": ["-y","@downatthebottomofthemolehole/megalinter-mcp-server"]
  }
}
```

## Documentation

## What megalinter MCP server does

megalinter MCP server exposes Ox Security MegaLinter through the Model Context Protocol. It invokes MegaLinter with `mega-linter-runner`, then returns scan results, report data, configuration output, or discovery information through MCP tools.

The server covers three main workflows:

- Run linting against a repository or selected path.
- Discover flavors, linters, security checks, and reporter formats.
- Parse reports and summarize issues by severity or linter.

It also includes short aliases for common actions. An agent can request a quick scan, summarize errors, parse a report, or ask for project-specific help without supplying the full tool name.

## How it works

`megalinter_quick_action` interprets a short request and routes it to a scan, configuration, discovery, parsing, summary, or recommendation workflow. Explicit parameters are available when deterministic behavior is preferred. Scan presets include quick, full, security, and fix modes; language hints can influence flavor selection, and security-only or auto-fix-only filters are available for linter queries.

`megalinter_run` provides lower-level control over the MegaLinter invocation, including the working directory, target path, flavor, release tag, image override, environment arguments, and timeout. Scan operations produce report artifacts in a configurable reports directory. JSON and SARIF outputs can be read with `megalinter_parse_reports`, while `megalinter_get_issue_summary` aggregates totals and highlights failing linters.

The project is intended for local use and CI/CD environments such as GitHub Actions, GitLab CI/CD, Azure DevOps, CircleCI, Jenkins, and other Docker-capable platforms.

## Setup and configuration

The package is published as `@downatthebottomofthemolehole/megalinter-mcp-server`. The server requires Node.js 24.14.0 or newer and Docker, or a compatible container runtime such as Colima. MegaLinter runs through its container-based runner, so the runtime must be available to the environment hosting the MCP server.

A baseline `.mega-linter.yml` can be generated with `megalinter_write_config`. Its output path is configurable, which allows an agent to create project configuration without manually assembling the file.

## Tools and capabilities

The server provides 15 tools:

- Run scans with `megalinter_run` or route short requests through `megalinter_quick_action`.
- Use `scan`, `summary`, `parse`, and `help_quick` as compact aliases.
- Generate a baseline configuration with `megalinter_write_config`.
- Find suitable MegaLinter flavors with `megalinter_list_flavors`.
- Filter linters by language, security focus, or auto-fix support with `megalinter_get_linters`.
- Group security checks into SAST, secrets, container, and infrastructure-as-code categories.
- Inspect reporter formats for local and CI output.
- Parse JSON or SARIF artifacts and summarize issue counts.
- Produce security-focused shift-left recommendations.
- Get repository-aware suggestions from `megalinter_help_quick`, which detects languages, frameworks, Docker, Terraform, and security-related files.

## Limitations and notes

The server is community-maintained rather than an official Model Context Protocol implementation. Ox Security sanctions it as a complement to its official MegaLinter tools. Container support is a prerequisite for running MegaLinter, and scan duration can be controlled through the available timeout options.

_Full upstream README: https://allmcps.com/mcp/megalinter/readme_