Skip to main content
Glama

Related Servers

Alternatives to backgen-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Blockend MCP Server lets AI coding agents manage production-ready backend building blocks directly in a project. Agents can discover available blocks, analyze project configuration, preview file changes, install backend utilities, diagnose issues, check for updates, and apply updates. Blockend generates the implementation directly into your codebase, giving you ownership of the resulting code with
      6 npm
      10
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server providing AI assistants with intelligent Supabase database access, featuring dynamic schema discovery, complete user management, and file storage operations.
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that equips AI assistants with specialized, opinionated development playbooks for building microservices, frontends, databases, and DevOps pipelines. It integrates with clients like VS Code Copilot, Claude Desktop, and Cursor to provide battle-tested expertise.
      74 npm
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Zero-config MCP server that gives AI coding assistants a real-time diagnostic snapshot of your local dev environment. Detects framework, running services, recent errors, git state, and provides a health diagnosis in one call.
      3
      6 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Multi-stack scaffolding engine for generating production-ready module structures (NestJS, Java Spring, Python FastAPI) directly from an MCP-compatible AI client, reducing token usage for boilerplate code.
      -

    TDQS

    A4.4/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., init_project, add_plugin, remove_plugin, generate_*). However, doctor and project_info both run 6-category diagnostics with overlapping descriptions, potentially causing confusion for an agent despite doctor having auto-fix capability.

    Naming Consistency4/5

    The majority of tools follow a verb_noun pattern in snake_case (add_plugin, generate_resource, list_plugins). Two tools break the pattern: doctor (just a noun) and project_info (noun_noun). This minor inconsistency is manageable.

    Tool Count5/5

    With 10 tools covering project initialization, plugin management, resource generation, and diagnostics, the count is well-scoped for the server's purpose. Each tool serves a distinct role without unnecessary bloat.

    Completeness4/5

    Core workflows are covered: init, add/remove plugins, generate resources/factories/seeds, and diagnostics. A minor gap is the lack of a dedicated tool to list installed plugins (only available through diagnostics/manifest), but this does not significantly hinder typical usage.

    Maintenance

    ActivityStale
    ResponsivenessResponsive