pickfit

BrowseMCP servers

renovate-mcp

MCP server to read, validate, preview and save Renovate configs interactively.

Tested on Linux

Use it

Linux x86_64

You need first

  • Runtimes: Node.js ≥ 24.11
  1. npm install -g renovate-mcp@1.7.1

    npm install -g renovate-mcp@1.7.1

Add it to your agent

claude mcp add renovate-mcp -- renovate-mcp
JSON for Claude Desktop, Cursor and other clients
{
  "mcpServers": {
    "renovate-mcp": {
      "command": "renovate-mcp",
      "args": []
    }
  }
}

Add renovate-mcp as an MCP server in your MCP client, then ask the client to call check_setup or read_config on your repository.

What it does

  • Read and explain Renovate configs
    How to use it
    1. Ask your MCP client to call the read_config tool with repoPath set to <your repo path>.
    2. Read the returned text to see the repository's Renovate config.
    Tested
  • Find presets that match what you want
    How to use it
    1. Ask your MCP client to call the suggest_presets tool with query set to <what you want Renovate to do>.
    2. Review the suggested presets in the returned text.
    Tested
  • Preview what a custom manager would match
    How to use it
    1. Ask your MCP client to call the preview_custom_manager tool with repoPath set to <your repo path>.
    2. Pass a manager object with customType "regex", managerFilePatterns such as <file pattern>, and matchStrings with your regex.
    3. Read the returned text to see what the manager finds in your repository.
    Tested
  • Validate and lint configs
    How to use it
    1. Ask your MCP client to call the validate_config tool with configContent set to <your config object>.
    2. Call the lint_config tool with the same configContent to check for problems.
    Tested

How far pickfit got

Linux x86_64

  1. Installs
  2. Connects
  3. 4 of 4 features work
  4. Works offline

macOS: the project says it runs there; pickfit hasn’t tried it.

Good for

  • expand extends presets and trace which preset set each field
  • validate a Renovate config against schema
  • dry-run Renovate to preview which PRs would open
  • preview custom manager regex against local repo
  • validate and atomically write config to disk

How pickfit tested it

Each run starts from a clean machine and follows the steps above. How pickfit verifies

Linux x86_64

An MCP client called one of its tools

  • Replayed from scratch
  • Works offline
  • Checked on 31 Oct 2026
  • Version 1.7.1

An MCP client handshake over stdio listed 18 tools, and a call to read_config returned a result.

Differences the test machine hit

  • README: Requires Node.js ≥ 24.11
    In the test: Server installed and handshaked successfully on Node 22.23.4 with EBADENGINE warnings only

How to read a tool card

Stitching
pickfit installed this tool itself. Everything under the stitches comes from that run. A tool pickfit has not run never gets stitches.
Verified on your OS
The install steps ran on the system you chose. “Ran on Linux only” means it has not been run on yours yet.
macOS, Linux and WindowsWhere it ran
Green OS marks: pickfit ran the install steps there. Grey ones: the README says it runs there, and pickfit has not tried.
How far the run got
Installs and starts, its main function works, its service answers, it produces model output. A window means a desktop app opened; a plug, an MCP client used it. The mark sits beside the run’s result, under “Why it fits and how we know” and in “How pickfit tested it”.
Visual check
pickfit looked at screenshots of the app. Green: it looks right. Amber with a number: things that look wrong; open it to see them. Grey and dashed: not checked yet.
Known vulnerabilities
Known high or critical vulnerabilities (OSV.dev) in what it installs. Green: none known. Red with a number: how many; open it for the list, and read it before you install. Grey and dashed: not checked, which does not mean safe.
About the run
The day it ran, and the version that ran.
Source of a reason
Every reason a pick fits rests on one profile field. Open the reason to see the field and the value it relies on.
Hidden gem
High quality, little known.
Quality and popularity
Two scores out of 100. Quality: how well it installed and worked when pickfit tried it, and how good its install docs and upkeep are. Popularity: from stars, downloads and Hacker News.
Features checked
Of the main features the README advertises, how many the run actually exercised (green), and how many failed (red). Grey ones were not checked, and the card says why.
Not verified
A well-known tool Fitz mentions from general knowledge. No run record, no steps, no score.