Skip to main content
Glama
nextDriveIoE

GitHub Action Trigger MCP Server

by nextDriveIoE
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to GitHub Action Trigger MCP Server

No user-submitted related servers found.

    Related Servers

    • GitHub MCP Server

      renantrendt
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to perform GitHub operations including repository management, file operations, issue tracking, and pull request creation.
      2
      -

    • GitHub Integrated MCP Server

      wj-yuta-imai
      -
      license
      C
      quality
      Not graded
      maintenance
      A Model Context Protocol server with GitHub API integration that enables interaction with repositories, issues, pull requests, and file management through a standardized interface.
      1
      -

    • Gooseworks MCP

      EduardKuun
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that exposes GitHub tools for repository management, code search, issue creation, and pull request operations.
      1
      MIT
    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.2/5.0

    Scored across 5 tools

    Disambiguation4/5

    Most tools have distinct purposes: enabling auto-merge, getting action details, listing available actions, fetching releases, and triggering actions. However, 'get_github_action' and 'get_github_actions' could be slightly confusing as they both retrieve action information but differ in scope (single vs. multiple). The descriptions clarify this, but the names are similar enough to cause potential misselection.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern with 'get', 'enable', and 'trigger' as verbs, all using snake_case. The only minor deviation is 'enable_pull_request_automerge' which includes a compound noun, but it still fits the overall style. This consistency makes the tools predictable and easy to understand.

    Tool Count4/5

    With 5 tools, the count is well-scoped for a GitHub Action Trigger server, covering key operations like triggering actions, managing auto-merge, and retrieving related information. It's slightly lean but reasonable, as it focuses on core functionality without unnecessary bloat, though a few more tools might enhance coverage.

    Completeness3/5

    The toolset covers triggering actions and getting action/release info, but has notable gaps. For example, there's no way to disable auto-merge, manage action runs (e.g., cancel or list workflows), or handle other GitHub Actions lifecycle aspects like secrets or environments. This limits agents to basic triggering and info retrieval, with missing operations that could cause workarounds or failures.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources