Skip to main content
Glama
github-core-clone-01

github-core-clone-01

by toirant

Related Servers

Alternatives to github-core-clone-01

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Exposes an MCP Streamable HTTP endpoint that lets clients create and fetch repositories, create and list issues, and create and merge pull requests against a self-hosted, GitHub-compatible git forge. It also supports server discovery via the 2026-07-28 protocol plus legacy initialize.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A lightweight MCP server that exposes GitHub operations as tools over HTTP, enabling any MCP-compatible client to interact with GitHub repositories without a built-in connector.
      1
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Exposes GitHub-compatible operations over MCP, letting agents create and inspect repositories, issues, pull requests, and file contents against a shared in-memory forge store that stays consistent with the same server's REST, GraphQL, and git smart HTTP surfaces.
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      MCP server exposing GitHub tools for issues, pull requests, and code browsing via the GitHub REST API. Designed for local LLM clients with flat arguments and streamable HTTP support.
      15
      -
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables Git repository operations and real-time monitoring via MCP tools, with support for WebSocket events, authentication, and observability.
      13 npm
      4
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      Enables operators to publish immutable, schema-validated tool and toolkit versions and expose them to authenticated, binding-scoped clients over stateless Streamable HTTP at /mcp, with bounded pagination and audited calls. Tool invocations run through a credential-brokering queue in isolated, ephemeral, non-root Kata workers, so packaged code is never executed by the API itself.
      Apache 2.0