Mirdan
AI Code Quality Orchestrator - Automatically transforms developer prompts into high-quality, structured requests that maximize AI coding assistant capabilities.
The Problem
AI coding assistants produce "slop" not because the models are incapable, but because developers provide prompts that lack context, structure, and quality constraints. Research shows properly structured prompts achieve 15-74% better results.
The Solution
Mirdan is an MCP server that intercepts prompts, automatically enhances them with quality requirements, codebase context, and architectural patterns, then intelligently orchestrates other available MCPs to ground the AI in reality.
Features
- Intent Analysis: Classifies task type (generation, refactor, debug, review, test)
- Quality Injection: Applies language-specific coding standards and security requirements
- Prompt Composition: Structures prompts using proven frameworks (Role/Goal/Constraints)
- MCP Orchestration: Recommends which tools to use for context gathering
- Verification Checklists: Generates task-specific verification steps
Installation
Prerequisites
- Python 3.11 or higher
- uv (recommended) or pip
From PyPI (Recommended)
# Using uv (recommended)
uv pip install mirdan --system
# Or using pip
pip install mirdan
# Verify installation
mirdan --help
From Source (Development)
# Clone the repository
git clone https://github.com/S-Corkum/mirdan.git
cd mirdan
# Install dependencies
uv sync
# Run from source
uv run mirdan
Quick Start
# 1. Add mirdan to Claude Code
claude mcp add mirdan -- uvx mirdan
# 2. Verify connection
# In Claude Code, run: /mcp
# Mirdan should appear in the connected servers list
Next steps: See the Claude Code Integration section below for automatic orchestration setup.
For other MCP clients (Cursor, Claude Desktop), see MCP Configuration Reference.
Claude Code Integration
Claude Code provides multiple integration points for maximizing mirdan's effectiveness. This section covers all available methods from simple to advanced.
Automatic Orchestration
Mirdan works best when it automatically enhances every coding task. Claude Code offers several integration levels:
| Level | Method | Effort | Enforcement |
|---|---|---|---|
| Basic | CLAUDE.md | Copy-paste | Soft (instructions) |
| Standard | CLAUDE.md + Slash Commands | Copy-paste | Medium (explicit trigger) |
| Advanced | CLAUDE.md + Hooks | Configuration | Hard (automatic checks) |
| Enterprise | Managed Settings + Hooks | IT deployment | Mandatory |
Level 1: CLAUDE.md Instructions (Recommended Start)
Add these instructions to your project's CLAUDE.md file. Claude will automatically follow them for all coding tasks.
File location: ./CLAUDE.md (project) or ~/.claude/CLAUDE.md (global)
## Mirdan Code Quality Orchestration
When performing ANY coding task (writing, editing, debugging, refactoring code), follow this workflow:
### 1. Entry Point (REQUIRED)
Before writing any code, call `mcp__mirdan__enhance_prompt` with the task description.
Use the response to guide your work:
- `detected_frameworks` → query context7 for documentation if unfamiliar
- `touches_security` → use stricter validation in step 3
- `quality_requirements` → follow these during implementation
- `tool_recommendations` → use suggested MCPs for context gathering
### 2. Implementation
Write code following the quality_requirements from step 1.
### 3. Exit Gate (REQUIRED)
Before marking any coding task complete, call `mcp__mirdan__validate_code_quality` with your code.
- Set `check_security=true` if `touches_security` was true in step 1
- If validation fails, fix all violations and re-validate
- Code is NOT complete until validation passes
### 4. Verification
Call `mcp__mirdan__get_verification_checklist` for the task type and execute each item.
Level 2: Slash Commands (Explicit Control)
Create custom slash commands for different workflows. Slash commands provide explicit triggers with full context.
/code - General Coding Tasks
File: .claude/commands/code.md
---
description: Execute coding task with mirdan quality orchestration
allowed-tools: Read, Edit, Write, Bash(*), Grep, Glob
---
Execute this coding task with full mirdan orchestration:
$ARGUMENTS
## Workflow
1. **Entry Gate**: Call `mcp__mirdan__enhance_prompt` with the task above
2. **Context Gathering**:
- Use `detected_frameworks` to query context7 for documentation
- Use `tool_recommendations` for additional MCP calls
3. **Implementation**: Follow `quality_requirements` during coding
4. **Exit Gate**: Call `mcp__mirdan__validate_code_quality` on completed code
- Set `check_security=true` if `touches_security` was true
- Fix violations and re-validate until passed
5. **Verification**: Call `mcp__mirdan__get_verification_checklist` and complete each item
Code is NOT complete until validation passes and checklist is done.
Usage:
/code implement user authentication with JWT tokens
/debug - Debugging Tasks
File: .claude/commands/debug.md
---
description: Debug issue with mirdan quality gates
allowed-tools: Read, Edit, Write, Bash(*), Grep, Glob
---
Debug this issue with mirdan orchestration:
$ARGUMENTS
## Workflow
1. **Classify**: Call `mcp__mirdan__analyze_intent` to understand security implications
2. **Investigate**: Analyze the issue thoroughly
3. **Fix**: Implement the fix
4. **Validate**: Call `mcp__mirdan__validate_code_quality` with `check_security=true`
(bugs often have security implications)
5. **Verify**: Call `mcp__mirdan__get_verification_checklist(task_type="debug")` and complete each item
Fix is NOT complete until validation passes.
/review - Code Review
File: .claude/commands/review.md
---
description: Review code with mirdan quality standards
allowed-tools: Read, Grep, Glob
---
Review this code with mirdan quality standards:
$ARGUMENTS
## Workflow
1. **Standards**: Call `mcp__mirdan__get_quality_standards` for the detected language
2. **Validate**: Call `mcp__mirdan__validate_code_quality` on the code
3. **Checklist**: Call `mcp__mirdan__get_verification_checklist(task_type="review")`
4. **Report**: Provide findings organized by:
- Security issues (critical)
- Quality violations
- Improvement suggestions
Level 3: Hooks (Automatic Enforcement)
Hooks provide automatic enforcement without requiring explicit commands. They run before or after specific tool calls.
Pre-Implementation Reminder
Reminds to use mirdan before writing code. Add to .claude/settings.json:
{
"hooks": {
"PreToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "prompt",
"prompt": "Before modifying code, ensure you've called mcp__mirdan__enhance_prompt for the current task. Have you done this?",
"timeout": 30
}
]
}
]
}
}
Post-Implementation Validation Gate
Automatically prompts for validation after code changes:
{
"hooks": {
"PostToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "prompt",
"prompt": "Code was just modified. Run mcp__mirdan__validate_code_quality on the changes before proceeding. If security-related code, use check_security=true.",
"timeout": 30
}
]
}
]
}
}
Combined Hooks Configuration
File: .claude/settings.json
{
"hooks": {
"SessionStart": [
{
"matcher": "",
"hooks": [
{
"type": "command",
"command": "echo '🔷 Mirdan code quality orchestration active'",
"timeout": 5
}
]
}
],
"PreToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "prompt",
"prompt": "Ensure mcp__mirdan__enhance_prompt was called for this task before writing code.",
"timeout": 30
}
]
}
],
"PostToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "prompt",
"prompt": "Code modified. Call mcp__mirdan__validate_code_quality before proceeding.",
"timeout": 30
}
]
}
]
}
}
Level 4: Project Rules (Path-Specific Enforcement)
Use .claude/rules/ for path-specific quality requirements.
Security-Critical Paths
File: .claude/rules/security.md
---
paths: ["**/auth/**", "**/security/**", "**/crypto/**", "**/*token*", "**/*session*"]
---
# Security-Critical Code Rules
This file is in a security-sensitive path. STRICT validation required.
## Mandatory Workflow
1. Call `mcp__mirdan__enhance_prompt` - task WILL be flagged as `touches_security=true`
2. Call `mcp__mirdan__get_quality_standards` with security focus
3. Implement with security-first mindset
4. Call `mcp__mirdan__validate_code_quality` with:
- `check_security=true` (REQUIRED)
- Address ALL security findings before completion
5. Complete full verification checklist
NO EXCEPTIONS. Security code is not complete until validation passes with zero security findings.
API Code Rules
File: .claude/rules/api.md
---
paths: ["**/api/**", "**/routes/**", "**/endpoints/**", "**/handlers/**"]
---
# API Code Rules
API code requires input validation and error handling verification.
## Workflow
1. `mcp__mirdan__enhance_prompt` - include "API endpoint" in task description
2. `mcp__mirdan__get_quality_standards` for the language
3. Implement with:
- Input validation for all external data
- Proper error responses
- Authentication/authorization checks
4. `mcp__mirdan__validate_code_quality` with `check_security=true`
5. Complete verification checklist
Project Settings
Configure mirdan-related settings in .claude/settings.json:
{
"permissions": {
"allow": [
"mcp__mirdan__enhance_prompt",
"mcp__mirdan__validate_code_quality",
"mcp__mirdan__get_quality_standards",
"mcp__mirdan__analyze_intent",
"mcp__mirdan__suggest_tools",
"mcp__mirdan__get_verification_checklist"
]
},
"enableAllProjectMcpServers": true,
"enabledMcpjsonServers": ["mirdan"]
}
Enterprise Deployment
For organization-wide mirdan enforcement, IT can deploy managed configuration.
Managed MCP Configuration
File (macOS): /Library/Application Support/ClaudeCode/managed-mcp.json
File (Linux): /etc/claude-code/managed-mcp.json
File (Windows): C:\Program Files\ClaudeCode\managed-mcp.json
{
"mcpServers": {
"mirdan": {
"command": "uvx",
"args": ["mirdan"]
}
}
}
Managed Settings (Enforcement)
File: Same paths as above, but managed-settings.json
{
"hooks": {
"PreToolUse": [
{
"matcher": "Write|Edit",
"hooks": [
{
"type": "prompt",
"prompt": "Company policy: Use mcp__mirdan__enhance_prompt before coding and mcp__mirdan__validate_code_quality after.",
"timeout": 30
}
]
}
]
},
"allowManagedHooksOnly": true
}
Which Approach Should I Use?
| Scenario | Recommended Setup |
|---|---|
| Individual developer, trying mirdan | Level 1 (CLAUDE.md only) |
| Individual developer, daily use | Level 1 + Level 2 (CLAUDE.md + slash commands) |
| Team project | Level 1 + Level 3 (CLAUDE.md + hooks) |
| Security-sensitive project | All levels including path-specific rules |
| Enterprise/regulated environment | Level 4 (managed settings + hooks) |
Recommended progression:
- Start with CLAUDE.md (copy-paste, immediate benefit)
- Add
/codeslash command for explicit control - Add hooks when you want automatic enforcement
- Add path-specific rules for security-critical code
Cursor: Project Rules (Cursor 2.2+)
Cursor's Project Rules provide persistent instructions that activate automatically based on what you're doing. mirdan leverages this for invisible quality orchestration - you just code normally, mirdan handles the rest.
Quick Start: AGENTS.md
For immediate setup, create AGENTS.md in your project root:
# Code Quality with Mirdan
When writing or modifying code:
1. Call `mirdan.enhance_prompt` with task description before implementation
2. Follow quality_requirements from response during coding
3. Call `mirdan.validate_code_quality` on completed code - must pass before done
4. If security-related, use check_security=true
Full Integration: Granular Project Rules
For teams and power users, create focused rules in .cursor/rules/. Each rule uses the RULE.md format with YAML frontmatter.
.cursor/rules/mirdan-code-quality/RULE.md - Auto-attaches on code files:
---
description: Code quality orchestration for all code modifications
globs: ["*.py", "*.ts", "*.tsx", "*.js", "*.jsx", "*.go", "*.rs", "*.java", "*.rb"]
alwaysApply: false
---
# Mirdan Code Quality Gate
When modifying code files:
## Entry Point
Call `mirdan.enhance_prompt` with task description. Use response for:
- `detected_frameworks` → query documentation if unfamiliar
- `touches_security` → enables strict validation
- `quality_requirements` → constraints during implementation
## Implementation
Follow quality_requirements from enhance_prompt.
## Exit Gate (REQUIRED)
Before completion:
1. Call `mirdan.validate_code_quality` on your code
2. Set `check_security=true` if touches_security was true
3. Fix all violations and re-validate until passed
.cursor/rules/mirdan-debug/RULE.md - For Debug Mode (Cursor 2.2):
---
description: Enhances Cursor Debug Mode with mirdan analysis for debugging and bug fixes
alwaysApply: false
---
# Mirdan Debug Enhancement
When using Cursor's Debug Mode or fixing bugs:
## Before Generating Hypotheses
Call `mirdan.analyze_intent` to classify the debugging task.
## Before Applying Fix
1. Call `mirdan.validate_code_quality` with `check_security=true`
(bugs often have security implications)
2. Call `mirdan.get_verification_checklist(task_type="debug")`
3. Complete each verification step before marking fixed
.cursor/rules/mirdan-security/RULE.md - Auto-attaches on auth/security paths:
---
description: Strict security validation for authentication and authorization code
globs: ["**/auth/**", "**/security/**", "**/crypto/**", "**/*token*", "**/*session*"]
alwaysApply: false
---
# Mirdan Security Gate
Code in security-sensitive paths requires STRICT validation:
## Mandatory Exit Gate
1. `mirdan.validate_code_quality` with:
- `check_security=true` (REQUIRED)
- `severity_threshold="info"` (catch ALL issues)
2. Resolve ALL security violations before completion
How Rules Activate
| Your Action | Rule That Activates | Why |
|---|---|---|
Edit api/routes.py | mirdan-code-quality | Glob matches *.py |
Edit src/auth/login.ts | mirdan-code-quality + mirdan-security | Matches *.ts AND **/auth/** |
| Say "debug this error" | mirdan-debug | Description matches intent |
| Plan an implementation | mirdan-code-quality (on execution) | Applies when code is written |
Cursor 2.2 Feature Integration
Debug Mode: mirdan augments Cursor's hypothesis-driven debugging. analyze_intent classifies the bug, validate_code_quality ensures fixes don't introduce new vulnerabilities.
Plan Mode: When using Plan Mode with Mermaid diagrams, enhance_prompt at planning stage surfaces security considerations. When delegating steps to parallel agents, each follows mirdan-code-quality.
Multi-Agent Judging: When Cursor evaluates parallel agent runs, mirdan validation results inform which solution is "best" - quality-validated code wins.
Background Agents: mirdan rules provide guardrails for autonomous agents running in the background, ensuring quality even without human oversight.
Which Approach to Use?
| Approach | Best For |
|---|---|
| AGENTS.md | Quick start, individual developers, trying mirdan out |
| Project Rules | Teams, production projects, fine-grained control |
| Both | AGENTS.md baseline + specific rules for security paths |
Recommended: Start with AGENTS.md for immediate benefit. Add granular Project Rules as your team's needs grow.
Available Tools
enhance_prompt
Automatically enhance a coding prompt with quality requirements and tool recommendations.
analyze_intent
Analyze a prompt without enhancement to understand the detected intent.
get_quality_standards
Retrieve quality standards for a language/framework combination.
suggest_tools
Get recommendations for which MCP tools to use.
get_verification_checklist
Get a verification checklist for a specific task type (generation, refactor, debug, review, test).
validate_code_quality
Validate generated code against quality standards. Checks for security issues, architecture patterns, and language-specific style violations.
MCP Configuration Reference
Mirdan works with any MCP-compatible client. This section provides quick configuration for each client.
Note: For Claude Code users, see the comprehensive Claude Code Integration section above for advanced setup including hooks, slash commands, and enterprise deployment.
Claude Code (Quick Reference)
CLI setup (recommended):
claude mcp add mirdan -- uvx mirdan
Or manual configuration:
| Scope | File |
|---|---|
| Project (team-shared) | .mcp.json |
| User (personal) | ~/.claude.json |
{
"mcpServers": {
"mirdan": {
"command": "uvx",
"args": ["mirdan"]
}
}
}
Claude Desktop
File locations:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
Configuration:
{
"mcpServers": {
"mirdan": {
"command": "uvx",
"args": ["mirdan"]
}
}
}
Cursor
File locations:
- Global:
~/.cursor/mcp.json - Project:
.cursor/mcp.json
Configuration:
{
"mcpServers": {
"mirdan": {
"command": "uvx",
"args": ["mirdan"]
}
}
}
UI setup: File → Preferences → Cursor Settings → MCP
From Source (Development)
If running from a local clone instead of PyPI:
{
"mcpServers": {
"mirdan": {
"command": "uv",
"args": ["--directory", "/absolute/path/to/mirdan", "run", "mirdan"]
}
}
}
Configuration
Create a .mirdan/config.yaml in your project:
version: "1.0"
project:
name: "MyApp"
primary_language: "typescript"
frameworks: ["next.js", "prisma"]
quality:
security: "strict"
architecture: "moderate"
Troubleshooting
Server Not Connecting
-
Check uvx is available:
uvx --version -
Test server manually:
uvx mirdan # Should start without errors, waiting for MCP protocol -
Check server status in Claude Code:
/mcp
Debug Logging
Enable verbose output for troubleshooting:
{
"mcpServers": {
"mirdan": {
"command": "uvx",
"args": ["mirdan"],
"env": {
"FASTMCP_DEBUG": "true"
}
}
}
}
Common Issues
| Issue | Solution |
|---|---|
command not found: uvx | Install uv: curl -LsSf https://astral.sh/uv/install.sh | sh |
| Server starts but no tools appear | Restart Claude Code after config changes |
| Python version error | Ensure Python 3.11+ is installed |
Development
# Clone and install
git clone https://github.com/S-Corkum/mirdan.git
cd mirdan
uv sync --all-extras
# Run tests
uv run pytest
# Run the server locally
uv run mirdan
License
MIT