Skip to main content
Glama

Related Servers

Alternatives to FRD Orchestrator

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      Transforms a NestJS REST API into an MCP server for AI agents to manage tasks securely via standardized tools.
      -
    • 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.
      -
    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that automates the generation of production-grade async FastAPI services following Clean Architecture, with self-healing pytest-based verification and OpenAPI spec ingestion for rapid CRUD API development.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An AI-native specification framework that enables deep requirements analysis and structured project planning through intelligent Q\&A workflows. The MCP server provides tools for project initialization, requirement analysis, and the generation of living documentation like development plans and architecture specs.
      6 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server built with NestJS that provides OAuth 2.1 authentication with GitHub and exposes MCP tools through Server-Sent Events transport. Enables secure, real-time communication with JWT-based protection and dependency injection.
      -

    TDQS

    B3.1/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_frd' has a clear and distinct purpose of retrieving FRD content by ID.

    Naming Consistency5/5

    The naming is trivially consistent as there is only one tool. The tool name 'get_frd' follows a clear verb_noun pattern (get + FRD), which would be appropriate if more tools were added.

    Tool Count2/5

    A single tool is too few for a server named 'FRD Orchestrator', which implies orchestration capabilities beyond simple retrieval. The scope suggests operations like create, update, delete, or manage FRDs, but only a read operation is provided.

    Completeness2/5

    The tool surface is severely incomplete for an orchestrator. It only supports retrieving FRDs by ID, lacking essential operations such as creating, updating, deleting, listing, or searching FRDs. This will cause significant agent failures in orchestration tasks.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues