npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@j0kz/orchestrator-mcp

v1.1.1

Published

MCP workflow orchestrator - chain multiple MCP tools together into powerful workflows

Readme

@j0kz/orchestrator-mcp

MCP Workflow Orchestrator - Chain multiple MCP tools into powerful automated workflows

npm MCP Compatible

Orchestrate code quality, security, testing, and architecture analysis tools into automated workflows that run on git hooks or in your AI editor.

⚡ Performance: Saves 25-55 seconds per commit and 2.5-5 minutes per PR compared to running MCPs separately. See benchmark results


🚀 Quick Start

Installation

npm install -g @j0kz/orchestrator-mcp

Configuration (Claude Code)

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "orchestrator": {
      "command": "orchestrator-mcp"
    }
  }
}

For other editors, see Configuration.


🎯 What It Does

The Orchestrator MCP enables you to:

  • Run pre-built workflows - pre-commit, pre-merge, quality-audit
  • Chain multiple MCPs - smart-reviewer → security-scanner → test-generator
  • Automate code quality - Trigger from git hooks or AI editor
  • Custom sequences - Build your own multi-tool workflows
  • 🌍 Bilingual support - Works in English and Spanish
  • 🎯 Smart clarification - Asks for focus when ambiguous

NEW: Ambiguity Detection & Focus Areas

The orchestrator now features intelligent ambiguity detection. When you make vague requests, it clarifies what you want:

User: "review my code"

Orchestrator responds:
  "What would you like me to focus on?"

  Options:
  a) Security Analysis - Fast security scan (pre-commit workflow)
  b) Code Quality - Review with complexity & tests (pre-merge workflow)
  c) Performance - Architecture analysis (quality-audit workflow)
  d) Everything - Complete analysis

User: "b"

Orchestrator executes pre-merge workflow with quality focus

Bilingual Support:

Usuario: "revisar mi código"

Orchestrador responde:
  "¿En qué te gustaría que me enfocara?"

  Opciones:
  a) Análisis de Seguridad - Escaneo rápido (flujo pre-commit)
  b) Calidad de Código - Revisión con complejidad (flujo pre-merge)
  c) Rendimiento - Análisis de arquitectura (flujo quality-audit)
  d) Todo - Análisis completo

Example: Pre-commit Workflow

User in Claude Code: "Run pre-commit checks on my staged files"

Orchestrator executes:
  1. smart-reviewer (code review)
  2. security-scanner (vulnerability scan)

Returns:
  ✅ Code review: 87/100
  ✅ Security scan: No issues found

📋 Pre-Built Workflows

1. pre-commit - Fast Local Checks

When to use: Before every commit Duration: ~2-5 seconds Steps:

  • Code review (moderate severity)
  • Security scan
// Usage in Claude Code
"Run pre-commit workflow on auth.ts"

// Result
{
  "workflow": "pre-commit",
  "success": true,
  "duration": 3247,
  "steps": [
    { "name": "code-review", "success": true, "score": 85 },
    { "name": "security-scan", "success": true, "issues": 0 }
  ]
}

2. pre-merge - Comprehensive PR Validation

When to use: Before merging pull requests Duration: ~10-30 seconds Steps:

  • Batch code review (strict)
  • Architecture analysis (circular dependency detection)
  • Security audit (project-wide)
  • Test coverage check (70% target)
// Usage in Claude Code
"Run pre-merge workflow for this PR"

// Result
{
  "workflow": "pre-merge",
  "success": true,
  "duration": 18234,
  "steps": [
    { "name": "batch-review", "success": true, "avgScore": 91 },
    { "name": "architecture-analysis", "success": true, "circular": 0 },
    { "name": "security-audit", "success": true, "findings": 0 },
    { "name": "test-coverage", "success": true, "coverage": 78 }
  ]
}

3. quality-audit - Deep Analysis & Reporting

When to use: Weekly/monthly quality reviews Duration: ~30-60 seconds Steps:

  • Security report generation (saved to reports/security.md)
  • Architecture analysis with dependency graph
  • Documentation generation
// Usage in Claude Code
"Run quality audit on the entire project"

// Result
{
  "workflow": "quality-audit",
  "success": true,
  "duration": 42891,
  "steps": [
    { "name": "security-report", "success": true, "generated": "reports/security.md" },
    { "name": "architecture-analysis", "success": true, "modules": 47 },
    { "name": "generate-docs", "success": true, "files": ["README.md", "API.md"] }
  ]
}

🔧 Custom Workflows

Build your own workflows with run_sequence:

// Custom workflow: Review → Refactor → Test → Document
{
  "tool": "run_sequence",
  "arguments": {
    "steps": [
      {
        "name": "review",
        "mcp": "smart-reviewer",
        "tool": "review_file",
        "params": { "filePath": "src/auth.ts", "config": { "severity": "strict" } }
      },
      {
        "name": "refactor",
        "mcp": "refactor-assistant",
        "tool": "suggest_refactorings",
        "params": { "code": "..." },
        "dependsOn": ["review"]
      },
      {
        "name": "generate-tests",
        "mcp": "test-generator",
        "tool": "generate_tests",
        "params": { "sourceFile": "src/auth.ts" },
        "dependsOn": ["refactor"]
      },
      {
        "name": "generate-docs",
        "mcp": "doc-generator",
        "tool": "generate_jsdoc",
        "params": { "filePath": "src/auth.ts" }
      }
    ]
  }
}

🛠️ Configuration

Claude Code

{
  "mcpServers": {
    "orchestrator": {
      "command": "orchestrator-mcp"
    }
  }
}

Config location:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json

Cursor

{
  "mcpServers": {
    "orchestrator": {
      "command": "orchestrator-mcp"
    }
  }
}

Config location: Cursor Settings → MCP → Edit Configuration

Windsurf / VS Code / Other

Follow your editor's MCP configuration guide. The command is always:

orchestrator-mcp

📦 Available MCPs

The orchestrator can coordinate these MCP tools:

| MCP | Tool Examples | Purpose | | ----------------------- | ------------------------------------------------------- | ---------------------------------- | | smart-reviewer | review_file, batch_review | Code quality analysis | | security-scanner | scan_file, scan_project, generate_security_report | Vulnerability detection | | test-generator | generate_tests, batch_generate | Test suite generation | | architecture-analyzer | analyze_architecture | Dependency & architecture analysis | | refactor-assistant | suggest_refactorings, extract_function | Code refactoring | | doc-generator | generate_jsdoc, generate_full_docs | Documentation generation | | api-designer | generate_openapi, design_rest_api | API design | | db-schema | design_schema, generate_migration | Database schema design |

Install MCPs:

npm install -g @j0kz/smart-reviewer-mcp
npm install -g @j0kz/security-scanner-mcp
npm install -g @j0kz/test-generator-mcp
# ... or install all at once:
npx @j0kz/mcp-agents@latest

🎮 Usage Examples

In Claude Code (Natural Language)

You: "Review my changes and check for security issues"
Claude: [Calls orchestrator with pre-commit workflow]
Claude: "✅ Code review passed (Score: 87/100). ✅ No security vulnerabilities found."

You: "Prepare this PR for merge"
Claude: [Calls orchestrator with pre-merge workflow]
Claude: "All checks passed! Architecture is clean, tests at 78% coverage, zero security issues."

You: "Analyze my entire project quality"
Claude: [Calls orchestrator with quality-audit workflow]
Claude: "Quality audit complete. Security report saved. Architecture graph generated. Docs updated."

Via JSON-RPC (Programmatic)

# List available workflows
echo '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"list_workflows","arguments":{}}}' | orchestrator-mcp

# Run pre-commit workflow
echo '{"jsonrpc":"2.0","method":"tools/call","params":{"name":"run_workflow","arguments":{"workflow":"pre-commit","files":["src/auth.ts"]}}}' | orchestrator-mcp

🔗 Git Hook Integration

Pre-commit Hook (Husky)

# Install Husky
npm install --save-dev husky
npx husky install

# Create pre-commit hook
npx husky add .husky/pre-commit "npx orchestrator-cli pre-commit"

.husky/pre-commit:

#!/bin/sh
. "$(dirname "$0")/_/husky.sh"

# Get staged files
STAGED_FILES=$(git diff --cached --name-only --diff-filter=ACM)

# Run orchestrator (you'll need to build a simple CLI wrapper)
echo "$STAGED_FILES" | npx run-orchestrator-workflow pre-commit

🧪 Testing

The orchestrator is thoroughly tested:

npm test

Test coverage:

  • MCP-to-MCP communication
  • Workflow execution
  • Dependency resolution
  • Error handling

📚 API Reference

Tool: run_workflow

Execute a pre-built workflow.

Parameters:

  • workflow (optional): 'pre-commit' | 'pre-merge' | 'quality-audit'
  • focus (optional): 'security' | 'quality' | 'performance' | 'comprehensive'
  • files (required): Array of file paths
  • projectPath (optional): Project root path (defaults to '.')
  • language (optional): 'en' | 'es' - Response language (auto-detected if not specified)

Note: Either workflow or focus must be provided. If neither is provided, the orchestrator will ask for clarification.

Focus Areas Map to Workflows:

  • security → pre-commit workflow
  • quality → pre-merge workflow
  • performance → quality-audit workflow
  • comprehensive → pre-merge workflow

Returns:

{
  workflow: string;
  success: boolean;
  duration: number;
  steps: Array<{
    name: string;
    success: boolean;
    duration: number;
    data?: any;
    error?: string;
  }>;
  errors: string[];
}

Tool: run_sequence

Execute a custom sequence of MCP tools.

Parameters:

  • steps (required): Array of workflow steps

Step schema:

{
  name: string;          // Step identifier
  mcp: string;           // MCP name (e.g., 'smart-reviewer')
  tool: string;          // Tool name (e.g., 'review_file')
  params?: any;          // Tool parameters
  dependsOn?: string[];  // Array of step names this depends on
}

Returns: Same as run_workflow


Tool: list_workflows

List all available workflows with metadata.

Parameters: None

Returns:

{
  workflows: Array<{
    id: string;
    name: string;
    description: string;
    steps: number;
  }>;
}

🐛 Troubleshooting

"MCP not installed" error

Install the required MCPs:

npx @j0kz/mcp-agents@latest

"Workflow timeout" error

Increase timeout in your MCP configuration (if supported by your editor).

"Circular dependency detected"

Check your dependsOn fields in custom workflows. Steps cannot depend on each other circularly.


🤝 Contributing

Contributions welcome! Please read CONTRIBUTING.md.


📄 License

MIT © j0kz


🔗 Related Packages


Made with ❤️ for AI-powered development