renovate-mcp
An MCP server for designing Renovate configurations interactively. Point it at a local repo and let an LLM help you read, validate, preview, and save .
Potencialize seu agente
O comando do próprio publicador. Não é um endpoint do PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]O Claude Code não tem link de instalação para um comando local. Copie o comando abaixo e execute-o em um terminal.
claude mcp add renovate-mcp -- npx -y renovate-mcp@2.1.1Execute em um terminal.
{ "mcpServers": { "renovate-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
URL remota ou um comando na sua máquina? Como as duas instalações diferem
Rodar no PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDo publicador
An MCP server for designing Renovate configurations interactively. Point it at a local repo and let an LLM help you read, validate, preview, and save .
MCP server for designing Renovate configurations interactively.
renovate.jsonNeeds Node.js ≥ 24.11 on Linux or macOS. With Claude Code:
npm install -g renovate-mcp
claude mcp add renovate -s user -- renovate-mcp
claude mcp list # renovate should show as connected
Then try the prompt: "List the namespaces available under renovate://presets." A response listing config, docker, npm, … confirms the server is reachable. No tokens are needed for the offline tools. Other clients, tokens and upgrades are under Install below.
renovate.json*, expand every extends preset offline, and trace which preset set each field.managerFilePatterns glob/regex file selection, file/line hits and extracted dep info.Eighteen tools, seven resources, and four workflow prompts. Each tool name below links to its full reference in docs/tools.md.
Prompts. Four workflow prompts package the tool sequences above into ready-to-run starting points. Claude Code surfaces MCP prompts as slash commands (e.g. /mcp__renovate__design-renovate-config); other MCP clients expose them through their own prompt picker.
package.json declares "os": ["darwin", "linux"], so npm i surfaces an EBADPLATFORM warning on Windows and the server exits with a clear stderr message at startup. Use WSL2 or a Linux/macOS host instead.Renovate ships bundled — the renovate package is a runtime dependency, so validate_config, dry_run, and write_config work out of the box with no separate install. The offline tools (read_config, suggest_presets, resolve_config, explain_config, resolve_config_diff, test_package_rules, preview_custom_manager, lint_config, dry_run_diff, annotate_dry_run, explain_dependency, migrate_config) never spawn Renovate at all — nor do check_setup (by default it reads version metadata from the bundled install instead of spawning) or get_version (it only reports the renovate-mcp server's own version).
Optional env vars:
RENOVATE_BIN / RENOVATE_CONFIG_VALIDATOR_BIN — override the bundled binaries. When set, the override always wins.RENOVATE_MCP_REQUIRE_CLI=false — suppress the startup "partial availability" notice when you only intend to use the offline tools.docs/platform-setup.md for the per-platform matrix.GITHUB_COM_TOKEN — authenticates github.com datasource lookups (release notes, github-tags / github-releases / github-actions). Distinct from the platform token and never auto-derived from it; set it when github.com-hosted deps are resolved under the default dry_run platform: local. See docs/security.md.Heads up: MCP servers do not inherit your shell env. Set every env var via the
envkey in.mcp.json/claude_desktop_config.json. Seedocs/security.md.
npm install -g renovate-mcp
Install before you register the server. The package bundles Renovate (about 670 packages, 350 MB), so a client that starts npx -y renovate-mcp against a cold npm cache downloads all of that during server startup and can time out.
Upgrade with npm install -g renovate-mcp@latest and restart your client. With nvm or fnm, global packages belong to one Node version — reinstall after switching.
Claude Code:
claude mcp add renovate -s user -- renovate-mcp
-s user makes the server available in every project. Leave it out to register it for the current project only, or use -s project to write a shared .mcp.json.
Claude Desktop and other GUI clients don't load your shell's PATH, so with nvm, fnm or Homebrew they may find no Node or an older one. Use absolute paths:
which node # → "command"
echo "$(npm root -g)/renovate-mcp/dist/index.js" # → "args"
Claude Desktop reads ~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"renovate": {
"command": "/Users/you/.nvm/versions/node/v24.14.1/bin/node",
"args": ["/Users/you/.nvm/versions/node/v24.14.1/lib/node_modules/renovate-mcp/dist/index.js"]
}
}
}
Any other client that can launch a stdio MCP server works with the same command.
The offline tools need nothing. Add env vars only for what you use:
Self-hosted GitLab and GitHub Enterprise also need RENOVATE_ENDPOINT — see Platform setup.
In Claude Code, re-register with -e:
claude mcp remove renovate -s user
claude mcp add renovate -s user -e GITHUB_COM_TOKEN=ghp_xxx -- renovate-mcp
-e stores the value in plain text in ~/.claude.json. Keep tokens in user or local scope, never in a project-scope .mcp.json that gets committed.-e accepts several values, so keep the -- before renovate-mcp."env": { … } block next to "args".npx -y renovate-mcp instead, after warming the npm cache once with npm exec --yes --package=renovate-mcp -- node -e 0.curl -fsSL https://raw.githubusercontent.com/tibuntu/renovate-mcp/main/install.sh | bash runs steps 1 and 2 interactively: it checks Node, asks for npx or global mode, verifies the server with an MCP initialize handshake, and registers it via claude mcp add when the Claude Code CLI is on PATH. Flags (after bash -s --): --global, --npx, --no-mcp-add, --mcp-scope=user|project|local, --version=X.Y.Z; also accepted as env vars (RENOVATE_MCP_GLOBAL=1, RENOVATE_MCP_NO_MCP_ADD=1, RENOVATE_MCP_VERSION=…).npm install && npm run build, and point your client at node /absolute/path/to/renovate-mcp/dist/index.js.For dry_run against a remote platform or resolve_config with externalPresets: true:
The Gitea / Forgejo / Bitbucket Cloud rows apply to the resolve_config family only: dry_run runs Renovate as local / github / gitlab and never reads those tokens. Pass platform (gitea / forgejo / bitbucket) and endpoint as tool inputs instead of RENOVATE_PLATFORM / RENOVATE_ENDPOINT.
See docs/platform-setup.md for a worked self-hosted GitLab example, local> preset handling, and private-registry credentials.
Once the server is wired up, try prompts like these. Written for Claude but work with any MCP-capable client.
Understanding an existing config
presetsUnresolved, with the reason for each."prCreation set to not-pending? Use explain_config to trace which preset set it."Discovering & browsing presets
../renovate-presets repo too, and draft a config I can validate."config namespace." (uses the renovate://presets/config sub-resource — cheaper than pulling the whole index)config:recommended actually enable? Show me its expanded JSON."suggest_presets with that intent)Self-hosted GitLab / GitHub Enterprise (env set per Platform setup)
gitlab>platform/renovate-presets from our self-hosted GitLab at https://gitlab.example.com/api/v4. Route local> presets through the same host."github>acme/renovate-config//base from our GitHub Enterprise at https://github.acme.corp/api/v3."infrastructure/kubernetes/our-platform (a nested-group GitLab project) so Renovate can fetch the local> presets the config extends."Authoring a custom manager (regex or JSONata)
# renovate: datasource=docker depName=... comments above image tags in my Dockerfiles. Draft a customManagers regex entry with managerFilePatterns: ["**/Dockerfile"] and preview it against this repo so I can see what it extracts."customManagers entry — preview it and tell me which files match managerFilePatterns, which lines hit each matchStrings regex, and what dep info gets extracted."fileMatch. Lint the config, then run migrate_config so it becomes managerFilePatterns."customType: \"jsonata\" customManager with fileFormat: \"yaml\" to extract Helm chart dependencies (name, version, repository) from Chart.yaml, and preview it against this repo."Validating, previewing, saving
lodash? Run a dry run and explain that dependency.":semanticCommits to my extends, validate it, and save back to renovate.json."A transcript-style walkthrough: design a Dockerfile custom manager from scratch, validate it, dry-run, and save. Turns are abbreviated — your client will show the actual tool-call JSON.
You: I've got
# renovate: datasource=docker depName=<image>comments aboveFROMlines in my Dockerfiles. Draft acustomManagersentry and preview it against this repo.Claude calls
preview_custom_managerwith a first-draftmanagerFilePatterns(**/Dockerfile) +matchStrings. → 4 Dockerfiles matchedmanagerFilePatterns, 0 lines matchedmatchStrings. The regex anchored onARG, but the Dockerfiles useFROM.You: Rewrite
matchStringsto anchor on the renovate comment, thenFROM <image>:<version>on the next line.Claude calls
preview_custom_manageragain with the fixed regex. → 4 files, 4 line hits. Extracted:postgres:15.3-alpine,redis:7.2,nginx:1.25,node:20.11. Named groupsdepNameandcurrentValuepopulated on every hit.You: Good. Validate the full config inline, with this
customManagersentry alongside my existingextends.Claude calls
validate_configwith the inline config. → valid.You: Now dry-run so I can see what Renovate would actually open.
Claude calls
dry_run. → 2 updates:postgres15.3-alpine → 15.5-alpine,redis7.2 → 7.4. No entries inproblems.You: Save it.
Claude calls
write_configonrenovate.json. → validated, written atomically; because the file already existed and parsed as JSON-with-comments, the round-trip serializer preserved the surrounding comments and key order — only thecustomManagersslice was edited in place.
npm run dev # build watch mode
npm run typecheck # tsc --noEmit
npm run build # compile to dist/
npm start # run the built server over stdio
npm test # vitest run (builds first)
npm run test:watch # vitest watch mode
npm run test:coverage # vitest run --coverage
npm run generate:presets # regenerate src/data/presets.generated.ts
npm run generate:managers # regenerate src/data/managers.generated.ts
npm run generate:migrations # regenerate src/data/migrations.generated.ts
npm run generate:options # regenerate src/data/options.generated.ts
npm run generate:datasources # regenerate src/data/datasources.generated.ts
npm run sync:jsonata-pin # sync package.json's jsonata pin to Renovate's own
npm run check:snapshot-versions # fail if any src/data/*.generated.ts is stale vs installed renovate
See docs/development.md for snapshot-file mechanics, CI matrix, the nightly upstream-drift workflow, dependency review, and integration-test setup.
docs/tools.md — full per-tool reference with all inputs, outputs, and edge cases.docs/platform-setup.md — per-platform env vars, worked example, local> presets, private-registry credentials.docs/security.md — token handling, env-var precedence, endpoint allowlist, redirect/body-cap policy, inline-secrets warning.docs/operations.md — timeouts, caps, large-report escape hatch, ok semantics, RE2 / nodeEnv handling, progress notifications.docs/architecture.md — shell-out vs import, worker isolation, round-trip writer, preset catalogue.docs/development.md — snapshot mechanics, CI matrix, nightly drift workflow, integration testing.renovate.json. Use the real Renovate for the actual dependency-update pipeline.resolve_config merges faithfully. Preset expansion runs offline against a committed snapshot, then folds with Renovate's real mergeChildConfig in a worker thread — mergeQuality: "faithful" (it falls back to an approximate in-process merge as "preview" only if the worker is unavailable). Template substitution still implements only positional {{argN}} placeholders — non-positional tokens and Handlebars helpers are flagged in warnings and pass through verbatim. For full config resolution (datasource lookups, etc.), run dry_run.preview_custom_manager is a subset of Renovate's custom managers. It covers customType: "regex" (with matchStringsStrategy of any / combination / recursive) and customType: "jsonata" (with fileFormat: "json" | "yaml" | "toml"). File selection follows Renovate's managerFilePatterns semantics (globs or /regex/, entries unioned like Renovate's extract phase); the deprecated fileMatch is still accepted with a warning. Template substitution is {{groupName}} only — full Handlebars helpers/conditionals are not implemented. Other custom types (e.g. html) are out of scope. Use it for fast iteration; confirm with dry_run. Full coverage matrix in docs/tools.md#preview_custom_manager.dry_run still uses fake binaries in CI. The bundled Renovate is available (it's a runtime dependency), and validate_config / write_config have real-validator integration tests (test/integration/realValidator.test.ts) exercising the actual bundled renovate-config-validator — but dry_run itself still runs per-PR against fake binaries via RENOVATE_BIN / RENOVATE_CONFIG_VALIDATOR_BIN env overrides, for determinism and speed. A separate nightly workflow re-runs the full suite against renovate@latest end-to-end. Run dry_run locally against a real config to validate behaviour.MCP server for designing Renovate configurations interactively.
{ "mcpServers": { "renovate-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Ferramentas
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Este registro não lista nenhuma variável de ambiente obrigatória.
Renovate roda localmente via stdio.
Última verificação: 2026-11-16. MCP server for designing Renovate configurations interactively.