Skip to main content
Glama
mithun4elp

briefkit-mcp-server

by mithun4elp

Related Servers

Alternatives to briefkit-mcp-server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      A
      maintenance
      Design contract layer for AI agents. Scans Figma, code, Storybook, and token files, reconciles conflicts, and serves a single machine-readable source of truth so every agent gets the same authoritative design rules before it builds. Local-first.
      6
      194 npm
      19
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      A Spec-Driven Development toolkit that transforms LLMs into development agents by providing expert-crafted prompts for generating structured specifications and validating documents across the Requirements → Design → Tasks → Code workflow.
      1
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables schema conversion from SQL/Prisma/JSON to Zod, TypeScript, and Pydantic, and generates realistic synthetic mock data.
      3
      MIT
    • A
      license
      D
      quality
      D
      maintenance
      Spec-driven development tool for AI coding assistants that generates specs, validates code compliance, and provides actionable feedback.
      11
      29
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Portable agent tools with typed schemas (diff, cron, units, JSON→TS, outdoor helpers, prompts). Free to try—no account required.
      30
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Behavioral verification intelligence for AI coding agents. Reads a TypeScript or JavaScript repo, clusters functions into 25 semantic workflows (Authentication, Payments, Webhooks, Caching, Queue, and more), and emits concrete adversarial probes per workflow. 17 MCP tools, local SQLite state, zero cloud.
      17
      62 npm
      1
      MIT

    TDQS

    A4.3/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: database schema, design system, RLS policies, and informational. No overlap or ambiguity.

    Naming Consistency5/5

    All names follow the pattern 'briefkit_verb_noun' with snake_case. Three use 'generate', one uses 'get', which is appropriate for its function. Fully consistent.

    Tool Count5/5

    Four tools cover the core generation needs for a SaaS brief (schema, design, RLS) plus an info tool. Well-scoped for the domain.

    Completeness4/5

    The tools cover the main specification areas, but additional tools for API spec or frontend components would provide fuller coverage. Minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues