Skip to main content
Glama
4hglee-ops

Gyuniverse GitHub Projects MCP

by 4hglee-ops
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to Gyuniverse GitHub Projects MCP

No user-submitted related servers found.

    Related Servers

    • ContextBridge

      Vatsal212005
      A
      license
      B
      quality
      B
      maintenance
      A security-first MCP gateway that enables AI assistants to safely inspect and interact with GitHub repositories through a controlled, auditable tool layer with policy enforcement and human approval for mutations.
      27
      MIT

    • GitHub Flow MCP

      thiagorchaves
      A
      license
      C
      quality
      B
      maintenance
      A policy-aware MCP server for GitHub and GitHub Actions that enables safe AI-assisted infrastructure workflows—inspecting repositories, preparing branches and pull requests, and constrained remote mutations behind explicit preview-bound approval tokens.
      18
      MIT

    • Moory

      dalmaktube-creator
      A
      license
      Not graded
      quality
      A
      maintenance
      A self-hosted MCP bridge that enables Notion AI to interact with approved Git repositories and curated GitHub APIs, supporting guarded code changes, pull requests, issues, Actions, logs, releases, secret scanning, and audit logging.
      Apache 2.0
    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

    C2.8/5.0

    Scored across 40 tools

    Disambiguation2/5

    Several tools overlap heavily, especially compatibility aliases (update_github_project_item_status vs update_work_item_status, and similarly for priority) and multiple project-state readers (get_github_project_snapshot, get_github_project_brief_context, get_project_brief, get_project_changes). An agent could easily misselect among resolution, snapshot, and brief tools.

    Naming Consistency3/5

    All names use snake_case, but the surface mixes prefixed (github_project) and unprefixed (work_item, project_brief) conventions, and includes explicit alias pairs. This remains readable but not fully predictable.

    Tool Count2/5

    40 tools is heavy for a GitHub Projects MCP, with bulk operations, audit logging, and multiple analysis layers. Each earns some place, but the count is well above a well-scoped 10–15 tool surface.

    Completeness3/5

    Core read, write, relationship, bulk, and analysis coverage is strong, but notable lifecycle gaps remain: no remove/delete Project item, no Project or field creation/mutation beyond item fields, and no draft issue creation. Agents can cover many workflows but will hit dead ends for cleanup and schema changes.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources