
rrubocop
io.github.adrianovPublished by GitHub account adrianovv0.8.17Updated Oct 29, 2026
Fast RuboCop-compatible Ruby linter with MCP inspect and autocorrect tools.
Overview
A fast RuboCop-compatible Ruby linter that runs as a local MCP server, letting an assistant lint and autocorrect Ruby code while it edits.
- What you can do
- Lint Ruby files or inline source code and get LSP-shaped offense JSON, with paths resolved against the project's .rubocop.yml
- Autocorrect offenses, either safe-only or all, writing changes back to files when a filesystem path is given
- Apply the same RuboCop-compatible config resolution, cop set and output formats as the CLI, including Rails, RSpec, Performance and GraphQL cops
- When to use it
- Useful when an assistant edits Ruby or Rails projects and should see offenses in the same turn and fix them immediately, rather than waiting for a later CLI or CI pass.
- Requirements
- A local rrubocop binary installed via Homebrew, cargo or a release package, launched with the --mcp flag over stdio. No Ruby runtime is needed for linting or simple ERB; unsupported ERB falls back to ruby or bundle exec ruby. No accounts, API keys or environment variables are declared.
Installation
In SourceWeft
- Open rrubocop in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
rrubocop
10x faster RuboCop drop-in — same CLI, .rubocop.yml, and offense output, without maintaining RuboCop gems. Linting and simple config need no Ruby; complex ERB still does. Point it at an existing project and use it like RuboCop.
One binary — runs the same way regardless of rbenv, rvm, system Ruby, or Docker. Uses tree-sitter; no Ruby runtime required for linting or simple ERB. Unsupported ERB falls back to ruby / bundle exec ruby.
Drop-in parity: reads your existing .rubocop.yml, emits RuboCop-like text/JSON, supports -a/-A autocorrect, and grows cop coverage over time.
Baseline (shown in --help / --version): rubocop 1.91.0 with rubocop-rails 2.37.0, rubocop-performance 1.27.0, rubocop-rspec 3.9.0, rubocop-rspec_rails 2.32.0, rubocop-factory_bot 2.28.0 — pinned in src/resources/baseline.json.
Parity runs have been verified over 600+ installed Ruby gem projects (RuboCop vs rrubocop on the same trees).
Install
macOS (.tar.gz from GitHub Releases; binary + man):
Ubuntu / Debian (.deb from GitHub Releases; amd64, Ubuntu 22.04+ / Debian bookworm+):
Features
- Config — RuboCop-compatible resolution: walk-up discovery,
inherit_from/inherit_gem/require/plugins,inherit_mode(merge/override), nested.rubocop.ymloverrides,DisabledByDefault,NewCops/Enabled: pending, plus per-copEnabled/Exclude/Include/ options; public gem defaults/inherit_gemYAML are vendored by version (fromGemfile.lock, withsame_asaliases when YAML is identical) and parsed in memory; private/unlisted gems fall back tobundle info --path; simple ERB in YAML expands natively (Ruby only for unsupported tags) - Autocorrect —
-a(safe) /-A(all) - Output —
progress(marks stream as files finish),text,json,github,quiet,files, … (TTY color like RuboCop;--color/--no-color) - Directives —
# rubocop:disable/enable - Parser — tree-sitter-ruby (no Prism / no CRuby)
- Cache — content-addressed
cache.redbunder$RRUBOCOP_CACHE_DIRor$XDG_CACHE_HOME/rrubocop/~/.cache/rrubocop(same style as abcop);--cache falseskips reads but still writes - Prefer MCP with LLMs.
rrubocop --mcpis the best way to use rrubocop from an agent: the model gets offenses as soon as it writes, so it can fix and autocorrect in the same turn and ship effective code right away — not after a later CLI/CI pass. Official RustrmcpSDK; same tools as RuboCop 1.85+:rubocop_inspectionandrubocop_autocorrection
Reference implementations: nitrocop (architecture & fixtures), upstream RuboCop.
Built-in cops
Departments grow breadth-first from common RuboCop plugin sets (nitrocop / gem sources). Notable coverage:
Use rrubocop --list-cops for the full registered set, and rrubocop --list-autocorrectable-cops for cops with -a/-A support (181 with autocorrect so far; Layout complete; Style/Lint/Rails/RSpec growing).
Usage
Exit codes: 0 clean, 1 offenses at/above --fail-level, 2 error.
MCP (Model Context Protocol)
Preferred for LLM / agent workflows. Wire rrubocop as an MCP server so the model can call rubocop_inspection / rubocop_autocorrection while it edits: feedback arrives in the same turn, the agent corrects soon, and it writes clean code on the first pass instead of discovering offenses only in CI.
rrubocop --mcp runs a long-lived MCP server on stdio — same idea as RuboCop’s MCP, with no Ruby mcp gem. Tools:
Always pass path or paths (absolute file or directory preferred; path may be a string or an array). The server walks up from the first target to find .rubocop.yml. Omitting targets for filesystem ops errors out (avoids scanning $HOME when MCP cwd is mis-set). Files without a recognized Ruby extension, filename, or shebang (e.g. YAML/JSON configs) are silently skipped — same as upstream MCP, whose TargetFinder runs in :only_recognized_file_types mode — so passing mixed paths yields no Lint/Syntax noise; summary.target_file_count reflects inspected files only. A long-lived global MCP started from $HOME otherwise inherits ~/.rubocop.yml (AllCops: Enabled: false is common) and misses project cops such as RSpec/ExampleLength.
- MCP Registry name:
mcp-name: io.github.adrianov/rrubocop
Metadata lives in server.json (Cargo package on crates.io). Each v* tag publishes that listing to the MCP Registry.
Example client config (Cursor / VS Code / Windsurf):
Claude Code:
Intended for MCP clients, not interactive use.
Caching
Content-addressed cache under $RRUBOCOP_CACHE_DIR (or $XDG_CACHE_HOME/rrubocop / ~/.cache/rrubocop). Keys cover contents, version, rule revision, --only/--except, --rubocop-version, config fingerprint, and path. Auto-pruned to 20 000 entries; --cache false skips reads but still writes. Autocorrect runs bypass the cache. Nothing is written inside the project.
Benchmarks
Cold lint (cache off) on a large Rails codebase (~3.8k Ruby files), same host:
rrubocop is ≈ 22× faster wall clock than RuboCop (156.6s / 7.0s) on the same clean result. RuboCop user time was 155s; rrubocop used 71s of CPU across cores.
nitrocop caveat: out of the box it did not honor the same disabled cops / custom rules / gem configs as bundle exec rubocop (e.g. failed inherit_gem load, skipped/unimplemented cops), so it reported ~21k false positives vs RuboCop/rrubocop’s clean run. Matching that baseline needs extra setup (--migrate, plugin/config wiring). Treat the 8.9s figure as raw throughput only, not drop-in parity.
Cold lint (cache off) on rails/rails (main, RuboCop 1.79.2 via bundle exec), same host (4 cores), both clean (0 offenses). Two runs averaged:
≈ 12× faster wall clock (67.254s / 5.668s). RuboCop user time was 66.9s; rrubocop used 20.2s of CPU across cores.
Same host, cold --cache false, offense-set parity on Active Support and Active Record (fp=0, fn=0 on shared .rb files):
Cold lint on a fresh rails new app (Rails 8.1.3.1, default rubocop-rails-omakase via inherit_gem, RuboCop 1.90.0 via bundle exec), plus scaffold/model/mailer/job generators (41 identical target files). Offense-set parity fp=0, fn=0 (both clean). Two-run average:
Cross-test vs nitrocop
With a local nitrocop build:
Compares (path, line, cop_name) offense sets.
License
GPL-3.0-or-later. See NOTICE for MIT attribution of nitrocop-derived design/logic.
Source: README.md at commit 0b67072
Tools
0Version history
10- v0.8.17LatestOct 29, 2026
- v0.8.16Oct 11, 2026
- v0.8.15Oct 1, 2026
- v0.8.14Sep 30, 2026
- v0.8.13Sep 30, 2026
- v0.8.12Sep 30, 2026
- v0.8.11Sep 24, 2026
- v0.8.10Sep 22, 2026
- v0.8.9Sep 18, 2026
- v0.8.8Sep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts