GitHub Actions MCP Server

Created By
Since120a year ago
Overview

what is GitHub Actions MCP Server?

GitHub Actions MCP Server is a management tool for the GitHub Actions API, designed to enable AI assistants to manage and operate GitHub Actions workflows.

how to use GitHub Actions MCP Server?

To use the MCP Server, clone the repository, build the project, and configure it with your GitHub Personal Access Token. Then, integrate it with AI coding assistants like Claude Desktop, Codeium, or Windsurf.

key features of GitHub Actions MCP Server?

  • Complete Workflow Management: List, view, trigger, cancel, and rerun workflows.
  • Workflow Run Analysis: Get detailed information about workflow runs and their jobs.
  • Comprehensive Error Handling: Clear error messages with enhanced details.
  • Flexible Type Validation: Robust type checking with graceful handling of API variations.
  • Security-Focused Design: Timeout handling, rate limiting, and strict URL validation.

use cases of GitHub Actions MCP Server?

  1. Managing CI/CD workflows in GitHub repositories.
  2. Automating the triggering of workflows based on events.
  3. Analyzing workflow run statistics for optimization.

FAQ from GitHub Actions MCP Server?

  • Can I use this server with any AI coding assistant?

Yes! It is compatible with multiple AI coding assistants including Claude Desktop, Codeium, and Windsurf.

  • Is there a specific Node.js version required?

Yes, Node.js version 14 or higher is required to run the server.

  • How do I handle authentication errors?

Ensure your GitHub token has the correct permissions and is set as an environment variable.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Since120
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago