Megalinter logo

Megalinter

Run Ox Security MegaLinter through MCP to scan code, inspect reports, discover linters, and generate configuration.

Install Megalinter

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "megalinter": {
      "command": "npx",
      "args": [
        "-y",
        "@downatthebottomofthemolehole/megalinter-mcp-server"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

megalinter MCP server connects AI agents to Ox Security MegaLinter through `mega-linter-runner`, supporting lint execution, report analysis, configuration generation, and linter discovery. Its tools handle both natural-language shortcuts and explicit workflows, including quick, full, security, and fix scans. Docker or a compatible runtime such as Colima is required, and the server can be used locally or within CI/CD environments. Reach for it when an agent needs to run MegaLinter or interpret its JSON and SARIF results.

Use cases

  • Run a quick or security-focused repository scan
  • Generate a baseline MegaLinter configuration
  • Inspect available linters for a language or security area
  • Parse JSON or SARIF reports and summarize failures

Key features

  • Natural-language scan shortcuts and compact aliases
  • Configurable MegaLinter execution through mega-linter-runner
  • Flavor and linter discovery by stack, language, and security focus
  • JSON and SARIF report parsing
  • Issue summaries and security recommendations
  • CI-oriented reporter discovery

Tools15

What Megalinter lets your agent do. Expand a tool for its parameters.

Self-reported~241 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked Today

Recent health check succeeded.

16/16 checks healthy over the last 89d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 4d ago via OSV.dev · @downatthebottomofthemolehole/megalinter-mcp-server (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars3Stargazers on the source repository.
npm downloads1.1kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed15Callable tools this server registers over MCP.

How Megalinter works

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.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Megalinter

megalinter is an MCP server that connects AI agents to Ox Security MegaLinter through mega-linter-runner. Its main tools run lint scans, generate `.mega-linter.yml`, discover flavors and linters, parse JSON or SARIF reports, summarize issues, and provide security recommendations for local or CI workflows.

Install or run the published `@downatthebottomofthemolehole/megalinter-mcp-server` package with an MCP-compatible host. The runtime requires Node.js 24.14.0 or newer, plus Docker or a compatible container runtime such as Colima for MegaLinter execution.

Use `megalinter_quick_action` with a security scan request or call `scan` with `scanMode` set to `security`. The server maps security scans to MegaLinter's security flavor and can return concise output or produce report artifacts for later parsing.

Use `megalinter_parse_reports` or its `parse` alias and select `json` or `sarif` as the report type. Supply the reports directory when it is not the default location, then use the summary tools to aggregate issue totals by severity or linter.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewMegalinter AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/megalinter?style=directory)](https://allmcps.com/mcp/megalinter)
HTML Embed
<a href="https://allmcps.com/mcp/megalinter"><img src="https://allmcps.com/api/badge/megalinter?style=directory" alt="Megalinter on AllMCPs" /></a>