Skip to main content
Glama
wuqunfei

github-mcp-server-js

by wuqunfei
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to github-mcp-server-js

No user-submitted related servers found.

    Related Servers

    • github-mcp-server

      tongax12
      A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that enables natural language interaction with GitHub, supporting operations like creating repositories, issues, commits, and listing repositories or issues.
      MIT

    • demo-github

      attacker-code
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server that connects to the GitHub API to list and create issues, comment on issues, and list pull requests with diff summaries. It enables natural language management of GitHub repositories from MCP-compatible clients.
      -

    • Git PR MCP Server

      peterj
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables Git repository operations and GitHub PR workflows, allowing users to manage repositories, create branches, commit changes, and create pull requests through natural language.
      2
      -
    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

    B3.4/5.0

    Scored across 108 tools

    Disambiguation5/5

    Each tool maps to a distinct GitHub REST endpoint and resource type; even dense areas like workflow runs and packages use precise noun phrases (e.g. list_workflow_run_jobs vs list_workflow_runs) that prevent confusion. The only near-overlaps (list_issues vs search_issues) are clearly disambiguated by repository-scoped vs global search semantics.

    Naming Consistency5/5

    All tool names follow a consistent lower_snake_case verb_noun pattern, with list_ for collection reads and get_ for single-item reads, and mutation verbs (create, update, delete, add, remove, merge, cancel, rerun) used predictably. Longer names like add_or_update_team_membership remain readable and aligned with the overall convention.

    Tool Count1/5

    At 108 tools, this is far beyond the 16-25 'heavy' range and falls squarely into the 'extreme mismatch (50+ tools)' category. The sheer number creates an overwhelming selection surface for agents, even though each tool is individually well-described.

    Completeness3/5

    Coverage is broad across repos, issues, PRs, workflows, gists, packages, advisories, and codespaces, with many full CRUD lifecycles present. However, there are notable missing operations: no create/update/delete repository, no releases, no alert state mutations (e.g. dismiss), and ProjectsV2 access is read-only.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources