Skip to main content
Glama
Wise Mise MCP

Wise Mise MCP

by delorenj

🎯 Wise Mise MCP

The intelligent MCP server that transforms mise task management with AI-powered analysis and domain expertise

PyPI version Python 3.9+ License: MIT Code style: black Documentation Deploy to Smithery

Stop wrestling with mise configuration. Wise Mise MCP brings enterprise-grade intelligence to your mise workflow, automatically analyzing your project structure and creating perfectly organized, maintainable task architectures that scale with your development needs.

Why Wise Mise MCP?

🧠 Intelligent Task Analysis

  • Automatically analyzes your project structure to extract meaningful tasks

  • Understands 10+ technology domains (build, test, lint, deploy, CI/CD, etc.)

  • Suggests optimal task organization and dependency patterns

πŸ—οΈ Architecture-Aware

  • Follows mise best practices with hierarchical task organization

  • Supports complex dependency graphs with source/output tracking

  • Optimizes for incremental builds and performance

πŸ”§ Developer Experience

  • Integrates seamlessly with any MCP-compatible client

  • Provides detailed explanations and recommendations

  • Reduces cognitive load of task management

Related MCP server: Trellis MCP

Quick Start

# Just run this to start Wise Mise MCP with UVX
uvx wise-mise-mcp

# Or install globally
uv tool install wise-mise-mcp

Traditional pip

pip install wise-mise-mcp

Add to Your MCP Client

Add to your MCP client configuration (e.g., Claude Desktop):

{
  "mcpServers": {
    "wise-mise-mcp": {
      "command": "uvx",
      "args": ["wise_mise_mcp"]
    }
  }
}

Deploy with Smithery (One-Click Deployment)

Deploy to Smithery

Deploy Wise Mise MCP instantly to Smithery's cloud infrastructure with one click. Smithery provides managed MCP server hosting with built-in monitoring, scaling, and zero-configuration deployment.

Quick Smithery Deployment:

  1. Click the "Deploy to Smithery" badge above

  2. Connect your GitHub account (if needed)

  3. Your MCP server will be automatically deployed and configured

  4. Use the provided endpoint in your MCP client configuration

Benefits of Smithery Deployment:

  • βœ… Zero server management overhead

  • βœ… Automatic scaling and load balancing

  • βœ… Built-in monitoring and health checks

  • βœ… Global CDN for low-latency access

  • βœ… Automatic SSL/TLS encryption

  • βœ… Integration with popular MCP clients

What Makes It "Wise"?

Wise Mise MCP goes beyond simple task creation. It brings intelligence to your mise configuration:

πŸ” Project Analysis

# Analyzes your entire project structure
analyze_project_for_tasks("/path/to/project")
# Returns strategically organized tasks based on your tech stack

πŸ•ΈοΈ Dependency Mapping

# Traces complex task relationships
trace_task_chain("/path/to/project", "build:prod")
# Visualizes the complete execution flow

⚑ Smart Task Creation

# Intelligently places tasks in the right domain
create_task(
    project_path="/path/to/project",
    task_description="Run TypeScript type checking",
    # Automatically suggests: lint:types with proper dependencies
)

Core Features

🎯 Domain Experts

  • Build: Frontend/Backend build systems, bundlers, compilers

  • Test: Unit, integration, e2e testing strategies

  • Lint: Code quality, formatting, static analysis

  • Deploy: CI/CD, containerization, release management

  • Database: Migrations, seeding, schema management

  • Development: Local dev servers, hot reloading, debugging

πŸ“Š Intelligent Analysis

  • Complexity Assessment: Automatically categorizes tasks as Simple, Moderate, or Complex

  • Dependency Detection: Identifies natural task relationships

  • Source/Output Tracking: Optimizes incremental builds

  • Redundancy Elimination: Finds and removes duplicate tasks

πŸ”§ MCP Tools

Tool

Purpose

analyze_project_for_tasks

Extract strategic tasks from project structure

trace_task_chain

Map task dependencies and execution flow

create_task

Add new tasks with intelligent placement

prune_tasks

Remove outdated or redundant tasks

validate_task_architecture

Ensure configuration follows best practices

get_task_recommendations

Get suggestions for optimization

Example Workflows

Analyzing a New Project

# Let Wise Mise MCP analyze your project
> analyze_project_for_tasks("./my-app")

βœ… Detected: Next.js + TypeScript + Prisma
πŸ“‹ Suggested Tasks:
  β”œβ”€β”€ build:dev (next dev)
  β”œβ”€β”€ build:prod (next build)
  β”œβ”€β”€ test:unit (jest)
  β”œβ”€β”€ test:e2e (playwright)
  β”œβ”€β”€ lint:code (eslint)
  β”œβ”€β”€ lint:types (tsc --noEmit)
  β”œβ”€β”€ db:migrate (prisma migrate)
  └── deploy:vercel (vercel deploy)

Understanding Task Dependencies

# Trace the execution flow
> trace_task_chain("./my-app", "deploy:prod")

πŸ•ΈοΈ Task Chain for deploy:prod:
  1. lint:types (TypeScript check)
  2. test:unit (Unit tests)
  3. build:prod (Production build)
  4. deploy:prod (Deploy to production)

πŸ’‘ Recommendation: Add test:e2e before deploy:prod

Smart Task Creation

# Describe what you want, get intelligent suggestions
> create_task(
    project_path="./my-app",
    task_description="Generate API documentation from OpenAPI spec"
  )

🧠 Analysis: Documentation generation task
πŸ“ Suggested Placement: docs:api
πŸ”— Dependencies: build:prod (for spec generation)
πŸ“ Suggested Implementation:
  [tasks.docs.api]
  run = "swagger-codegen generate -i ./openapi.json -l html2 -o ./docs/api"
  sources = ["src/api/**/*.ts", "openapi.json"]
  outputs = ["docs/api/**/*"]

Architecture Philosophy

Wise Mise MCP follows a Domain-Driven Design approach to task organization:

πŸ›οΈ Hierarchical Structure

  • Level 1: Domain (build, test, lint, etc.)

  • Level 2: Environment/Type (dev, prod, unit, e2e)

  • Level 3: Specific Implementation (server, client, api)

πŸ”„ Dependency Patterns

  • Sequential: lint β†’ test β†’ build β†’ deploy

  • Parallel: test:unit + test:e2e β†’ deploy

  • Conditional: deploy:staging β†’ test:smoke β†’ deploy:prod

⚑ Performance Optimization

  • Source Tracking: Only rebuild when sources change

  • Output Caching: Reuse previous build artifacts

  • Incremental Builds: Support for modern build tools

Technology Support

Wise Mise MCP includes expert knowledge for:

Frontend: React, Vue, Angular, Svelte, Next.js, Nuxt, Vite, Webpack Backend: Node.js, Python, Go, Rust, Java, .NET, PHP Databases: PostgreSQL, MySQL, MongoDB, Redis, Prisma, TypeORM Testing: Jest, Vitest, Cypress, Playwright, PyTest, Go Test CI/CD: GitHub Actions, GitLab CI, CircleCI, Jenkins Deployment: Docker, Kubernetes, Vercel, Netlify, AWS, GCP

Contributing

We welcome contributions! See our Contributing Guide for details.

Quick Start for Contributors

# Clone and setup with UV
git clone https://github.com/delorenj/wise-mise-mcp
cd wise-mise-mcp
uv sync

# Run tests
uv run pytest

# Format code
uv run black .
uv run ruff check --fix .

License

MIT License - see LICENSE for details.

Support


Built with ❀️ by Jarad DeLorenzo and the open source community

Available Tools

10 tools
analyze_project_for_tasksA

Analyze a project structure and extract strategic task recommendations.

This tool examines the project's package managers, languages, frameworks, and structure to recommend useful tasks organized by domain. It identifies what build systems, testing frameworks, and development tools are in use to suggest practical, actionable tasks.

Inputs: project_path (required). Returns: object

create_taskB

Create a new task with intelligent placement and configuration.

This tool analyzes the task description and project context to suggest the best domain, complexity level, and implementation for a new task. It follows mise best practices for task organization and naming.

Inputs: project_path (required), task_description (required), domain_hint, suggested_name, +1 more. Returns: object

get_mise_architecture_rulesA

Get the architectural rules and patterns that Wise Mise MCP follows.

This tool explains the design principles, domain organization, and architectural decisions that guide intelligent task management.

Inputs: no named parameters. Returns: object

get_task_recommendationsA

Get general recommendations for mise task organization and best practices.

This tool provides guidance on how to structure tasks effectively, naming conventions, dependency patterns, and optimization strategies.

Inputs: no named parameters. Returns: object

mise_task_expert_guidanceA

Get expert guidance on mise task management and optimization.

This tool provides advanced tips, troubleshooting advice, and expert recommendations for getting the most out of mise task management.

Inputs: no named parameters. Returns: object

prune_tasksB

Remove redundant or outdated tasks from the project.

This tool identifies tasks that are no longer needed, have become redundant, or are not following current best practices. It can either report what would be pruned (dry run) or actually remove the tasks.

Inputs: project_path (required), dry_run. Returns: object

remove_taskA

Remove a specific task from the project.

This tool removes a named task from the mise configuration, handling any cleanup needed and warning about dependent tasks that might be affected.

Inputs: task_name (required), project_path (required). Returns: object

task_chain_analystA

Analyze and optimize task execution chains for better performance.

This tool provides insights into task execution patterns, identifies bottlenecks, and suggests optimizations for complex task workflows.

Inputs: no named parameters. Returns: object

trace_task_chainA

Trace the dependency chain for a specific task.

This tool analyzes task dependencies to show the complete execution flow for a given task. It helps understand what tasks will run and in what order, making it easier to optimize build processes and debug issues.

Inputs: task_name (required), project_path (required). Returns: object

validate_task_architectureB

Validate the current task architecture against best practices.

This tool analyzes the existing task structure to identify issues like circular dependencies, missing dependencies, redundant tasks, and opportunities for better organization.

Inputs: project_path (required). Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 10 tools

    Disambiguation4/5

    Tools generally have distinct purposes, but 'get_task_recommendations' and 'mise_task_expert_guidance' both offer advice, and 'trace_task_chain' overlaps slightly with 'task_chain_analyst'. Descriptions help differentiate them.

    Naming Consistency4/5

    Most tools use a consistent verb_noun pattern (e.g., create_task, prune_tasks), but 'task_chain_analyst' and 'mise_task_expert_guidance' break the pattern with noun-first or lengthy names.

    Tool Count5/5

    10 tools cover the domain well without being excessive. Each tool has a clear role in task management, from creation to analysis to cleanup.

    Completeness4/5

    The set includes creation, removal, pruning, validation, tracing, and guidance. However, an explicit tool for listing all tasks or updating existing tasks is missing, which is a minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers