Skip to main content
Glama
pranjal2410719

dev-mcp

by pranjal2410719
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to dev-mcp

No user-submitted related servers found.

    Related Servers

    • MCP Memory Server

      keleshteri
      A
      license
      B
      quality
      D
      maintenance
      Gives AI coding assistants persistent memory, safety controls, and project awareness by tracking coding sessions, protecting critical files from modifications, and managing approval workflows with automatic changelog generation.
      19
      41 npm
      MIT

    • Vibe Coder MCP Server

      JasmijnWarren
      A
      license
      Not graded
      quality
      A
      maintenance
      Extends AI assistants with software development capabilities such as deep research, codebase analysis, requirements and user-story generation, project scaffolding, context curation, task management, and multi-step workflow execution.
      19 npm
      MIT

    • CastPlan MCP

      Ghostseller
      A
      license
      B
      quality
      C
      maintenance
      Provides AI assistants with persistent memory of your project architecture, development history, and technical decisions, allowing them to give context-aware coding help without needing repeated explanations.
      16
      61 npm
      2
      MIT

    • MCP Memory Keeper

      emanuelele5502
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI coding assistants to persistently save, search, checkpoint, and restore project context across sessions, including decisions, progress, and file state. It supports shared channels, git-aware organization, and batch operations for long-running or parallel development workflows.
      250 npm
      MIT

    • Vibe-Coder-MCP

      julie85552
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to research, plan, generate requirements and user stories, create starter projects, analyze codebases, curate context, manage tasks, and execute multi-step development workflows.
      19 npm
      MIT
    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

    C2.9/5.0

    Scored across 71 tools

    Disambiguation2/5

    With 71 tools, several serve nearly identical purposes: add_task vs create_task, next_task vs next_best_action, complete_phase vs next_phase, and commit_changes vs git_commit. This overlap creates confusion and makes it difficult for an agent to select the correct tool. Descriptions help somewhat, but the boundaries are fuzzy for many pairs.

    Naming Consistency3/5

    Most tools use snake_case with a verb-noun pattern (list_tasks, create_task, get_context), but there are many exceptions like 'doctor', 'blocked_tasks', 'impact_analysis', 'project_dashboard', and 'next_best_action'. The mix of imperative verbs and noun phrases makes it hard to predict tool names, though the majority are still readable.

    Tool Count1/5

    71 tools is an extreme count for a single MCP server, far exceeding the 3-15 well-scoped range. The massive surface area creates significant cognitive load and makes tool discovery and selection unwieldy for agents.

    Completeness4/5

    The tool set covers an impressively broad project lifecycle: file operations, git workflows, task/phase/milestone management, PRD handling, context management, handoffs, dashboards, and architecture validation. Minor gaps exist (e.g., no delete_task or delete_milestone), but core workflows are supported with multiple redundant paths.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources