Skip to main content
Glama

Related Servers

Alternatives to ForgePilot MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Lets ChatGPT, Claude Desktop, Claude Code, and other MCP clients run an allowlisted set of local commands and read files from a chosen directory, so an assistant can analyse a codebase or trigger local generators (images, sprites, assets) without metered API tokens. The server is read-only and deny-by-default by default, with no shell, path containment, opt-in writes, and required auth when exposed over HTTP.
      3
      1
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      A local-first MCP server that enables AI-assisted coding through workspace-scoped tools for file reading/editing, command execution, jobs, Git, LSP, media, browser, and desktop workflows. It enforces OAuth, workspace ACL, trust policies, and file/secret guards so owners can safely grant inspect, edit, or trusted capabilities.
      40 npm
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that helps coding agents research and prepare GitHub contributions by gathering repository guidance, related work, code context, and validation evidence into a local SQLite corpus, without ever writing to GitHub.
      96 npm
      5
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A local, read-only MCP server that lets coding agents search the complete AAS skill catalog, compose and validate agent-chosen skill stacks, and generate reproducible, reviewable plans without uploading project code.
      6,894 npm
      1
      MIT

    TDQS

    B3.2/5.0

    Scored across 12 tools

    Disambiguation3/5

    Several tools generate configs or artifacts (generate_config, create_connector_artifact, create_artifact, create_shareable_pack, create_community_bridge_pack) with overlapping 'create' verbs, and chat/search both use Exa, so misselection is possible despite descriptive text.

    Naming Consistency4/5

    All tools use the forgepilot_ snake_case prefix, but four tools are noun-phrase plans (local_acceleration_plan, backend_switch_plan, community_bridge_plan) while the rest use verb or verb_noun patterns, a minor deviation.

    Tool Count5/5

    12 tools is well within the ideal 3-15 range and each tool maps to a distinct ForgePilot integration task (health, search, config, artifacts, plans), so the count is appropriate.

    Completeness3/5

    The surface covers many one-way generation/planning tasks but lacks lifecycle operations: no list, get, update, or delete for artifacts/packs, and device flow has only a start tool with no completion/poll tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues