Skip to main content
Glama
Sign In
forge-mcp

forge-mcp

by concurrence-hq
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to forge-mcp

No user-submitted related servers found.

    Related Servers

    • @restforge-dev/mcp-server

      @restforge-dev/mcp-serverofficial

      restforge
      A
      license
      A
      quality
      C
      maintenance
      MCP server that exposes RESTForge capabilities to AI agents, enabling them to set up, configure, generate code, and manage RESTForge projects through natural language.
      29
      44 npm
      MIT

    • Ops-Center

      Unicorn-Commander
      A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables agents to administer a self-hosted AI control plane for users, organizations, subscriptions, API keys, model providers, and service health, with local-first model routing and cloud failover.
      Apache 2.0

    • coding-os

      kouroshez
      A
      license
      B
      quality
      A
      maintenance
      MCP server for coding-os, a cognitive operating system that gives AI agents memory, structure, and discipline. It exposes tools for project management, task tracking, knowledge graphs, and cognition traces to Claude Code and Codex.
      89
      34 PyPI
      6
      Apache 2.0
    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    TDQS

    C2.9/5.0

    Scored across 37 tools

    Disambiguation2/5

    Many entity-specific create/update tools (agent, context_graph, metric, etc.) overlap with the generic forge_entity_create/forge_entity_update, and the update semantics are inconsistent: some entity-specific updates create versions, others only edit metadata while pointing to forge_entity_update for version changes. This creates real ambiguity about which tool to call for a given change.

    Naming Consistency4/5

    Most tools follow forge_<entity>_<action>, and all use snake_case, but org tools flip to forge_<action>_<entity> (list_orgs, set_org) and a couple are action-only (simulate, smoke_test). The inconsistency is noticeable but not chaotic.

    Tool Count2/5

    37 tools is well above the 3-15 well-scoped range and even above the 16-25 heavy range; the generic entity_* CRUD layer plus per-entity create/update duplicates much of the surface. A more streamlined set would use either generic CRUD or specialized entity tools, not both.

    Completeness3/5

    Core resource lifecycle and testing/evaluation are covered, and entity_delete/get/list fill many gaps. However, unit test sets can be created but not executed, and tool versions are said to be 'published separately' with no corresponding tool, leaving notable dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Resources