Skip to main content
Glama
khalilbenaz

MDAN

by khalilbenaz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to MDAN

No user-submitted related servers found.

    Related Servers

    • agent-team-mcp

      RichardLemmon
      A
      license
      Not graded
      quality
      C
      maintenance
      A reusable AI software development team built on MCP. 13 specialized agents (Project Manager, Backend, Frontend, QA, Security, DevOps, UX, and more) collaborate via shared SQLite state. Exposes 44 MCP tools across 12 domains. All discussions and decisions are stored in the database so agents get back up to speed immediately when re-loaded.
      MIT

    • Jules AI MCP Server

      Helfstein-one
      A
      license
      A
      quality
      C
      maintenance
      Enables developers to delegate asynchronous coding tasks to a cloud-based autonomous agent, creating tasks, reviewing and approving execution plans, sending feedback, monitoring sessions, and retrieving diffs and Pull Requests directly from an MCP-compatible IDE. It also supports configurable mock mode for local testing without consuming API credits.
      7
      MIT

    • Boring Gemini

      Boring206
      F
      license
      Not graded
      quality
      C
      maintenance
      An autonomous AI development agent that enables full-stack coding, automated verification, RAG-powered code search, and quality assurance through MCP tools. Supports Gemini CLI, Claude Code CLI, with features like parallel verification, security scanning, and spec-driven development.
      23 PyPI
      5
      -
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/5.0

    Scored across 27 tools

    Disambiguation4/5

    Most tools target distinct resources (workflows, agents, memory, graph, ecosystem, quality) and their descriptions clarify boundaries. A few pairs like memory_list vs list_agents or graph_impact vs graph_stale could be confused at first glance, but the descriptions prevent serious misselection.

    Naming Consistency3/5

    All tools share the mdan_ prefix, but the suffix pattern varies: verb_noun (list_workflows), noun_verb (memory_list, ecosystem_search), noun_adjective (graph_stale), and bare verbs (check, trace). This mixed ordering is readable but not predictable.

    Tool Count2/5

    27 tools is above the comfortable range and covers seven or eight distinct subdomains, making the server feel heavy. Some tools like ecosystem_stats and memory_list could arguably be merged without loss.

    Completeness4/5

    The server covers the full workflow lifecycle: planning, execution, state tracking, quality gates, traceability, and export. Minor gaps exist (no graph node/edge removal, no workflow creation/editing, no decision record update), but these are likely handled by file operations and don't block core usage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources