Skip to main content
Glama
neural-shubh

personal-github-mcp

by neural-shubh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to personal-github-mcp

No user-submitted related servers found.

    Related Servers

    • GitHub MCP Server

      akarnik23
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables access to GitHub repositories and data through the GitHub API. Supports retrieving repositories, issues, pull requests, and searching code across GitHub with authentication via personal access tokens.
      -

    • GitHub MCP Server

      AlexKissiJr
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables comprehensive interaction with the GitHub API, including file operations, repository management, issue tracking, pull request workflows, and advanced search functionality across code, issues, and users.
      88,163 npm
      MIT

    • GitHub Mapper MCP Server

      dazeb
      F
      license
      C
      quality
      D
      maintenance
      Provides tools for mapping and analyzing GitHub repositories. It allows users to set a GitHub Personal Access Token and retrieve detailed information about a specified repository, including its structure and summary statistics.
      2
      25
      -

    • Git Workflow Automation MCP

      Arcia125
      F
      license
      C
      quality
      D
      maintenance
      Provides automated Git workflow tools for committing, creating pull requests, and merging with proper GitHub authentication handling. Supports complete Git workflows from commit to merge with dry run capabilities and conventional commit formatting.
      4
      1
      -
    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.6/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool, there is no possibility of confusion between different tools. The tool's purpose as a generic GitHub API request handler is clear and unambiguous.

    Naming Consistency5/5

    The single tool name 'github_request' directly describes its function. Since there is only one tool, there is no inconsistent naming pattern to evaluate.

    Tool Count3/5

    A single tool is on the lower end of the spectrum and feels thin for a GitHub MCP server. However, the tool is powerful and comprehensive, so it is not trivial, but it places a heavy burden on the agent to know the API specifics.

    Completeness5/5

    The tool claims to cover any GitHub REST API endpoint, making it functionally complete for the domain. It supports all HTTP verbs and includes query parameters and body handling, so no obvious operations are missing.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources