code-quality-mcp
Provides code quality analysis for Angular projects, including unused code detection and AI-powered deep analysis.
Provides code quality analysis for AWS Amplify projects, supporting both fast and deep analysis modes.
Provides code quality analysis for Firebase projects, including security checks and complexity analysis.
Provides code quality analysis for NestJS projects, with smart summaries and quick win suggestions.
Provides code quality analysis for .NET projects, including logic-based and AI-powered checks.
Provides code quality analysis for Next.js projects, with support for pagination and trend tracking.
Provides code quality analysis for Node.js projects, including fast mode for CI/CD and deep mode for code reviews.
Provides code quality analysis for React and React Native projects, with smart ignore patterns for build artifacts.
Provides code quality analysis for TypeScript projects, including unused code detection and complexity analysis.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@code-quality-mcp Give me a smart summary of the code quality for my project"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
š Code Quality MCP Server
Hybrid Code Quality Analysis - Combines logic-based checks with AI-powered deep analysis
MCP (Model Context Protocol) system for code quality analysis. Supports two modes:
ā” Fast Mode: Quick logic-based checks
š¤ Deep Mode: AI-powered deep analysis (Claude)
š§ Installation
npm install
npm run buildRelated MCP server: Tech Debt MCP Server
ā¶ļø Running the Server
Option 1: Direct Run
npm startOption 2: Via Claude Desktop
Add to ~/.config/Claude/claude_desktop_config.json:
{
"mcpServers": {
"code-quality": {
"command": "node",
"args": ["/absolute/path/to/code-quality-mcp/dist/index.js"]
}
}
}š API Tools
š Analysis Tools
1. check_quality - Full Code Quality Check
{
"tool": "check_quality",
"arguments": {
"projectPath": ".",
"deepAnalysis": false, // true = AI mode
"checkUnusedCode": true,
"checkComplexity": false, // requires AI
"checkSecurity": false, // requires AI
"page": 1, // pagination
"pageSize": 50 // items per page
}
}Returns: Complete list of issues with pagination
š” Smart Tools (Recommended!)
2. get_smart_summary - Smart Summary ā
Instead of 500 issues, get a focused summary:
{
"tool": "get_smart_summary",
"arguments": {
"projectPath": "."
}
}Returns:
š Score: 68/100
š Issues: 500 (120 critical)
ā±ļø Fix Time: 2 days
š„ Top Problems:
⢠unused-code: 300 (60%)
⢠security: 50 (10%)
š Hotspot Files:
š“ UserService.ts - 45 issues3. get_quick_wins - Quick Wins ā”
Get only actions that provide maximum impact in minimum time:
{
"tool": "get_quick_wins",
"arguments": {
"projectPath": "."
}
}Returns:
ā” Quick Wins:
1. Remove 50 unused vars (10 min) ā +15 points
2. Fix 30 console.log (5 min) ā +8 points
3. Translate Hebrew comments (15 min) ā +5 points
Total: 30 minutes ā +28 points!4. get_trends - Progress Tracking š
See how code quality improves over time:
{
"tool": "get_trends",
"arguments": {
"projectPath": "."
}
}Returns:
š Trends:
ā
Score: 45 ā 68 (+23)
ā
Fixed: 120 issues
ā ļø New: 15 issues
Improving:
⢠unused-code: 300 ā 180 (-120)
⢠security: 10 ā 5 (-5)
Degrading:
⢠code-style: 50 ā 65 (+15)š§ Other Tools
5. analyze_project - Project Type Detection
{
"tool": "analyze_project",
"arguments": {
"projectPath": ".",
"deep": true
}
}6. get_recommendations - Quick Recommendations
{
"tool": "get_recommendations",
"arguments": {
"projectPath": ".",
"language": "en" // or "he" for Hebrew
}
}ā” Fast vs Deep Mode
Feature | Fast Mode | Deep Mode |
Speed | ~20ms | ~1000ms |
Cost | Free | API calls |
Accuracy | Good | Excellent |
AI insights | ā | ā |
When to use Fast Mode:
During development
Before commits
In CI/CD pipelines
When to use Deep Mode:
Before Pull Requests
Code reviews
Security audits
š Examples
HOW_TO_USE.md - šÆ How to use this MCP in Claude (commands, examples)
examples/usage-examples.ts - Complete API examples
š Supported Platforms
Node.js / TypeScript
React / React Native
Next.js / NestJS
Firebase / AWS Amplify
Java / .NET / Angular
š Key Features
ā Smart Ignore Patterns - Automatically skips:
node_modules,build,dist,.gitReact Native:
android/gradle,ios/Pods, native build foldersOnly scans your code, not auto-generated files
ā Pagination - Handle large projects with many issues
ā Smart Summaries - Get actionable insights instead of overwhelming lists
ā Quick Wins - Find high-impact, low-effort fixes
ā Trend Tracking - Monitor code quality improvements over time
Built with ā¤ļø using MCP and Claude
Available Tools
6 toolsanalyze_projectC
Analyze project type and code quality
Inputs: projectPath (required), deep.
check_qualityC
Check code quality based on project type. Supports both fast (logic-based) and deep (AI-powered) analysis modes.
Inputs: projectPath (required), page, pageSize, aiEnabled, +5 more.
get_quick_winsB
Get high-impact, low-effort fixes to quickly improve code quality score
Inputs: projectPath (required).
get_recommendationsC
Get code quality recommendations
Inputs: projectPath (required), language.
get_smart_summaryB
Get a concise, actionable summary of code quality instead of full issue list
Inputs: projectPath (required).
get_trendsA
See how code quality is improving or degrading over time
Inputs: projectPath (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogā¦
TDQS
Scored across 6 tools
analyze_project and check_quality overlap in purpose, both analyzing project type and quality. The get_recommendations, get_smart_summary, and get_quick_wins tools are related but distinct in output style, so disambiguation is moderate.
All tool names consistently follow a verb_noun pattern (analyze_project, check_quality, get_recommendations, etc.). The use of get_ for most retrieval functions is uniform and predictable.
Six tools is within the ideal 3-15 range for a focused code-quality server. Each tool addresses a specific aspect of the domain without bloat.
The tool set covers analysis, quality checking, recommendations, summaries, quick wins, and trends, providing a comprehensive view of code quality. Missing a raw issue list or fix application is a minor gap, but agents can work around it via the existing tools.
Maintenance
Related MCP Connectors
AI-powered codebase analysis ā call graphs, security, dead code, complexity. 150+ tools.
Enterprise code intelligence for M&A, security audits, and tech debt. Hosted server with 200k free.
30+ deterministic dev and delivery tools: linting, metrics, diagrams, model advice, AI-text checks.
Code intelligence platform for AI agents. 20 tools for architecture, security & impact analysis.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides comprehensive codebase analysis including project structure evaluation, cross-language duplicate detection, microservices validation, and configuration optimization with AI-powered pattern learning that generates actionable improvement reports.MIT
- AlicenseAqualityDmaintenanceA server for analyzing technical debt across multiple programming languages, integrating with MCP-compatible tools to detect code quality issues and provide prioritized recommendations.1673 npm7MIT
- AlicenseAqualityBmaintenanceAn MCP server that provides local code quality analysis for AI coding assistants, supporting file analysis, git diff review, and full project scanning with quality scoring.538 PyPI3MIT
- FlicenseNot gradedqualityDmaintenanceAI-powered code quality analysis that detects security issues, bugs, code smells, and performance problems across multiple languages.4-