Github Action Trigger Mcp

Created By
nextDriveIoEa year ago
Overview

what is Github Action Trigger MCP?

Github Action Trigger MCP is a TypeScript-based Model Context Protocol server designed for seamless integration with GitHub Actions, allowing users to manage and trigger workflows efficiently.

how to use Github Action Trigger MCP?

To use the Github Action Trigger MCP, you can install it via npx or manually through npm. Configure your GitHub personal access token for authentication and set it in your Claude Desktop configuration file.

key features of Github Action Trigger MCP?

  • Fetch available GitHub Actions from a repository.
  • Get detailed information about specific GitHub Actions.
  • Trigger GitHub workflow dispatch events.
  • Fetch the latest releases from a GitHub repository.

use cases of Github Action Trigger MCP?

  1. Automating CI/CD workflows in GitHub repositories.
  2. Fetching and managing GitHub Actions for better workflow management.
  3. Triggering workflows based on specific events or conditions.

FAQ from Github Action Trigger MCP?

  • How do I install Github Action Trigger MCP?

You can install it using npx or manually via npm. Refer to the installation section in the documentation for detailed steps.

  • Do I need a GitHub personal access token?

Yes, a GitHub personal access token is required for accessing private repositories and triggering workflows.

  • Can I use this tool for any GitHub repository?

Yes, as long as you have the necessary permissions and the repository is accessible with your GitHub token.

Server Config

{
  "mcpServers": {
    "github-action-trigger-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@nextdrive/github-action-trigger-mcp"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "your_github_token_here"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
nextDriveIoE
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago