de en es ja ko ru zh

GitHub Actions MCP Server

Name: GitHub Actions MCP Server
Author: ko1ynnky

by ko1ynnky

Overview Schema Related Servers Score Discussions

TypeScript

Remote

GitHub Действия MCP Сервер

значок кузнеца

MCP Server для API GitHub Actions, позволяющий помощникам ИИ управлять и работать с рабочими процессами GitHub Actions. Совместим с несколькими помощниками ИИ по кодированию, включая Claude Desktop, Codeium и Windsurf.

Функции

Полное управление рабочими процессами : список, просмотр, запуск, отмена и повторный запуск рабочих процессов
Анализ выполнения рабочего процесса : получите подробную информацию о выполнении рабочего процесса и его задачах.
Комплексная обработка ошибок : понятные сообщения об ошибках с расширенными подробностями
Гибкая проверка типов : надежная проверка типов с изящной обработкой вариаций API
Дизайн, ориентированный на безопасность : обработка тайм-аутов, ограничение скорости и строгая проверка URL-адресов

Инструменты

list_workflows
- Список рабочих процессов в репозитории GitHub
- Входные данные:
  - owner (строка): Владелец репозитория (имя пользователя или организация)
  - repo (строка): Имя репозитория
  - page (необязательное число): Номер страницы для нумерации страниц
  - perPage (необязательное число): Результаты на страницу (макс. 100)
- Возвращает: Список рабочих процессов в репозитории.
get_workflow
- Получите подробную информацию о конкретном рабочем процессе
- Входные данные:
  - owner (строка): Владелец репозитория (имя пользователя или организация)
  - repo (строка): Имя репозитория
  - workflowId (строка или число): идентификатор рабочего процесса или имя файла.
- Возврат: Подробная информация о рабочем процессе
get_workflow_usage
- Получите статистику использования рабочего процесса
- Входные данные:
  - owner (строка): Владелец репозитория (имя пользователя или организация)
  - repo (строка): Имя репозитория
  - workflowId (строка или число): идентификатор рабочего процесса или имя файла.
- Возврат: статистика использования, включая оплачиваемые минуты
list_workflow_runs
- Список всех запущенных рабочих процессов для репозитория или определенного рабочего процесса
- Входные данные:
  - owner (строка): Владелец репозитория (имя пользователя или организация)
  - repo (строка): Имя репозитория
  - workflowId (необязательная строка или число): идентификатор рабочего процесса или имя файла.
  - actor (необязательная строка): Фильтр по пользователю, который запустил рабочий процесс.
  - branch (необязательная строка): Фильтр по филиалу
  - event (необязательная строка): Фильтр по типу события
  - status (необязательная строка): Фильтр по статусу
  - created (необязательная строка): Фильтр по дате создания (ГГГГ-ММ-ДД)
  - excludePullRequests (необязательное логическое значение): исключить запуски, инициированные PR
  - checkSuiteId (необязательное число): Фильтр по идентификатору набора проверок
  - page (необязательное число): Номер страницы для нумерации страниц
  - perPage (необязательное число): Результаты на страницу (макс. 100)
- Возвращает: список выполненных рабочих процессов, соответствующих критериям.
get_workflow_run
- Получите подробную информацию о конкретном рабочем процессе
- Входные данные:
  - owner (строка): Владелец репозитория (имя пользователя или организация)
  - repo (строка): Имя репозитория
  - runId (число): идентификатор запущенного рабочего процесса.
- Возвращает: Подробную информацию о конкретном рабочем процессе.
get_workflow_run_jobs
- Получить задания для определенного рабочего процесса
- Входные данные:
  - owner (строка): Владелец репозитория (имя пользователя или организация)
  - repo (строка): Имя репозитория
  - runId (число): идентификатор запущенного рабочего процесса.
  - filter (необязательная строка): Фильтрация заданий по статусу завершения («последние», «все»)
  - page (необязательное число): Номер страницы для нумерации страниц
  - perPage (необязательное число): Результаты на страницу (макс. 100)
- Возвращает: список заданий в рабочем процессе.
trigger_workflow
- Запустить рабочий процесс
- Входные данные:
  - owner (строка): Владелец репозитория (имя пользователя или организация)
  - repo (строка): Имя репозитория
  - workflowId (строка или число): идентификатор рабочего процесса или имя файла.
  - ref (строка): ссылка для запуска рабочего процесса (ветвь, тег или SHA)
  - inputs (необязательный объект): входные параметры для рабочего процесса
- Возвращает: информацию о запущенном рабочем процессе.
cancel_workflow_run
- Отменить выполнение рабочего процесса
- Входные данные:
  - owner (строка): Владелец репозитория (имя пользователя или организация)
  - repo (строка): Имя репозитория
  - runId (число): идентификатор запущенного рабочего процесса.
- Возврат: Статус операции отмены
rerun_workflow
- Повторный запуск рабочего процесса
- Входные данные:
  - owner (строка): Владелец репозитория (имя пользователя или организация)
  - repo (строка): Имя репозитория
  - runId (число): идентификатор запущенного рабочего процесса.
- Возвращает: Статус повторной операции

Использование с помощниками по кодированию на основе искусственного интеллекта

Этот MCP-сервер совместим с несколькими помощниками по кодированию на основе искусственного интеллекта, включая Claude Desktop, Codeium и Windsurf.

Клод Десктоп

Сначала убедитесь, что вы собрали проект (см. раздел «Сборка» ниже). Затем добавьте следующее в ваш claude_desktop_config.json :

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

Кодеум

Добавьте следующую конфигурацию в файл конфигурации Codeium MCP (обычно в ~/.codeium/windsurf/mcp_config.json в системах на базе Unix или %USERPROFILE%\.codeium\windsurf\mcp_config.json в Windows):

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

Виндсерфинг

Windsurf использует тот же формат конфигурации, что и Codeium. Добавьте сервер в конфигурацию Windsurf MCP, как показано выше для Codeium.

Related MCP server: GitHub MCP Server

Строить

Unix/Linux/macOS

Клонируйте репозиторий и соберите:

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]

Это создаст необходимые файлы в каталоге dist , которые вам понадобятся для запуска сервера MCP.

Инструкции для Windows

Предпосылки

Node.js (v14 или выше)
npm (v6 или выше)

Запуск сервера на Windows

Использование пакетного файла (самый простой способ):
```
run-server.bat [optional-github-token]
```
Это проверит, существует ли сборка, выполнит сборку при необходимости и запустит сервер.
Использование npm напрямую:
```
npm run start
```

Настройка персонального токена доступа GitHub в Windows

Для полной функциональности и во избежание ограничения скорости вам необходимо установить свой персональный токен доступа 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 имеет правильные разрешения.
- Проверьте, что токен правильно установлен как переменная среды.
Ограничение скорости :
- Сервер реализует ограничение скорости, чтобы избежать превышения лимитов API GitHub.
- Если вы столкнулись с ошибками ограничения скорости, уменьшите частоту запросов.
Ошибки проверки типа :
- Ответы API GitHub иногда могут отличаться от ожидаемых схем
- Сервер реализует гибкую проверку для обработки большинства вариаций.
- Если вы столкнулись с постоянными ошибками, пожалуйста, создайте проблему

Лицензия

Этот сервер 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. Dates show when Glama detected each change.

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

Install Server

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.1/5.0

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

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

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
5361
ArletOAuth
dev.arlet
Create, deploy, and operate MCP servers directly from your GitHub repositories.
Developer Tools CI/CD & DevOps
2
OneSchema MCP Server
co.oneschema
MCP server that lets AI assistants use all OneSchema features exposed via the public API.
Data Platforms App Automation
1

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)
25
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 10 months ago (2025-11-03 16:42 UTC)
467
ISC
GitHub MCP Server
Version Control Developer Tools CI/CD & DevOps
Pawangunjkar
A
license
B
quality
C
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 a month ago (2026-08-01 13:36 UTC)
73
MIT
github-directory-mcp
Version Control Developer Tools
Productdeveloper5192
F
license
A
quality
C
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 a month ago (2026-07-27 15:54 UTC)
2
-

Appeared in Searches

Latest Blog Posts

Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)
By Om-Shree-0709 on July 25, 2026.
mcp
Agent Identity
OAuth 2.1
Your AI Chatbot Just Exposed Your CEO's Salary to an Intern
By Om-Shree-0709 on July 2, 2026.
Agent Identity
MCP Security
OAuth Delegation
Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)
By Om-Shree-0709 on June 30, 2026.
Agentic Ai
Prompt Injection
WebAssembly

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/ko1ynnky/github-actions-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server