de en es ja ko ru zh

GitHub Actions MCP Server

Name: GitHub Actions MCP Server
Author: ko1ynnky

by ko1ynnky

Overview Schema Source Related Servers Discussions Admin

TypeScript

Remote

GitHub Actions MCP 서버

대장간 배지

GitHub Actions API용 MCP 서버로, AI 어시스턴트가 GitHub Actions 워크플로를 관리하고 운영할 수 있도록 지원합니다. Claude Desktop, Codeium, Windsurf를 포함한 여러 AI 코딩 어시스턴트와 호환됩니다.

특징

완벽한 워크플로 관리 : 워크플로 나열, 보기, 트리거, 취소 및 다시 실행
워크플로 실행 분석 : 워크플로 실행 및 해당 작업에 대한 자세한 정보를 얻으세요.
포괄적인 오류 처리 : 향상된 세부 정보를 포함한 명확한 오류 메시지
유연한 유형 검증 : API 변형을 우아하게 처리하여 강력한 유형 검사
보안 중심 설계 : 시간 초과 처리, 속도 제한 및 엄격한 URL 유효성 검사

도구

list_workflows
- GitHub 저장소의 워크플로 나열
- 입력:
  - owner (문자열): 저장소 소유자(사용자 이름 또는 조직)
  - repo (문자열): 저장소 이름
  - page (선택적 숫자): 페이지 번호
  - perPage (선택적 숫자): 페이지당 결과(최대 100개)
- 반환: 저장소의 워크플로 목록
get_workflow
- 특정 워크플로의 세부 정보 가져오기
- 입력:
  - owner (문자열): 저장소 소유자(사용자 이름 또는 조직)
  - repo (문자열): 저장소 이름
  - workflowId (문자열 또는 숫자): 워크플로 또는 파일 이름의 ID
- 반환: 워크플로에 대한 자세한 정보
get_workflow_usage
- 워크플로우의 사용 통계 가져오기
- 입력:
  - owner (문자열): 저장소 소유자(사용자 이름 또는 조직)
  - repo (문자열): 저장소 이름
  - workflowId (문자열 또는 숫자): 워크플로 또는 파일 이름의 ID
- 반환: 청구 가능한 시간을 포함한 사용 통계
list_workflow_runs
- 저장소 또는 특정 워크플로에 대한 모든 워크플로 실행을 나열합니다.
- 입력:
  - owner (문자열): 저장소 소유자(사용자 이름 또는 조직)
  - repo (문자열): 저장소 이름
  - workflowId (선택적 문자열 또는 숫자): 워크플로 또는 파일 이름의 ID
  - actor (선택 문자열): 워크플로를 트리거한 사용자로 필터링
  - branch (선택적 문자열): branch로 필터링
  - event (선택 문자열): 이벤트 유형별 필터링
  - status (선택 문자열): 상태별 필터링
  - created (선택 문자열): 생성 날짜(YYYY-MM-DD)로 필터링
  - excludePullRequests (선택적 부울): PR 트리거 실행 제외
  - checkSuiteId (선택적 숫자): 체크 스위트 ID로 필터링
  - page (선택적 숫자): 페이지 번호
  - perPage (선택적 숫자): 페이지당 결과(최대 100개)
- 반환: 기준과 일치하는 워크플로 실행 목록
get_workflow_run
- 특정 워크플로 실행에 대한 세부 정보 가져오기
- 입력:
  - owner (문자열): 저장소 소유자(사용자 이름 또는 조직)
  - repo (문자열): 저장소 이름
  - runId (숫자): 워크플로 실행의 ID
- 반환: 특정 워크플로 실행에 대한 자세한 정보
get_workflow_run_jobs
- 특정 워크플로 실행에 대한 작업 가져오기
- 입력:
  - owner (문자열): 저장소 소유자(사용자 이름 또는 조직)
  - repo (문자열): 저장소 이름
  - runId (숫자): 워크플로 실행의 ID
  - filter (선택적 문자열): 완료 상태('최신', '모두')로 작업을 필터링합니다.
  - page (선택적 숫자): 페이지 번호
  - perPage (선택적 숫자): 페이지당 결과(최대 100개)
- 반환: 워크플로 실행의 작업 목록
trigger_workflow
- 워크플로 실행 트리거
- 입력:
  - owner (문자열): 저장소 소유자(사용자 이름 또는 조직)
  - repo (문자열): 저장소 이름
  - workflowId (문자열 또는 숫자): 워크플로 또는 파일 이름의 ID
  - ref (문자열): 워크플로를 실행할 참조(분기, 태그 또는 SHA)
  - inputs (선택적 객체): 워크플로에 대한 입력 매개변수
- 반환: 트리거된 워크플로 실행에 대한 정보
cancel_workflow_run
- 워크플로 실행 취소
- 입력:
  - owner (문자열): 저장소 소유자(사용자 이름 또는 조직)
  - repo (문자열): 저장소 이름
  - runId (숫자): 워크플로 실행의 ID
- 반환: 취소 작업의 상태
rerun_workflow
- 워크플로 실행을 다시 실행합니다.
- 입력:
  - owner (문자열): 저장소 소유자(사용자 이름 또는 조직)
  - repo (문자열): 저장소 이름
  - runId (숫자): 워크플로 실행의 ID
- 반환: 재실행 작업의 상태

AI 코딩 어시스턴트와 함께 사용

이 MCP 서버는 Claude Desktop, Codeium, Windsurf를 포함한 여러 AI 코딩 어시스턴트와 호환됩니다.

클로드 데스크탑

먼저 프로젝트를 빌드했는지 확인하세요(아래 빌드 섹션 참조). 그런 다음 claude_desktop_config.json 파일에 다음을 추가하세요.

지엑스피1

코디움

Codeium MCP 구성 파일(일반적으로 Unix 기반 시스템에서는 ~/.codeium/windsurf/mcp_config.json 에 있고, Windows에서는 %USERPROFILE%\.codeium\windsurf\mcp_config.json 에 있음)에 다음 구성을 추가합니다.

{
  "mcpServers": {
    "github-actions": {
      "command": "node",
      "args": [
        "<path-to-mcp-server>/dist/index.js"
      ],
      "env": {
        "GITHUB_PERSONAL_ACCESS_TOKEN": "<YOUR_TOKEN>"
      }
    }
  }
}

윈드서핑

Windsurf는 Codeium과 동일한 구성 형식을 사용합니다. 위에 표시된 Codeium의 Windsurf MCP 구성에 서버를 추가하세요.

Related MCP server: GitHub MCP Server

짓다

유닉스/리눅스/맥OS

저장소를 복제하고 빌드합니다.

git clone https://github.com/ko1ynnky/github-actions-mcp-server.git
cd github-actions-mcp-server
npm install
npm run build

윈도우

Windows 시스템의 경우 Windows 전용 빌드 명령을 사용하세요.

git clone https://github.com/ko1ynnky/github-actions-mcp-server.git
cd github-actions-mcp-server
npm install
npm run build:win

또는 포함된 배치 파일을 사용할 수 있습니다.

run-server.bat [optional-github-token]

이렇게 하면 MCP 서버를 실행하는 데 필요한 파일이 dist 디렉토리에 생성됩니다.

Windows 관련 지침

필수 조건

Node.js(v14 이상)
npm(v6 이상)

Windows에서 서버 실행

배치 파일 사용(가장 간단한 방법):
```
run-server.bat [optional-github-token]
```
이렇게 하면 빌드가 있는지 확인하고, 필요한 경우 빌드하고, 서버를 시작합니다.
npm을 직접 사용하는 경우:
```
npm run start
```

Windows에서 GitHub 개인 액세스 토큰 설정

모든 기능을 활용하고 속도 제한을 피하려면 GitHub 개인 액세스 토큰을 설정해야 합니다.

옵션:

배치 파일에 매개변수로 전달합니다.
```
run-server.bat your_github_token_here
```

환경 변수로 설정하세요:

set GITHUB_PERSONAL_ACCESS_TOKEN=your_github_token_here
npm run start

Windows 문제 해결

문제가 발생하는 경우:

빌드 오류 : TypeScript가 올바르게 설치되었는지 확인하세요.
```
npm install -g typescript
```
권한 문제 : 적절한 권한으로 명령 프롬프트에서 명령을 실행하고 있는지 확인하세요.
Node.js 오류 : 호환되는 Node.js 버전을 사용하고 있는지 확인하세요.
```
node --version
```

사용 예

저장소의 워크플로 나열:

const result = await listWorkflows({
  owner: "your-username",
  repo: "your-repository"
});

워크플로 트리거:

const result = await triggerWorkflow({
  owner: "your-username",
  repo: "your-repository",
  workflowId: "ci.yml",
  ref: "main",
  inputs: {
    environment: "production"
  }
});

문제 해결

일반적인 문제

인증 오류 :
- GitHub 토큰에 올바른 권한이 있는지 확인하세요.
- 토큰이 환경 변수로 올바르게 설정되었는지 확인하세요.
속도 제한 :
- 서버는 GitHub API 제한에 도달하지 않도록 속도 제한을 구현합니다.
- 속도 제한 오류가 발생하면 요청 빈도를 줄이십시오.
유형 검증 오류 :
- GitHub API 응답은 예상 스키마와 다를 수 있습니다.
- 서버는 대부분의 변형을 처리하기 위해 유연한 검증을 구현합니다.
- 지속적으로 오류가 발생하는 경우 문제를 열어주세요.

특허

이 MCP 서버는 MIT 라이선스에 따라 라이선스가 부여되었습니다.

Available Tools

9 tools

cancel_workflow_runD

ParametersJSON Schema

Name	Required	Description
`owner`	Yes	Repository owner (username or organization)
`repo`	Yes	Repository name
`runId`	Yes	The ID of the workflow run

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_workflowD

ParametersJSON Schema

Name	Required	Description
`owner`	Yes	Repository owner (username or organization)
`repo`	Yes	Repository name
`workflowId`	Yes	The ID of the workflow or filename (string or number)

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_workflow_runD

ParametersJSON Schema

Name	Required	Description
`owner`	Yes	Repository owner (username or organization)
`repo`	Yes	Repository name
`runId`	Yes	The ID of the workflow run

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_workflow_run_jobsD

ParametersJSON Schema

Name	Required	Description
`owner`	Yes	Repository owner (username or organization)
`repo`	Yes	Repository name
`runId`	Yes	The ID of the workflow run
`filter`	No	Filter jobs by their completed_at date
`page`	No	Page number for pagination
`perPage`	No	Results per page (max 100)

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

get_workflow_usageD

ParametersJSON Schema

Name	Required	Description
`owner`	Yes	Repository owner (username or organization)
`repo`	Yes	Repository name
`workflowId`	Yes	The ID of the workflow or filename (string or number)

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_workflow_runsD

ParametersJSON Schema

Name	Required	Description
`owner`	Yes	Repository owner (username or organization)
`repo`	Yes	Repository name
`workflowId`	No	The ID of the workflow or filename (string or number)
`actor`	No	Returns someone's workflow runs. Use the login for the user
`branch`	No	Returns workflow runs associated with a branch
`event`	No	Returns workflow runs triggered by the event
`status`	No	Returns workflow runs with the check run status
`created`	No	Returns workflow runs created within date range (YYYY-MM-DD)
`excludePullRequests`	No	If true, pull requests are omitted from the response
`checkSuiteId`	No	Returns workflow runs with the check_suite_id
`page`	No	Page number for pagination
`perPage`	No	Results per page (max 100)

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

list_workflowsD

ParametersJSON Schema

Name	Required	Description
`owner`	Yes	Repository owner (username or organization)
`repo`	Yes	Repository name
`page`	No	Page number for pagination
`perPage`	No	Results per page (max 100)

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

rerun_workflowD

ParametersJSON Schema

Name	Required	Description
`owner`	Yes	Repository owner (username or organization)
`repo`	Yes	Repository name
`runId`	Yes	The ID of the workflow run

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

trigger_workflowD

ParametersJSON Schema

Name	Required	Description
`owner`	Yes	Repository owner (username or organization)
`repo`	Yes	Repository name
`workflowId`	Yes	The ID of the workflow or filename (string or number)
`ref`	Yes	The reference of the workflow run (branch, tag, or SHA)
`inputs`	No	Input parameters for the workflow

TDQS

D1/5.0

Behavior1/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Tool has no description.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness1/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Tool has no description.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness1/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Tool has no description.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters1/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Tool has no description.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose1/5

Does the description clearly state what the tool does and how it differs from similar tools?

Tool has no description.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines1/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Tool has no description.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

4 tool updatesv1.0.0Jan 2, 2026

Changedget_workflow2 fields changed

changedInput schema / properties / workflowId / description

Previous value: -"The ID of the workflow or filename"New value: +"The ID of the workflow or filename (string or number)"

changedInput schema / properties / workflowId / type

Previous value: -[
-  "string",
-  "number"
-]New value: +"string"

Changedget_workflow_usage2 fields changed

changedInput schema / properties / workflowId / description

Previous value: -"The ID of the workflow or filename"New value: +"The ID of the workflow or filename (string or number)"

changedInput schema / properties / workflowId / type

Previous value: -[
-  "string",
-  "number"
-]New value: +"string"

Changedlist_workflow_runs2 fields changed

changedInput schema / properties / workflowId / description

Previous value: -"The ID of the workflow or filename"New value: +"The ID of the workflow or filename (string or number)"

changedInput schema / properties / workflowId / type

Previous value: -[
-  "string",
-  "number"
-]New value: +"string"

Changedtrigger_workflow2 fields changed

changedInput schema / properties / workflowId / description

Previous value: -"The ID of the workflow or filename"New value: +"The ID of the workflow or filename (string or number)"

changedInput schema / properties / workflowId / type

Previous value: -[
-  "string",
-  "number"
-]New value: +"string"

9 tool updatesApr 7, 2025
- First observedcancel_workflow_run
- First observedget_workflow
- First observedget_workflow_run
- First observedget_workflow_run_jobs
- First observedget_workflow_usage
- First observedlist_workflow_runs
- First observedlist_workflows
- First observedrerun_workflow
- First observedtrigger_workflow

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

C2.1/5.0

Scored 2026-04-18 11:05 across 9 tools

Disambiguation5/5

Every tool has a clearly distinct purpose targeting specific GitHub Actions resources and operations. The naming clearly indicates whether tools retrieve information (get_, list_), trigger actions (trigger_, rerun_, cancel_), or access different aspects (workflows, runs, jobs, usage). There is no ambiguity or overlap in functionality.

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with perfect uniformity. The verbs (cancel, get, list, rerun, trigger) are consistently applied to clearly defined nouns (workflow, workflow_run, workflow_run_jobs, etc.). There are no deviations in naming conventions or styles.

Tool Count5/5

With 9 tools, this server is well-scoped for managing GitHub Actions workflows. The count is appropriate for covering core operations like listing, retrieving, triggering, and managing workflow runs without being overwhelming. Each tool serves a distinct purpose that earns its place in the set.

Completeness4/5

The tool surface provides excellent coverage for the GitHub Actions domain with operations for listing, retrieving, triggering, rerunning, and canceling workflows and runs. Minor gaps might include tools for managing workflow files or secrets, but the core lifecycle operations are well-covered for typical agent workflows.

Maintenance

ActivityInactive

ResponsivenessNo issues

Resources

Need Help?

Reddit Discussion

Related Servers

Related MCP Connectors

FlowraOAuth
io.github.flowradev
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Agent Orchestration Autonomous Agents
11
driflyte-mcp-server
com.driflyte
Driflyte MCP server which lets AI assistants query topic-specific knowledge from web and GitHub.
Search Web Scraping Knowledge & Memory
211
gread A
io.github.NitroRCr
An MCP server that gives your AI access to the source code and docs of all public github repos
Version Control Code Analysis Documentation Access
5365
ArletOAuth
dev.arlet
Create, deploy, and operate MCP servers directly from your GitHub repositories.
Developer Tools CI/CD & DevOps
2

Related MCP Servers

GitHub CLI MCP Server
Version Control Developer Tools App Automation
CodingButterBot
A
license
Not graded
quality
D
maintenance
An MCP server that wraps around the GitHub CLI tool, allowing AI assistants to interact with GitHub repositories through commands for pull requests, issues, and repository operations.
Updated a year ago (2025-05-02 04:53 UTC)
12 npm
MIT
GitHub MCP Server
Version Control Developer Tools
grysonbaltazar
A
license
Not graded
quality
D
maintenance
An MCP server that provides tools for interacting with the GitHub API, enabling AI assistants to query repositories, pull requests, issues, commits, users, and more.
Updated a year ago (2025-11-03 16:42 UTC)
261 npm
ISC
GitHub MCP Server
Version Control Developer Tools CI/CD & DevOps
Pawangunjkar
A
license
B
quality
D
maintenance
A comprehensive MCP server that exposes 73 GitHub API tools for managing repositories, pull requests, issues, actions, releases, search, and more, enabling natural language control of GitHub.
Updated 3 months ago (2026-08-01 13:36 UTC)
73
MIT
github-directory-mcp
Version Control Developer Tools
Productdeveloper5192
A
license
A
quality
D
maintenance
An MCP server that enables AI assistants to list GitHub repositories for a user or organization and list directories within a repository via the GitHub REST API.
Updated 3 months ago (2026-07-27 15:54 UTC)
2
ISC

GitHub Actions MCP 서버

특징

도구

AI 코딩 어시스턴트와 함께 사용

클로드 데스크탑

코디움

윈드서핑

짓다

유닉스/리눅스/맥OS

윈도우

Windows 관련 지침

사용 예

문제 해결

일반적인 문제

특허

Available Tools

Tool Schema Changelog

Maintenance

Resources

Related MCP Connectors

Related MCP Servers

Appeared in Searches