Skip to main content
Glama
mo666-med

Enhanced Miyabi MCP Server

by mo666-med
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to Enhanced Miyabi MCP Server

No user-submitted related servers found.

    Related Servers

    • Delia

      zbrdc
      F
      license
      A
      quality
      Not graded
      maintenance
      Routes AI tasks to appropriate local LLM models (quick, coder, MoE, thinking) with automatic model selection, multi-backend support (Ollama, llama.cpp, Gemini), and parallel processing capabilities.
      9
      1
      -

    • mcp-swarm

      MoseLu
      A
      license
      Not graded
      quality
      F
      maintenance
      A multi-model agent swarm coordinator that automatically selects the most suitable LLM based on task content and role requirements. It provides tools for automated model selection, direct model interaction, and task analysis across a variety of specialized AI models.
      43 npm
      MIT

    • MCP Shrimp Task Manager

      samihalawa
      A
      license
      Not graded
      quality
      D
      maintenance
      An intelligent task management system that provides structured workflows for AI Agents to plan, decompose, and execute complex programming tasks. It features a dedicated research mode for technical investigations and a task memory function to optimize workflows and avoid redundant coding work.
      1
      MIT

    • Oxide

      yayoboy
      A
      license
      A
      quality
      D
      maintenance
      Intelligent LLM orchestrator that automatically routes tasks to the most appropriate AI model (Gemini, Qwen, Ollama, LM Studio) based on task characteristics, enabling distributed processing and parallel execution across local and network services.
      3
      10 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.2/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools have distinct primary purposes: analyzing task intent, dispatching tasks, generating articles, and handling development tasks. However, miyabi__auto_dispatch and miyabi__handle_development_task could be slightly confusing as both involve task handling, but their descriptions clarify dispatch vs. execution roles.

    Naming Consistency5/5

    All tools follow a consistent miyabi__verb_noun pattern with underscores, making them predictable and easy to parse. There are no deviations in naming style across the set.

    Tool Count3/5

    With 4 tools, the count is reasonable but feels borderline thin for a server named 'Enhanced Miyabi MCP Server' that implies broader functionality. The tools cover specific workflows but may leave gaps in a comprehensive task-handling system.

    Completeness3/5

    The tools cover key steps like analysis, dispatch, article generation, and development tasks, but there are notable gaps. For example, there's no tool for handling general tasks (Manus) after dispatch, and no update or delete operations for generated articles or tasks, limiting lifecycle coverage.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources