Skip to main content
Glama
pluto-atom-4

mcp-gh-forge

by pluto-atom-4

Related Servers

Alternatives to mcp-gh-forge

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight MCP server that handles git operations on behalf of AI coding assistants, running as a local HTTP service without external network exposure by default.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets AI assistants safely access local git repositories, with free reads and gated writes requiring explicit confirmation.
      1
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      A lightweight MCP server that enables AI assistants to manage local Git repositories by executing commands like status, add, and commit. It streamlines development workflows by providing repository context and diffs directly to the assistant.
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that enables AI assistants to interact with GitHub via a fine-grained personal access token — pushing commits, managing branches, opening and merging PRs, creating issues, and reading repositories. It runs locally with no telemetry and supports a read-only mode.
      15
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that turns AI clients into power users of local git repositories, enabling clone, browse, search, and inspect code without burning API tokens.
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides tools for interacting with Git repositories, enabling AI assistants to manage repositories, branches, commits, and files through a standardized interface.
      2,852 npm
      1
      Apache 2.0

    TDQS

    B3.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    Only one tool exists, so there is no possibility of confusion between tools. The single tool is clearly named and described.

    Naming Consistency5/5

    With only one tool, naming consistency is trivially maintained. The tool follows a verb_noun pattern.

    Tool Count1/5

    A single tool is extremely thin for a server named 'mcp-gh-forge', which implies a broader scope. Packing multiple operations into one macro tool is poor design.

    Completeness2/5

    The tool bundles several scripts (consolidate, get-changed-files, etc.) but lacks granular tools for individual operations, making the surface incomplete for typical GitHub automation workflows.

    Maintenance

    ActivityStale
    ResponsivenessUnresponsive