Skip to main content
Glama
DPGS-oss

App Factory MCP

by DPGS-oss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to App Factory MCP

No user-submitted related servers found.

    Related Servers

    • MCP Director

      userlite
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      An intelligent orchestration server that routes user requests to appropriate specialized MCP servers and manages complex workflows.
      -

    • genesys-mcp

      sachin-genesysdev
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that puts a Genesys Cloud org in an AI assistant's hands, enabling it to build queues, skills, users, wrap-up codes, Architect flows, and outbound contact lists, campaigns, and cadences. It composes flows as diagrams and YAML, then publishes them through Genesys' own validation pipeline.
      -

    • agentloop

      luckeyfaraday
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that enables AI agents to run a deterministic orchestration loop with decomposition, subagent execution, and review feedback across multiple LLM backends.
      60
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 32 tools

    Disambiguation5/5

    Each tool maps to a distinct phase or supporting function (intake, interview, design, blueprint, build, audit, deploy, memory, research). Even similar-sounding tools like get_context and get_project_state have clearly different scopes, so an agent can reliably select the right one.

    Naming Consistency4/5

    The vast majority of tools follow a clear verb_noun pattern (e.g., start_project, get_next_questions, generate_blueprint). A few single-word verbs (deploy, remember, refine) are minor exceptions but remain unambiguous and fit the action-oriented style.

    Tool Count2/5

    At 32 tools, this is a very large surface for an agent to navigate. While each tool has a role in the comprehensive workflow, the sheer number exceeds the typical range and increases selection overhead, making it feel heavy.

    Completeness5/5

    The toolset covers the entire app lifecycle—from initial prompt enhancement and interview, through design and blueprint generation, to build, audit, and deployment—plus supporting utilities for memory, context, research, and legal compliance. No obvious dead ends or major gaps exist.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources