Skip to main content
Glama
kirubeshvarman28

CodeForgeX

by kirubeshvarman28
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to CodeForgeX

No user-submitted related servers found.

    Related Servers

    • Sandbox MCP Server

      nagaozen
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to create isolated Docker runtimes, execute commands, manage workspace files, drive a headed browser, and retrieve artifacts through eight semantic MCP tools, with progressive capability discovery and explicit sandbox lifecycle.
      Apache 2.0

    • Coding Tools MCP

      xyTom
      A
      license
      Not graded
      quality
      B
      maintenance
      Empower any MCP-compatible AI Agent(MCP Client) with engineering-grade capabilities to understand, modify, run, and deliver real-world code repositories.
      212 PyPI
      1,194
      Apache 2.0

    • DevPilot MCP

      wbb316
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to understand, run, test, diagnose, review, benchmark, and validate real local software projects through the Model Context Protocol. It provides workspace-confined safe execution, structured evidence instead of raw logs, and Git checkpoints with guarded rollback that never destroys user work.
      8 npm
      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.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct concern: file listing, status inspection, content reading, search, test execution, test output retrieval, patching, and diff viewing. The only related pair is run_tests/get_test_output, but their roles are clearly sequential rather than interchangeable.

    Naming Consistency4/5

    Most tools follow a clear verb_noun pattern like list_files, read_file, search_code, run_tests, and apply_patch. The get_* variants are slightly different in style but still predictable and consistent with common Git-related naming.

    Tool Count5/5

    Eight tools is a well-scoped size for a repository coding assistant. Each tool covers a necessary operation without redundancy or bloat, and the set is small enough for an agent to navigate easily.

    Completeness4/5

    The toolset covers the core inspect-modify-test loop well: reading, searching, patching, diffing, and running tests. Missing commit/branch management tools are a minor gap for full repository lifecycle coverage, but agents can still complete most coding workflows.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources