About readyorai
readyorai is a local code-inspection MCP server and CLI that reports code-quality findings and actionable recommendations without changing files or making API calls. It supports deep AST analysis for several languages and heuristic checks for others.
Key features
- 01Nine code-quality analyzers
- 02AST analysis for five languages
- 03CLI and MCP access
- 04SARIF output and watch mode
- 05Baseline comparison and inline suppressions
Use cases
- 01Inspect files or directories for code-quality issues
- 02Monitor a project for new findings as files change
- 03Export findings for GitHub Code Scanning
- 04Compare results against a saved baseline
MCP support
The MCP server exposes tools to inspect files and directories, retrieve code metrics, compare file versions, and suggest fixes. It also provides review-code and health-check prompts.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEReadyOrAI
Zero-cost MCP server for local code inspection. Analyzes your code for clean code practices, best practices, and gives actionable recommendations — without modifying your code or making API calls.
Features
- 9 analyzers: complexity, naming, structure, patterns, imports, documentation, security, duplication, AI-generated code detection
- Multi-language: JS/TS, Python, Go, Rust (deep analysis) + Java, C#, Ruby, PHP, and more (regex-based)
- Zero-cost: All analysis runs locally — no API keys, no external calls
- MCP server: Works with Claude Desktop, Claude Code, and VS Code via stdio transport
- CLI tool:
ready @filenameandAIterminal commands for standalone use - SARIF output: Export results for GitHub Code Scanning integration
- Watch mode: Continuous re-analysis on file changes
- Baseline/diff mode: Track incremental adoption — only see new issues
- Config file: Project-level
.readyorai.jsonfor shared settings - Inline suppressions: Silence specific findings with
// readyorai-ignorecomments
Installation
As an MCP Server
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"readyorai": {
"command": "npx",
"args": ["-y", "readyorai"]
}
}
}
Claude Code:
claude mcp add readyorai -- npx -y readyorai
VS Code (.vscode/mcp.json):
{
"servers": {
"readyorai": {
"command": "npx",
"args": ["-y", "readyorai"]
}
}
}
As a CLI Tool
npm install -g readyorai
CLI Usage
ready @src/index.ts # Inspect a single file
ready @src/ # Inspect a directory
ready @src/index.ts --checks security,naming # Run specific checks
ready @src/index.ts --json # JSON output
ready @src/index.ts --sarif # SARIF output (GitHub Code Scanning)
ready @src/index.ts --severity warning # Only warnings and errors
ready @src/index.ts --watch # Re-analyze on file changes
ready @src/ --baseline baseline.json # Compare against saved baseline
ready @src/ --save-baseline baseline.json # Save current results as baseline
AI # Inspect current directory
AI @src/utils.ts # Alias with file target
Exit Codes
| Code | Meaning |
|---|---|
0 | No issues found |
1 | Warnings found |
2 | Errors found |
3 | Runtime error |
Configuration
Create a .readyorai.json in your project root:
{
"checks": ["complexity", "naming", "security"],
"severity": "warning",
"exclude": ["dist/**", "node_modules/**"]
}
Inline Suppressions
Silence specific findings on a line:
eval(code); // readyorai-ignore
MCP Tools
| Tool | Description |
|---|---|
inspect_file | Analyze a single file for code quality issues |
inspect_directory | Batch analysis of all source files in a directory |
get_metrics | Get quantitative metrics (LOC, complexity, function count) |
compare_files | Compare two file versions and show fixed, introduced, or unchanged findings |
suggest_fixes | Get actionable fix suggestions with context for each finding |
MCP Prompts
| Prompt | Description |
|---|---|
review-code | Structured code review with optional focus area |
health-check | Project-level health assessment |
Checks
| Check | What it detects |
|---|---|
complexity | Cyclomatic/cognitive complexity, deep nesting |
naming | Convention violations, single-letter vars, boolean prefixes |
structure | Long files/functions, too many parameters, long lines |
patterns | console.log, empty catch, magic numbers, nested ternaries, TODOs |
imports | Unused imports, wildcard imports, scattered imports |
documentation | Missing JSDoc/docstrings, low comment ratio |
security | Hardcoded secrets, eval(), SQL injection, XSS patterns |
duplication | Duplicate code blocks, repeated magic strings |
ai-detection | Detects patterns common in AI-generated code |
Language Support
| Tier | Languages | Analysis |
|---|---|---|
| 1 | JavaScript, TypeScript, Python, Go, Rust | Full AST-powered analysis |
| 2 | Java, C#, Ruby, PHP, Swift, Kotlin, C, C++ | Regex + heuristic analysis |
| 3 | Any text file | Line-based checks (length, TODOs, secrets, duplication) |
Development
git clone https://github.com/TedoNeObichaJavaScript/ReadyOrAI.git
cd ReadyOrAI
npm install
npm run build
npm test
Support
If you find ReadyOrAI useful, consider supporting the project:
- Borko — 5 euro
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.