Skip to main content
Glama
Flagler-County-BoCC

mcp-forge

by Flagler-County-BoCC
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-forge

No user-submitted related servers found.

    Related Servers

    • dep-scope

      FlorianBruniaux
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides symbol-level dependency analysis and LLM-ready migration prompts for TypeScript/JavaScript projects, enabling AI editors to scan projects, analyze packages, and generate refactoring prompts.
      58 npm
      19
      MIT

    • upgrade-pilot-mcp

      kdinisv
      A
      license
      B
      quality
      D
      maintenance
      Enables AI agents to safely upgrade JavaScript and TypeScript projects through dependency analysis, upgrade path detection, breaking change identification, codemod application, and PR summary generation.
      14
      14 npm
      MIT

    • Programmatic

      DarkLordGeo
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to perform structural code operations on TypeScript/TSX projects—finding symbols and references and renaming them semantically while preserving source.
      27 npm
      MIT

    • PromptArchitect MCP

      MerabyLabs
      F
      license
      A
      quality
      C
      maintenance
      Refines and improves AI prompts using workspace-aware context from your project's tech stack, structure, and dependencies. Includes tools to analyze prompt quality and generate well-structured prompts from raw ideas.
      4
      209 npm
      5
      -
    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 5 tools

    Disambiguation5/5

    Each tool serves a distinct purpose: retrieving specific prompts (entrypoint, master, or step), listing steps, or validating manifests. No ambiguity in their roles.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., get_entrypoint, list_steps, validate_manifest), ensuring predictability.

    Tool Count5/5

    With 5 tools, the server is well-scoped for its domain of prompt management and validation, neither too sparse nor too heavy.

    Completeness5/5

    The tool set covers retrieval of all prompt variations, step listing, and manifest validation, leaving no obvious gaps for the intended use case.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources