Skip to main content
Glama
SinboBoop

vibe-blueprint

by SinboBoop
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to vibe-blueprint

No user-submitted related servers found.

    Related Servers

    • aistarter-mcp

      foremox22
      A
      license
      A
      quality
      C
      maintenance
      Guides users through a structured pre-coding workflow—classifying experience, interviewing, scoping, architecture, database schema, and roadmap—while persisting decisions and checking for drift during implementation.
      10
      7 npm
      MIT

    • Doan

      Streamize-llc
      A
      license
      Not graded
      quality
      B
      maintenance
      Turns a rambling app idea into a structured planning canvas of screens, flows, systems, data and open questions inside an existing Claude Code or Codex session, then writes the settled plan back to that session as a spec to build from. Plans are stored in the project's .doan/ folder alongside the code.
      MIT

    • need-overthink

      vvn6d4zg82-byte
      A
      license
      B
      quality
      C
      maintenance
      Enables AI clients and agents to turn a new idea into a structured set of clarifying questions, technology options, upward design breakdowns, reverse reasoning, and risk assessments so users can steer top-level design decisions. It also supports saving insights and building a bidirectional design tree of concepts and their implementations.
      19
      MIT

    • MCP SSDLC Security Toolkit

      vuongdat67
      A
      license
      Not graded
      quality
      C
      maintenance
      Automates 85-95% of the Secure Software Development Lifecycle (SSDLC) planning phase through multi-role AI orchestration, enabling business analysis, threat modeling, test strategy design, and security code review.
      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

    A3.9/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct phase of the Foundation workflow: health check (doctor), proposal (analyze_project), user interaction (answer_question), reading (get), writing (commit), re-evaluation (assess_change), scanning (scan_changes), and verification (verify). There is no meaningful overlap between any two tools.

    Naming Consistency5/5

    All tools share the fixed prefix 'foundation_' followed by a clear verb_noun pattern (e.g., analyze_project, answer_question, scan_changes). This provides a predictable and systematic naming scheme across the entire set.

    Tool Count5/5

    With 8 tools, the set is well-scoped for the Foundation domain. Each tool serves a necessary function and none feel redundant or superfluous, fitting comfortably within the ideal 3-15 tool range.

    Completeness5/5

    The toolset covers the full lifecycle: analysis, user interaction, commit, change assessment, scanning, verification, and health checks. There are no obvious dead ends or missing core operations for the stated purpose of managing project Foundation state.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources