Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

Megalinter

by DownAtTheBottomOfTheMoleHoleversion 4.0.0i★ –iRuns on your computer
Registry nameio.github.DownAtTheBottomOfTheMoleHole/megalinter

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

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

Run this in your terminal

claude mcp add megalinter -- npx -y @downatthebottomofthemolehole/megalinter-mcp-server

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "megalinter": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@downatthebottomofthemolehole/megalinter-mcp-server"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account DownAtTheBottomOfTheMoleHole, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32718 servers in this category
  • Published to the registry more recently than 89% of the other 32718 servers in this category
  • Basic checks equal to or better than 100% of the other 32718 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Megalinter safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (4.0.0) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, MemberVault MCP by usefulapi

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

MegaLinter MCP Server

Note: This is a community-maintained MCP server. It is not an official Model Context Protocol server, but it is sanctioned by Ox Security as a complement to their official MegaLinter tools.

A Model Context Protocol (MCP) server for running Ox Security MegaLinter through mega-linter-runner. Works with any CI/CD platform (GitHub Actions, GitLab CI, Azure DevOps, CircleCI, Jenkins) or locally.

Overview

This server provides 15 MCP tools in total: 10 core tools and 5 convenience aliases across execution, discovery, and analysis workflows.

  • megalinter_quick_action for short, natural requests with sensible defaults.
  • megalinter_run to execute MegaLinter with configurable runtime and runner options.
  • megalinter_write_config to generate a minimal .mega-linter.yml file.
  • megalinter_list_flavors to return common MegaLinter flavors.
  • megalinter_get_linters to discover available linters by language, security focus, and auto-fix capability.
  • megalinter_get_security_info to group security linters by threat category.
  • megalinter_get_reporters to list supported report output formats and CI-targeted reporters.
  • megalinter_parse_reports to parse JSON or SARIF report artefacts.
  • megalinter_get_issue_summary to aggregate report issues by linter and severity.
  • megalinter_get_security_recommendations to generate security-focused remediation guidance.
Quick Start (Short Prompts)

If you prefer short prompts, use megalinter_quick_action first:

  • @megalinter quick scan this repository
  • @megalinter security scan
  • @megalinter summarise errors
  • @megalinter list python security linters
  • @megalinter write config

Or use ultra-short aliases for minimal typing:

  • @megalinter scan — Quick scan with defaults
  • @megalinter summary — Summarise last run's errors
  • @megalinter parse — Parse JSON report
  • @megalinter help_quick — Context-aware help for your project
Platform Compatibility

This MCP server is platform-agnostic and works universally:

  • ✅ Locally — Run MegaLinter from your IDE or command line
  • ✅ GitHub Actions — Integrate with workflows
  • ✅ GitLab CI/CD — Use in GitLab pipelines
  • ✅ Azure DevOps — Run in Azure Pipelines
  • ✅ CircleCI, Jenkins, Bitbucket Pipelines — Any CI/CD platform with Docker support
  • ✅ AI Agents & Copilot — Automated code quality checks via MCP

The only requirement is Docker (or a compatible container runtime like Colima).

Tool Matrix
ToolCategoryTypical outcome
megalinter_quick_actionInteractiveHandle short natural requests with defaults
scanAliasUltra-short alias for quick scan
summaryAliasUltra-short alias for error summary
parseAliasUltra-short alias for report parsing
help_quickAliasUltra-short alias for context-aware help
megalinter_help_quickHelpContext-aware suggestions for your project
megalinter_runExecutionRun linting and produce report artefacts
megalinter_write_configConfigurationGenerate baseline .mega-linter.yml
megalinter_list_flavorsDiscoveryIdentify an appropriate flavour for your stack
megalinter_get_lintersDiscoveryFilter linters by language, security, and auto-fix support
megalinter_get_security_infoDiscoveryView security linters grouped by SAST, secrets, container, and IaC
megalinter_get_reportersDiscoverySelect output/reporting formats for local and CI workflows
megalinter_parse_reportsAnalysisRead JSON or SARIF reports in structured form
megalinter_get_issue_summaryAnalysisSummarise issue totals and top failing linters
megalinter_get_security_recommendationsAnalysisProduce practical shift-left security actions

Tools

megalinter_quick_action

Interactive shortcut that accepts a short request and routes it to the right workflow.

Inputs:

  • request (string, optional): Short instruction. Default: quick scan.
  • action (string, optional): Explicit quick action (scan, config, flavors, linters, security, reporters, parse, summary, recommendations).
  • scanMode (string, optional): Scan preset (quick, full, security, fix).
  • target (string, optional): Directory to scan. Default: ..
  • workingDirectory (string, optional): Command working directory.
  • reportsPath (string, optional): Reports directory. Default: megalinter-reports.
  • reportType (string, optional): Parse format (json or sarif).
  • severity (string, optional): Summary filter (error, warning, info).
  • language (string, optional): Language filter for linter queries. For scans, maps to a flavor hint (python, javascript, terraform, and similar).
  • securityOnly (boolean, optional): Return only security linters in linter queries. For scans, forces security flavor.
  • autoFixOnly (boolean, optional): Return only auto-fix linters in linter queries.
  • timeoutMinutes (number, optional): Timeout for scan actions. Default: 20.
  • summaryOnly (boolean, optional): Return concise output for scans. Default: true.
  • flavor (string, optional): Optional flavor override for scan actions.
  • fix (boolean, optional): Force auto-fixes for scan actions.
  • targetPath (string, optional): Config output path for write-config requests.

Examples:

  • request: "quick scan" -> Runs ci_light against changed files.
  • request: "full scan" -> Runs all flavor.
  • request: "security scan" -> Runs security flavor.
  • request: "summarise errors" -> Returns issue summary filtered to errors.
  • request: "parse sarif report" -> Parses SARIF output.
  • action: "summary", severity: "error" -> Deterministic summary with no phrase parsing.
  • action: "scan", scanMode: "security" -> Deterministic security scan.
scan (Ultra-short alias)

Run a quick scan with minimal typing. Accepts optional parameters for customization.

Inputs:

  • language (string, optional): Target language mapped to flavor (e.g., python, javascript, terraform).
  • scanMode (string, optional): Scan preset (quick, full, security, fix). Default: quick.
  • summaryOnly (boolean, optional): Return concise output. Default: true.

Example: @megalinter scan runs a quick scan with concise output.

summary (Ultra-short alias)

Summarise errors from the last MegaLinter run with minimal typing.

Inputs:

  • severity (string, optional): Filter by severity (error, warning, info).
  • linterFilter (string, optional): Filter by linter name.

Example: @megalinter summary shows all error/warning totals.

parse (Ultra-short alias)

Parse MegaLinter report files with minimal typing.

Inputs:

  • reportType (string, optional): Report format (json or sarif). Default: json.
  • reportsPath (string, optional): Reports directory path.

Example: @megalinter parse parses the JSON report.

megalinter_help_quick

Get context-aware help based on your current repository. Detects languages, frameworks, Docker, Terraform, and security files to suggest relevant commands.

No inputs required.

Example: @megalinter help_quick returns tailored suggestions for your project.

megalinter_run

Use this tool when you need full argument-level control. For short prompts, prefer megalinter_quick_action.

Runs mega-linter-runner via npx.

Inputs:

  • workingDirectory (string, optional): Command working directory. Defaults to current process directory.
  • path (string, optional): Directory path to lint.
  • flavor (string, optional): MegaLinter flavor. Default: all.
  • release (string, optional): MegaLinter image tag. Default: v9.
  • image (string, optional): Full Docker image override.
  • env (string, optional): Environment variable string passed to --env.
  • fix (boolean, optional): Apply auto-fixes.
  • help (boolean, optional): Show mega-linter-runner help.
  • install (boolean, optional): Generate MegaLinter starter config.
  • containerName (string, optional): Docker container name override.
  • removeContainer (boolean, optional): Remove container after run.
  • configFile (string, optional): Path to .mega-linter.yml.
  • reportsPath (string, optional): Reports directory. Default: megalinter-reports.
  • disableLinters (string, optional): Comma-separated list of linters to disable.
  • lintChangedFilesOnly (boolean, optional): Sets VALIDATE_ALL_CODEBASE=false when true.
  • runnerVersion (string, optional): npm version for mega-linter-runner (for example latest).
  • timeoutSeconds (number, optional): Timeout in seconds. Default: 3600.
  • summaryOnly (boolean, optional): Return concise logs. Default: false.
  • extraArgs (string[], optional): Additional CLI arguments.
megalinter_write_config

Writes a minimal MegaLinter configuration.

Inputs:

  • targetPath (string, optional): Output file path. Default: .mega-linter.yml.
  • applyFixes (string, optional): Value for APPLY_FIXES. Default: none.
  • showElapsedTime (boolean, optional): Value for SHOW_ELAPSED_TIME. Default: true.
  • flavorSuggestions (boolean, optional): Value for FLAVOR_SUGGESTIONS. Default: false.
  • disableLinters (string[], optional): Values for DISABLE_LINTERS.
megalinter_list_flavors

Returns the built-in list of common flavors (all, javascript, python, terraform, and others).

megalinter_get_linters

Returns linter metadata from the built-in catalogue and supports targeted filtering.

Inputs:

  • language (string, optional): Filter by language (for example python, javascript, terraform).
  • securityOnly (boolean, optional): Return only security-focused linters.
  • autoFixOnly (boolean, optional): Return only linters with automatic fix capability.
megalinter_get_security_info

Returns security linters grouped into categories such as SAST, secrets, supply chain, container, and infrastructure.

Inputs:

  • None.
megalinter_get_reporters

Returns available MegaLinter reporters, including CI-targeted formats.

Inputs:

  • None.
megalinter_parse_reports

Parses MegaLinter report files from the reports directory.

Inputs:

  • reportsPath (string, optional): Report directory path. Default: megalinter-reports.
  • reportType (string, optional): Report type (json or sarif). Default: json.
megalinter_get_issue_summary

Summarises issues from megalinter-report.json and can apply severity/linter filters.

Inputs:

  • reportsPath (string, optional): Report directory path. Default: megalinter-reports.
  • severityFilter (string, optional): Filter results by severity (error, warning, info).
  • linterFilter (string, optional): Filter results by linter name.
megalinter_get_security_recommendations

Generates security

Only the beginning is shown; read the rest in the repo

Ask PopNx