Skip to main content
Glama
shreyakat21

mcp-github-db-server

by shreyakat21
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to mcp-github-db-server

No user-submitted related servers found.

    Related Servers

    • GitHub Dev Copilot

      yashwant-kumar08
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to interact with GitHub via MCP, managing repositories, issues, PRs, and analyzing repository health through tools like list_repositories, read_issues, create_issue, comment_on_pr, and analyze_repo_health.
      -

    • Gitingest-MCP

      ryuji1315
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP clients such as Claude Desktop, Cline, and Cursor to extract information from GitHub repositories, including repository summaries, project directory structure, and file contents. It exposes these capabilities as tools that can be invoked directly from a natural-language chat session.
      -

    • repogate

      JohnXu22786
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that wraps the GitHub REST API into tools for repo queries, issue/PR management, code review, search, and authentication, letting coding agents operate GitHub directly in conversations.
      5 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.2/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct resource-and-action purposes: GitHub reads, issue creation, PR listing, and DB read/write/table inspection are separable. The main overlap is db_upsert_project versus db_execute, since upsert_project is a specialized write helper that could also be done via generic execution.

    Naming Consistency4/5

    The set follows a predictable domain-prefixed verb_noun pattern: github_list_repos, github_get_file, db_list_tables, db_describe_table, db_upsert_project. Minor deviations are db_query and db_execute, which omit a noun object but remain clear and consistent with the db_ prefix.

    Tool Count5/5

    Twelve tools is well within a reasonable range for a server combining GitHub reads/issue creation with local SQLite access. Each tool covers a distinct operation, and the surface does not feel bloated or thin.

    Completeness3/5

    The database side is fairly complete with table listing, schema description, read queries, writes, and an upsert helper. The GitHub side is notably incomplete: it can list issues and create issues, but has no update/close/get issue, no PR creation or merge, and no PR detail or comment operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources